Please explain how you upgraded from a snapshot?
cvs_sync.sh? If so, did you happen to forget the RELENG_1 portion?
On 4/10/06, William Armstrong <[EMAIL PROTECTED]> wrote:
> I upgrade direct from snapshot and get this errors
> I create all rules again and get this error
>
> 2006/4/10, Bill Marquette <[EMAIL PROTECTED]>:
> > Haven't seen that one before (and I just upgraded my main box to the
> > 4-08 snapshot). What happens if you delete that rule (I assume it's
> > not needed based on your wording)?
> >
> > --Bill
> >
> > On 4/10/06, William Armstrong <[EMAIL PROTECTED]> wrote:
> > > phantom rule is inserted on my system config.xml
> > >
> > > <rule>
> > > <type>pass</type>
> > > <interface>opt3</interface>
> > > <max-src-nodes/>
> > > <max-src-states/>
> > > <statetimeout/>
> > > <statetype>keep state</statetype>
> > > <os/>
> > > <max-src-conn-rate/>
> > > <max-src-conn-rates/>
> > > <source>
> > > <any/>
> > > </source>
> > > <destination>
> > > <any/>
> > > </destination>
> > > <descr/>
> > > </rule>
> > >
> > >
> > > there were error(s) loading the rules: /tmp/rules.debug:393: syntax
> > > errorpfctl: Syntax error in config file: pf rules not loaded - The
> > > line in question reads [393]: label "USER_RULE" ...
> > >
> > >
> > > # /tmp/debug.rules
> > >
> > > pass in quick on $wan proto udp from any to { 10.0.1.3 } port = 4712
> > > keep state queue (qwandef, qwanacks) label "USER_RULE: NAT LAN"
> > > pass in quick on $wan proto udp from any to { 10.0.1.3 } port = 2213
> > > keep state queue (qwandef, qwanacks) label "USER_RULE: NAT RAID"
> > > ------>>>>> label "USER_RULE" <<<<<------------
> > > # opt3 array key does not exist for label "USER_RULE"
> > >
> > >
> > > partial dmesg
> > >
> > > fxp0: <Intel 82559 Pro/100 Ethernet> port 0xd800-0xd83f mem
> > > 0xe4800000-0xe4800fff,0xe4000000-0xe40fffff irq 9 at device 9.0 on
> > > pci1
> > > miibus0: <MII bus> on fxp0
> > > inphy0: <i82555 10/100 media interface> on miibus0
> > > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > > fxp0: Ethernet address: 00:02:b3:3a:42:f2
> > > dc0: <82c169 PNIC 10/100BaseTX> port 0xd400-0xd4ff mem
> > > 0xe3800000-0xe38000ff at device 10.0 on pci1
> > > miibus1: <MII bus> on dc0
> > > bmtphy0: <BCM5201 10/100baseTX PHY> on miibus1
> > > bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > > dc0: Ethernet address: 00:a0:cc:5a:14:dd
> > > xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd000-0xd07f mem
> > > 0xe3000000-0xe300007f irq 11 at device 11.0 on pci1
> > > miibus2: <MII bus> on xl0
> > > xlphy0: <3c905C 10/100 internal PHY> on miibus2
> > > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > > xl0: Ethernet address: 00:01:02:38:ff:81
> > > xl1: <3Com 3c905C-TX Fast Etherlink XL> port 0xb800-0xb87f mem
> > > 0xe2800000-0xe280007f irq 5 at device 12.0 on pci1
> > > miibus3: <MII bus> on xl1
> > > ukphy0: <Generic IEEE 802.3u media interface> on miibus3
> > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > > xl1: Ethernet address: 00:01:03:df:83:3f
> > >
> > >
> > > *** Welcome to pfSense RELENG_1_SNAPSHOT_04-08-2006-pfSense on cerberus
> > > ***
> > >
> > > WAN* -> fxp0 -> 192.168.33.2
> > > OPT2(OPT2) -> dc0 -> NONE
> > > LAN* -> xl0 -> 10.0.1.1
> > > OPT1(OPT1) -> xl1 -> NONE
> > >
> > >
> > >
> > > --
> > > -=-=-=-=-=-=-=-=-=-
> > > William David Armstrong <----. Of course it runs
> > > Bio Systems Security.Networking <----|============================
> > > Hinodeinfo Soluções em Informática <----' NetBSD, OpenBSD or FreeBSD
> > > ICQ 27550645
> > > MSN / GT Ψ biosystems ∆ gmail . com Ψ
> > > --------------------------------------
> > >
> >
>
>
> --
> -=-=-=-=-=-=-=-=-=-
> William David Armstrong <----. Of course it runs
> Bio Systems Security.Networking <----|============================
> Hinodeinfo Soluções em Informática <----' NetBSD, OpenBSD or FreeBSD
> ICQ 27550645 MSN / GT Ψ biosystems ∆ gmail . com Ψ
> --------------------------------------
>
