Improvement to fw & NAT
-
Hi all. Perhaps this is not the correct way to do this, so sorry.
would be desirable to use hostnames on NAT and filter rules.
Great job!! Many thanks!!
-
you can, via aliases.
-
@cmb:
you can, via aliases.
MMmmm not. I say to use real hostnames, because exits the posibility that dhcp (or anything else) change the hostname ip.
Captive portal manage hostnames, so I think that is a good idea to use hostnames on fw or nat too.
It's only a suggestion…
Thanks!!!
-
Aliases automatically update to new IPs as needed.
-
-
Another improvement is to use "not" on port destination.
For example: How can I block all connections from one host that's don't use https port destination? (without the need to create two or more rules)