1
0
mirror of https://github.com/fwbuilder/fwbuilder synced 2026-05-01 14:47:27 +02:00
fwbuilder/test/pf/firewall109-1.fw.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

39 lines
999 B
Plaintext
Executable File

#
# This is automatically generated file. DO NOT MODIFY !
#
# Firewall Builder fwb_pf v5.0.0.3551
#
# Generated Wed Jun 22 10:50:08 2011 PDT by vadim
#
# files: * firewall109-1.fw /etc/fw/pf.fw
# files: firewall109-1.conf /etc/fw/path\ with\ space/pf.conf
#
# Compiled for pf 4.7
#
# complex configuration with bridge and vlan, rc.conf format
gateway_enable="YES"
cloned_interfaces="vlan101 vlan102 bridge0"
network_interfaces="bridge0 em0 vlan101 vlan102"
ifconfig_em0="10.3.14.81 netmask 0xffffff00"
ifconfig_em1="up media 100baseTX mediaopt full-duplex"
vlans_em2="vlan101 vlan102"
create_args_vlan101="vlan 101 vlandev em2"
create_args_vlan102="vlan 102 vlandev em2"
ifconfig_em2="up media 100baseTX mediaopt full-duplex"
ifconfig_vlan101="192.168.101.1 netmask 0xffffff00"
ifconfig_vlan102="192.168.102.1 netmask 0xffffff00"
ifconfig_bridge0="addm em1 -stp em1 addm em2 -stp em2 up 192.168.1.1 netmask 0xffffff00"
pf_enable="YES"
pf_rules="/etc/fw/path\ with\ space/pf.conf"