Hi, here’s the situation: I have a WWW server in my LAN and forward ports 443 and 80 from public IP to local server’s IP. I’ve noticed that there are very specific IPs that tend to try cracking my server. I thought I’d block them and here is when things start to become ugly. First of all when I try to add a filter like this:
/ip firewall filter add chain=input src-address=xxx.xxx.xxx.xxx action=drop
nothing really happens. I have a testing computer with public IP and whenever I use its IP in the rule, the rule is completly ignored and I can access mu server from the outside. I experimented a bit and at one point found a solution (at least sort of):
/ip firewall filter add chain=forward src-address=xxx.xxx.xxx.xxx action=drop
I have a 2 questions:
- why chain=input didn’t work while chain=forward works? This doesn’t make sense to me really,
- when in the same rule I add dst-address=yyy.yyy.yyy.yyy (my server’s public IP), the rule stops working. What if I have 2-3 WWW servers, forward their public addresses to their LAN addresses and want some external IPs prevent from accessing only one or two of these servers?.
Kindest regards,
Olek