My brother and I play a few online games together, and neither game has built-in voice chat, so I installed a Teamspeak server on my machine and we both run the client. Of course, I have to forward the port to my machine, and that works fine.
However, I don't want to leave the port forwarded if we're not playing, so I wind up activating and deactivating that forwarding rule (and the Ghost Recon one if we're playing that game and I'm hosting) whenever we play. Unfortunately, that requires a reboot, which kicks my whole house off the router (and hence, the Internet) for 30-35 seconds. With my old Zyxel router, this reboot lasted just a few seconds, and in fact didn't always kick people off.
So, I thought I'd try Inbound Filters. But I've had zero luck with them. I want to limit that rule to just my brother's IP address. To test it, I've created a rule with a different IP and then had him join - he shouldn't be able to join, but he is.
On the same entry as the Teamspeak rule, I leave the schedule at "Always" and I set the Filter to something, but it seems to make no difference. I even tried "Deny All" and my brother was still able to connect.
I'd appreciate any suggestions. Thanks.