Blocking with no logs?

This forum is only for reproducible bugs with csf and lfd (i.e. not iptables problems, lack of understanding how to use a feature, etc). Posts must be accompanied with full technical details of the problem and how it can be recreated. Any posts not adhering to this, or not considered bugs, will be moved to the General Discussion (csf) forum.
Post Reply
mistaneat
Junior Member
Posts: 6
Joined: 08 Dec 2008, 22:33

Blocking with no logs?

Post by mistaneat »

I've seen a lot of reports of clients being blocked by the firewall, yet there are no logs that LFD ever blocked that IP. Messenger service is being used. Synflood is off. Any reason why blocks would be occurring with no logs indicating so.
chirpy
Moderator
Posts: 3537
Joined: 09 Dec 2006, 18:13

Post by chirpy »

You would need to use the grep function of csf to see if an IP address is blocked and where. The only place an IP address could be blocked in iptables and not appear in iptables explicitly (or implicitly in a CIDR range) is if you use the latest ipt_recent option PORTFLOOD. Apart from that, or inclusion in one of the BLOCKLISTS, lfd will always log in lfd.log when it adds an ip address to iptables.

The only other likely cause is if you have anything else that blocks connections, e.g. cPHulk on cPanel.
mistaneat
Junior Member
Posts: 6
Joined: 08 Dec 2008, 22:33

Post by mistaneat »

The messenger service is reporting the block to the end user so I assume that it is a CSF/LFD related block rather than another service. CSF/LFD doesn't modify existing IPtables blocks to forward as far as I'm aware. (CPhulkd is also disabled).

The blocks are temporary blocks because when we go to examine the issue the IP is no longer blocked. Checking the logs also reveals nothing. PORTFLOOD is not being used. None of the block lists (BOGON, SpamHaus, or DSHIELD) are enabled. So the issue is quite odd.

Let me know if you have any additional ideas as to what could be causing these occasional temporary block issues.
Post Reply