Does the NOT option also include the port setting?
-
Hi,
While defining rules, if we select the NOT option (to invert the sense of the following source or destination setting), does it also include the port setting?
For instance, if I want to define a rule that'll pass all UDP traffic except when destination has certain BitTorrent ports (but any destination host), can we implement this as NOT of destination, where host is ANY and port is an alias like BitTorrentPorts (which defines such ports)?
Thanks!
pubmsu -
You can use NOT on dest and or ports, etc.
So sure you could put any and NOT a alias with ports it so for example if your alais had ports 5678 and port 1234 in there. And you were trying to go to 9000 it would work, anything that is NOT those 2 ports would work.
Keep in mind that bittorrent can run on any port reall.. Could be anything really >1024
-
Thanks a lot for confirming!
Bittorrent is really tough to control it seems.
-
You can use NOT on dest and or ports, etc.
So sure you could put any and NOT a alias with ports it so for example if your alais had ports 5678 and port 1234 in there. And you were trying to go to 9000 it would work, anything that is NOT those 2 ports would work.
Keep in mind that bittorrent can run on any port reall.. Could be anything really >1024
Including ports under 1024 because you can run a torrent daemon with root privileges if you're brave enough to do so.
