I was quite pleased I'd configured our 9980 firewall to block all manner of traffic until one of the guys from the workshop popped his head around the door and said "there's something wrong with the...

Agree, I flagged the IPSec vulnerability 18 months ago and they said it would be fixed in the next firmware. It wasn't. Still it's easy to address once you know it's happening, and guest wireless...

Of course the other alternative is to not bother with the firewall, as it's easy to bypass by anyone who knows what they're doing (VPN on port 80). P.S. I wonder if these problems are why TP-Link...

Thanks for pointing this out, my 9980 displays the same behaviour. I also found that if you have a site-to-site IPSec VPN, users on the guest network can access devices on the remote network. There...

NAT forwarding cannot meet this requirement. So it appears TP-Link have taken the configurable firewall out of all new routers which is a massive step backwards I don't understand.

I want to do the following: 1. Allow port 53 traffic to OpenDNS server for all clients 2. Block port 53 traffic to everywhere else for all clients 3. Allow ports 25, 80, 100, 143, 465, 587, 993, 995...