1
0
mirror of https://github.com/fwbuilder/fwbuilder synced 2026-03-20 02:07:23 +01:00
fwbuilder/test/pf/firewall20.conf.orig
Vadim Kurland 344a22feed see #2524 'avoid " {tcp udp icmp} " in place of protocol'. NAT
compiler for PF does not need to generate protocol match "proto {tcp
udp icmp}" when service object used in the NAT rule is "any". The
reason this was done this way is lost in the mist of time; it's been
like this since very early versions of fwbuilder.
2011-06-22 11:03:07 -07:00

33 lines
710 B
Plaintext

#
# Rule 0 (NAT)
nat on dc2 from 192.168.1.0/24 to any -> (dc2)
nat on dc0 from 192.168.1.0/24 to any -> (dc0)
nat on dc1 from 192.168.1.0/24 to any -> (dc1)
#
# Rule 1 (NAT)
nat on dc1 from 192.168.1.0/24 to any -> (dc1)
#
# Rule 2 (NAT)
nat on dc1 from 192.168.1.0/24 to any -> 222.222.222.20
#
# Rule 3 (NAT)
nat on dc0 from 192.168.1.0/24 to any -> 222.222.222.40
#
# Rule 0 (dc0)
pass in quick on dc0 inet from any to 222.222.222.22 keep state
#
# Rule 1 (dc1)
pass out quick on dc1 inet from any to 222.222.222.22 keep state
#
# Rule 2 (global)
block quick inet from any to any
#
# Rule fallback rule
# fallback rule
block quick inet from any to any