Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

recent-badguys also triggers for broadcast and multicast. #47

Open
ypid opened this issue Sep 1, 2015 · 1 comment
Open

recent-badguys also triggers for broadcast and multicast. #47

ypid opened this issue Sep 1, 2015 · 1 comment

Comments

@ypid
Copy link
Member

ypid commented Sep 1, 2015

Hi

One should be careful when enabling ferm_mark_portscan as it also triggers for broadcast and multicast and thus might block legitimate hosts. This is probably only relevant for LAN environments.

I have solved that issue for my workstation with the "addrtype" module (custom Firewall script 😉 ):

-m addrtype --dst-type BROADCAST,MULTICAST
@drybjed
Copy link
Member

drybjed commented Sep 1, 2015

Marking potential port scans in this way is not active by default in debops.ferm. Perhaps a separate list of whitelisted networks could be added here, so that the affected hosts can be easily added. I imagine that this would be a broad range of hosts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants