I then use nmap to do a full scan of my ports from an outside network and sadly I was able to scan everything. All of the rules were easy to add except for the first one:
add chain=input protocol=tcp psd=21,3s,3,1 action=add-src-to-address-list address-list=“port scanners” address-list-timeout=2w comment="Port scanners to list " disabled=no
For some reason the terminal didn’t like the comment being before the disabled = no entry so I switched it around and it took the rule fine.
However the most important part is that this isn’t working at all. I am able to easily scan all sports using SYN stealth scan.
So I wondering are these rules supposed to stop wan side port scans? The description on that page says this:
“To protect the Router from port scanners, we can record the IPs of hackers who try to scan your box. Using this address list we can drop connection from those IP”
I copied these rules directly using the terminal and they are present on the firewall rules. Then I tested the router by scanning it with nmap from an outside network. The internal network port scanning rules are working quite well and do block any internal port scans. So should the chain be set to input or forward?
I was still able to port scan without detection using nmap. Blocking all connections except for what I want in and out seems interesting. However I really want to be able to stop the port scanning, do you have any other recommendations or is there something that I may have missed with these rules? Was I supposed to change any of the “0” for actual ports or anything of that nature? Please let me know.
Doesn’t that need to be AFTER your "accept from outside"rules? If you put it before, EVERYTHING coming in gets either tarpitted (tcp) or dropped (other than tcp) before it ever gets to your “accept from outside” rules. Or am I missing something?