Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    1.2 Beta WAN "Port bouncing" / random disconnects - DUAL WAN

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    16 Posts 4 Posters 7.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      cmb
      last edited by

      Could you post the exact system logs you're seeing? This sounds like a regression between FreeBSD 6.1 and 6.2. I'd like to look and see if it's a known issue, and the exact logs will help me Google. :)

      1 Reply Last reply Reply Quote 0
      • S
        SMachiz
        last edited by

        I just re-upgraded to the latest snapshot from 1.0.1; as soon as it starts happening again I'll grab the logs.  Is there any other info regarding the hardware platform or something else that might be useful?

        Sam

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by

          One other thing - the entire contents from dmesg on status.php.

          1 Reply Last reply Reply Quote 0
          • S
            SMachiz
            last edited by

            DMESG
            
            Copyright (c) 1992-2007 The FreeBSD Project.
            Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
            	The Regents of the University of California. All rights reserved.
            FreeBSD is a registered trademark of The FreeBSD Foundation.
            FreeBSD 6.2-RELEASE-p5 #0: Mon May 28 21:51:22 EDT 2007
                sullrich@builder6.pfsense.com:/usr/obj.pfSense/usr/src/sys/pfSense.6
            Timecounter "i8254" frequency 1193182 Hz quality 0
            CPU: VIA C7 Esther+RNG+AES+AES-CTR+SHA1+SHA256+RSA (1000.01-MHz 686-class CPU)
              Origin = "CentaurHauls"  Id = 0x6a9  Stepping = 9
              Features=0xa7c9baff <fpu,vme,de,pse,tsc,msr,pae,mce,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>Features2=0x181 <sse3,est,tm2>real memory  = 1005453312 (958 MB)
            avail memory = 974585856 (929 MB)
            ACPI APIC Table: <cn700  awrdacpi="">ioapic0 <version 0.3="">irqs 0-23 on motherboard
            wlan: mac acl policy registered
            kbd1 at kbdmux0
            ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
            acpi0: <cn700 awrdacpi="">on motherboard
            acpi0: Power Button (fixed)
            can't fetch resources for \\_SB_.PCI0.UAR1 - AE_BAD_DATA
            can't fetch resources for \\_SB_.PCI0.UAR2 - AE_BAD_DATA
            Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
            acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
            cpu0: <acpi cpu="">on acpi0
            acpi_perf0: <acpi cpu="" frequency="" control="">on cpu0
            acpi_throttle0: <acpi cpu="" throttling="">on cpu0
            acpi_button0: <power button="">on acpi0
            pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
            pci0: <acpi pci="" bus="">on pcib0
            pcib1: <pci-pci bridge="">at device 1.0 on pci0
            pci1: <pci bus="">on pcib1
            pci1: <display, vga="">at device 0.0 (no driver attached)
            re0: <realtek 8169sc="" 8110sc="" single-chip="" gigabit="" ethernet="">port 0xf200-0xf2ff mem 0xfdfff000-0xfdfff0ff irq 18 at device 9.0 on pci0
            miibus0: <mii bus="">on re0
            rgephy0: <rtl8169s 8110s="" media="" interface="">on miibus0
            rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
            re0: Ethernet address: 00:30:18:a6:2a:ee
            re0: [FAST]
            fwohci0: <via fire="" ii="" (vt6306)="">port 0xff00-0xff7f mem 0xfdffe000-0xfdffe7ff irq 19 at device 10.0 on pci0
            fwohci0: OHCI version 1.10 (ROM=1)
            fwohci0: No. of Isochronous channels is 4.
            fwohci0: EUI64 00:30:18:00:00:ab:92:cd
            fwohci0: Phy 1394a available S400, 2 ports.
            fwohci0: Link S400, max_rec 2048 bytes.
            firewire0: <ieee1394(firewire) bus="">on fwohci0
            sbp0: <sbp-2 scsi="" over="" firewire="">on firewire0
            fwohci0: Initiate bus reset
            fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
            firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
            firewire0: bus manager 0 (me)
            re1: <realtek 8169sc="" 8110sc="" single-chip="" gigabit="" ethernet="">port 0xf000-0xf0ff mem 0xfdffd000-0xfdffd0ff irq 19 at device 11.0 on pci0
            miibus1: <mii bus="">on re1
            rgephy1: <rtl8169s 8110s="" media="" interface="">on miibus1
            rgephy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
            re1: Ethernet address: 00:30:18:a6:2a:ef
            re1: [FAST]
            re2: <realtek 8169sc="" 8110sc="" single-chip="" gigabit="" ethernet="">port 0xec00-0xecff mem 0xfdffc000-0xfdffc0ff irq 16 at device 12.0 on pci0
            miibus2: <mii bus="">on re2
            rgephy2: <rtl8169s 8110s="" media="" interface="">on miibus2
            rgephy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
            re2: Ethernet address: 00:30:18:a6:2a:f0
            re2: [FAST]
            atapci0: <via 6420="" sata150="" controller="">port 0xfe00-0xfe07,0xfd00-0xfd03,0xfc00-0xfc07,0xfb00-0xfb03,0xfa00-0xfa0f,0xee00-0xeeff irq 20 at device 15.0 on pci0
            ata2: <ata 0="" channel="">on atapci0
            ata3: <ata 1="" channel="">on atapci0
            atapci1: <via 8237="" udma133="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf900-0xf90f at device 15.1 on pci0
            ata0: <ata 0="" channel="">on atapci1
            ata1: <ata 1="" channel="">on atapci1
            uhci0: <via 83c572="" usb="" controller="">port 0xf800-0xf81f irq 21 at device 16.0 on pci0
            uhci0: [GIANT-LOCKED]
            usb0: <via 83c572="" usb="" controller="">on uhci0
            usb0: USB revision 1.0
            uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
            uhub0: 2 ports with 2 removable, self powered
            uhci1: <via 83c572="" usb="" controller="">port 0xf700-0xf71f irq 21 at device 16.1 on pci0
            uhci1: [GIANT-LOCKED]
            usb1: <via 83c572="" usb="" controller="">on uhci1
            usb1: USB revision 1.0
            uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
            uhub1: 2 ports with 2 removable, self powered
            uhci2: <via 83c572="" usb="" controller="">port 0xf600-0xf61f irq 21 at device 16.2 on pci0
            uhci2: [GIANT-LOCKED]
            usb2: <via 83c572="" usb="" controller="">on uhci2
            usb2: USB revision 1.0
            uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
            uhub2: 2 ports with 2 removable, self powered
            uhci3: <via 83c572="" usb="" controller="">port 0xf500-0xf51f irq 21 at device 16.3 on pci0
            uhci3: [GIANT-LOCKED]
            usb3: <via 83c572="" usb="" controller="">on uhci3
            usb3: USB revision 1.0
            uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
            uhub3: 2 ports with 2 removable, self powered
            ehci0: <via vt6202="" usb="" 2.0="" controller="">mem 0xfdffb000-0xfdffb0ff irq 21 at device 16.4 on pci0
            ehci0: [GIANT-LOCKED]
            usb4: waiting for BIOS to give up control
            usb4: timed out waiting for BIOS
            usb4: EHCI version 1.0
            usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
            usb4: <via vt6202="" usb="" 2.0="" controller="">on ehci0
            usb4: USB revision 2.0
            uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
            uhub4: 8 ports with 8 removable, self powered
            isab0: <pci-isa bridge="">at device 17.0 on pci0
            isa0: <isa bus="">on isab0
            pci0: <multimedia, audio="">at device 17.5 (no driver attached)
            vr0: <via 10="" vt6102="" rhine="" ii="" 100basetx="">port 0xe800-0xe8ff mem 0xfdffa000-0xfdffa0ff irq 23 at device 18.0 on pci0
            miibus3: <mii bus="">on vr0
            ukphy0: <generic ieee="" 802.3u="" media="" interface="">on miibus3
            ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
            vr0: Ethernet address: 00:30:18:b0:59:75
            acpi_tz0: <thermal zone="">on acpi0
            speaker0: <pc speaker="">port 0x61 on acpi0
            fdc0: <floppy drive="" controller="">port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
            fdc0: [FAST]
            ppc0: <standard parallel="" printer="" port="">port 0x378-0x37f irq 7 on acpi0
            ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
            ppbus0: <parallel port="" bus="">on ppc0
            lpt0: <printer>on ppbus0
            lpt0: Interrupt-driven port
            ppi0: <parallel i="" o="">on ppbus0
            pmtimer0 on isa0
            atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
            atkbd0: <at keyboard="">irq 1 on atkbdc0
            kbd0 at atkbd0
            atkbd0: [GIANT-LOCKED]
            sc0: <system console="">at flags 0x100 on isa0
            sc0: VGA <16 virtual consoles, flags=0x300>
            sio0: configured irq 4 not in bitmap of probed irqs 0
            sio0: port may not be enabled
            sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
            sio0: type 16550A
            sio1 at port 0x2f8-0x2ff irq 3 on isa0
            sio1: type 16550A
            vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
            uhid0: ITUNER INC USB-LCD-20x2, rev 2.00/0.01, addr 2, iclass 3/0
            Timecounter "TSC" frequency 1000007517 Hz quality 800
            Timecounters tick every 1.000 msec
            Fast IPsec: Initialized Security Association Processing.
            ad2: 1953MB <sandisk sdcfx-2048="" hdx="" 3.22="">at ata1-master PIO4
            Trying to mount root from ufs:/dev/ad2s1a
            
                 ___
             ___/ f \\
            / p \\___/ Sense
            \\___/   \\
                \\___/
            
            Welcome to pfSense 1.2-BETA-1-TESTING-SNAPSHOT-05-27-2007 on the 'pfSense' platform...
            
            Mounting filesystems...
             done.
            Creating symlinks...
            .
            .
            .
            done.
            Launching PHP init system...
             done.
            Initializing...
            .
            .
            .
            .
            .
            .
            .
            .
            .
            .
            .
            .
            .
            .
            .
             done.
            Starting device manager (devd)...
            done.
            Loading configuration...
            .
            .
            .
            done.
            Updating configuration...
            done.
            Cleaning backup cache...
            done.
            Setting up extended sysctls...
            done.
            Syncing user passwords...
            done.
            Starting Secure Shell Services...
            done.
            Setting timezone...
            done.
            Starting syslog...
            done.
            Configuring LAN interface...
            re0: link state changed to DOWN
            re1: link state changed to UP
            re2: link state changed to UP
            vr0: link state changed to UP
            done.
            Configuring WAN interface...
            re2: link state changed to DOWN
            re2: link state changed to UP
            re2: link state changed to DOWN
            re2: link state changed to UP
            re2: link state changed to DOWN
            done.
            Configuring OPT interfaces...
            re1: link state changed to DOWN
            done.
            Configuring CARP interfaces...
            done.
            Syncing system time before startup...
            re2: link state changed to UP
            re1: link state changed to UP
            done.
            pflog0: promiscuous mode enabled
            arplookup 10.31.9.1 failed: host is not on local network
            Configuring firewall...
            .
            .
            .
            done.
            Starting webConfigurator...
            done.
            Starting DHCP service...
            done.
            Configuring PPTP VPN service...
            done
            Setting up microcode and tx/rx offloading...
            done.
            Starting FTP helpers...
            done.
            Generating RRD graphs...
            done.
            Starting DHCP service...
            done.
            Starting OpenNTP time client...
            done.
            Starting CRON...
            done.
            Syncing packages:
            
            .
            Executing rc.d items...
             Starting /usr/local/etc/rc.d/miniupnpd.sh...
            done.
            appending output to nohup.out
            Bootup complete
            arplookup 10.31.9.1 failed: host is not on local network
            arplookup 10.31.9.1 failed: host is not on local network
            arplookup 10.31.9.1 failed: host is not on local network</sandisk></generic></system></at></keyboard></parallel></printer></parallel></standard></floppy></pc></thermal></generic></mii></via></multimedia,></isa></pci-isa></via></via></via></via></via></via></via></via></via></via></ata></ata></via></ata></ata></via></rtl8169s></mii></realtek></rtl8169s></mii></realtek></sbp-2></ieee1394(firewire)></via></rtl8169s></mii></realtek></display,></pci></pci-pci></acpi></acpi></power></acpi></acpi></acpi></cn700></version></cn700 ></sse3,est,tm2></fpu,vme,de,pse,tsc,msr,pae,mce,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe> 
            

            arplookup 10.31.9.1 failed: host is not on local network repeats another hundred times or so - but that's a function of the way Time Warner NYC sets up their RoadRunner service I believe.

            1 Reply Last reply Reply Quote 0
            • S
              SMachiz
              last edited by

              Almost on command…

              May 29 23:22:47 	dhclient[7327]: DHCPREQUEST on re2 to 255.255.255.255 port 67
              May 29 23:22:47 	kernel: re2: link state changed to DOWN
              May 29 23:22:47 	kernel: re2: link state changed to UP
              May 29 23:22:45 	kernel: re2: link state changed to DOWN
              May 29 23:22:45 	dhclient[7205]: exiting.
              May 29 23:22:45 	dhclient[7205]: exiting.
              May 29 23:22:45 	dhclient[7205]: short write: wanted 20 got 0 bytes
              May 29 23:22:45 	dhclient[7205]: short write: wanted 20 got 0 bytes
              May 29 23:22:44 	slbd[6543]: Service balance changed status, reloading filter policy
              May 29 23:22:44 	slbd[6543]: Service wan2 changed status, reloading filter policy
              May 29 23:22:44 	slbd[6543]: Service wan1 changed status, reloading filter policy
              May 29 23:22:44 	last message repeated 2 times
              May 29 23:22:44 	slbd[6543]: ICMP poll succeeded for 69.9.160.XXX, marking service UP
              May 29 23:22:44 	kernel: re2: link state changed to UP
              May 29 23:22:42 	php: : HOTPLUG: Configuring wan interface
              May 29 23:22:42 	php: : Processing -
              May 29 23:22:42 	php: : Hotplug event detected for start but ignoring since interface is not set for DHCP
              May 29 23:22:42 	php: : Processing start -
              May 29 23:22:42 	kernel: re2: link state changed to DOWN
              May 29 23:22:41 	dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
              May 29 23:22:41 	dhcpd: All rights reserved.
              May 29 23:22:41 	dhcpd: Copyright 2004-2006 Internet Systems Consortium.
              May 29 23:22:41 	dhcpd: Internet Systems Consortium DHCP Server V3.0.5
              May 29 23:22:40 	kernel: re2: link state changed to UP
              May 29 23:22:37 	dhclient[7131]: bound to 66.234.57.XXX-- renewal in 39280 seconds.
              May 29 23:22:37 	kernel: re2: link state changed to DOWN
              May 29 23:22:37 	dhclient[7131]: DHCPACK from 10.35.128.1
              May 29 23:22:37 	kernel: re2: link state changed to UP
              May 29 23:22:36 	kernel: arpresolve: can't allocate route for 66.234.57.XXX
              May 29 23:22:36 	kernel: arpresolve: can't allocate route for 66.234.57.XXX
              May 29 23:22:35 	dhclient[7131]: DHCPREQUEST on re2 to 255.255.255.255 port 67
              May 29 23:22:35 	kernel: re2: link state changed to DOWN
              May 29 23:22:35 	kernel: re2: link state changed to UP
              May 29 23:22:33 	slbd[6543]: Service balance changed status, reloading filter policy
              May 29 23:22:33 	slbd[6543]: Service wan1 changed status, reloading filter policy
              May 29 23:22:33 	slbd[6543]: ICMP poll failed for 69.9.160.XXX, marking service DOWN
              May 29 23:22:33 	slbd[6543]: ICMP poll failed for 69.9.160.XXX, marking service DOWN
              May 29 23:22:33 	slbd[6543]: Service wan2 changed status, reloading filter policy
              May 29 23:22:33 	slbd[6543]: ICMP poll failed for 69.9.160.XXX, marking service DOWN
              May 29 23:22:33 	kernel: re2: link state changed to DOWN
              
              1 Reply Last reply Reply Quote 0
              • S
                SMachiz
                last edited by

                For what it's worth - restarting pfsense seems to fix it for another 18-24 hours; restarting the cable modem (re2) has no effect.  Also, before you ask, the host it's monitoring with ICMP is online :)

                Sam

                1 Reply Last reply Reply Quote 0
                • S
                  SMachiz
                  last edited by

                  any other data or info I can provide?  I tried the whole googling / forum search with no real success. I'm also not really familiar with freebsd outside of having used pfsense though :)

                  1 Reply Last reply Reply Quote 0
                  • P
                    PaulS
                    last edited by

                    I am seeing this same behavior.  I am running:
                    "1.2-RELEASE built on Sun Feb 24 17:04:58 EST 2008" on a test box with no traffic passing (no DUAL WAN).  The common thread here seems to be the network cards.  I am using an onboard Intel PRO100/VE(kernel: fxp0: <intel 100="" 82801ba="" cam="" (ich2="" 3)="" pro="" ethernet="">) and 3 netgear ga311 (kernel: re0: <realtek 8169s="" single-chip="" gigabit="" ethernet="">).  All the links start to bounce after an undetermined time has passed.  A reboot resolves the issue for a short time.  I have tried 2 switches (HP Procurve and a Linksys) and it doesn't resolve it.  I am waiting for it to start bouncing again to post the logs but it seems to happen every 3 seconds once it starts.

                    Thanks</realtek></intel>

                    1 Reply Last reply Reply Quote 0
                    • P
                      PaulS
                      last edited by

                      Jul 7 22:21:46 SnortStartup[14218]: Ram free BEFORE starting Snort: 34M – Ram free AFTER starting Snort: 34M -- Mode lowmem -- Snort memory usage:
                      Jul 7 22:22:40 kernel: re0: promiscuous mode enabled
                      Jul 7 22:22:40 kernel: re0: link state changed to DOWN
                      Jul 7 22:22:40 kernel: re0: promiscuous mode disabled
                      Jul 7 22:22:42 kernel: re0: promiscuous mode enabled
                      Jul 7 22:22:44 kernel: re0: link state changed to UP
                      Jul 7 22:22:47 check_reload_status: rc.linkup starting
                      Jul 7 22:22:48 php: : Processing re0 - start
                      Jul 7 22:22:48 php: : DEVD Ethernet attached event for re0
                      Jul 7 22:22:48 kernel: re0: link state changed to DOWN
                      Jul 7 22:22:48 php: : HOTPLUG: Configuring wan interface re0
                      Jul 7 22:22:48 dhclient[251]: connection closed
                      Jul 7 22:22:48 dhclient[251]: connection closed
                      Jul 7 22:22:48 dhclient[251]: exiting.
                      Jul 7 22:22:48 dhclient[251]: exiting.
                      Jul 7 22:22:50 kernel: re0: link state changed to UP
                      Jul 7 22:22:51 kernel: re0: link state changed to DOWN
                      Jul 7 22:22:53 kernel: re0: link state changed to UP
                      Jul 7 22:22:54 kernel: re0: link state changed to DOWN
                      Jul 7 22:22:54 dhclient[14431]: DHCPREQUEST on re0 to 255.255.255.255 port 67
                      Jul 7 22:22:55 kernel: re0: link state changed to UP
                      Jul 7 22:22:57 last message repeated 2 times
                      Jul 7 22:22:57 dhclient[14431]: DHCPACK from 192.168.10.3
                      Jul 7 22:22:57 dhclient[14431]: Bogus domain search list 15: hope_domain.local (hope_domain.local)
                      Jul 7 22:22:57 dhclient[14431]: Bogus domain search list 15: hope_domain.local (hope_domain.local)
                      Jul 7 22:22:58 kernel: re0: link state changed to DOWN
                      Jul 7 22:22:58 dhclient[14431]: bound to 192.168.10.204 – renewal in 28800 seconds.
                      Jul 7 22:22:59 kernel: re0: link state changed to UP
                      Jul 7 22:23:00 dnsmasq[501]: reading /etc/resolv.conf
                      Jul 7 22:23:00 dnsmasq[501]: using nameserver 192.168.1.3#53
                      Jul 7 22:23:00 dnsmasq[501]: using nameserver 192.168.10.3#53
                      Jul 7 22:23:00 dnsmasq[501]: exiting on receipt of SIGTERM
                      Jul 7 22:23:01 dnsmasq[14519]: started, version 2.39 cachesize 150
                      Jul 7 22:23:01 dnsmasq[14519]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
                      Jul 7 22:23:01 dnsmasq[14519]: reading /etc/resolv.conf
                      Jul 7 22:23:01 dnsmasq[14519]: using nameserver 192.168.1.3#53
                      Jul 7 22:23:01 dnsmasq[14519]: using nameserver 192.168.10.3#53
                      Jul 7 22:23:01 dnsmasq[14519]: read /etc/hosts - 2 addresses
                      Jul 7 22:23:01 kernel: re0: link state changed to DOWN
                      Jul 7 22:23:01 php: : Processing start -
                      Jul 7 22:23:01 php: : Not a valid interface action ""
                      Jul 7 22:23:01 php: : Processing -
                      Jul 7 22:23:01 php: : Not a valid interface action ""
                      Jul 7 22:23:01 check_reload_status: rc.newwanip starting
                      Jul 7 22:23:02 php: : Informational: rc.newwanip is starting re0.
                      Jul 7 22:23:02 php: : rc.newwanip working with (IP address: 192.168.10.204) (interface: wan) (interface real: re0).
                      Jul 7 22:23:03 kernel: re0: link state changed to UP
                      Jul 7 22:23:07 php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - 192.168.10.204.
                      Jul 7 22:23:07 php: : Creating rrd update script
                      Jul 7 22:23:07 php: : Configuring slbd
                      Jul 7 22:23:07 check_reload_status: reloading filter
                      Jul 7 22:23:09 check_reload_status: updating dyndns
                      Jul 7 22:23:15 check_reload_status: rc.linkup starting
                      Jul 7 22:23:16 php: : Processing re0 - start
                      Jul 7 22:23:16 php: : DEVD Ethernet attached event for re0
                      Jul 7 22:23:16 kernel: re0: link state changed to DOWN
                      Jul 7 22:23:16 php: : HOTPLUG: Configuring wan interface re0
                      Jul 7 22:23:19 kernel: re0: link state changed to UP
                      Jul 7 22:23:19 dhclient[14489]: short write: wanted 20 got 0 bytes
                      Jul 7 22:23:19 dhclient[14489]: short write: wanted 20 got 0 bytes
                      Jul 7 22:23:19 dhclient[14489]: exiting.
                      Jul 7 22:23:19 dhclient[14489]: exiting.
                      Jul 7 22:23:19 kernel: re0: link state changed to DOWN
                      Jul 7 22:23:21 kernel: re0: link state changed to UP
                      Jul 7 22:23:22 kernel: re0: link state changed to DOWN
                      Jul 7 22:23:22 dhclient[14902]: DHCPREQUEST on re0 to 255.255.255.255 port 67
                      Jul 7 22:23:24 kernel: re0: link state changed to UP
                      Jul 7 22:23:27 last message repeated 2 times
                      Jul 7 22:23:32 dhclient[14902]: DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 2
                      Jul 7 22:23:32 dhclient[14902]: DHCPOFFER from 192.168.10.3
                      Jul 7 22:23:32 dhclient[14902]: Bogus domain search list 15: hope_domain.local (hope_domain.local)
                      Jul 7 22:23:32 dhclient[14902]: Bogus domain search list 15: hope_domain.local (hope_domain.local)
                      Jul 7 22:23:32 dhclient[14902]: DHCPOFFER from 192.168.10.1
                      Jul 7 22:23:34 dhclient[14902]: DHCPREQUEST on re0 to 255.255.255.255 port 67
                      Jul 7 22:23:34 dhclient[14902]: DHCPACK from 192.168.10.3
                      Jul 7 22:23:34 dhclient[14902]: Bogus domain search list 15: hope_domain.local (hope_domain.local)
                      Jul 7 22:23:34 dhclient[14902]: Bogus domain search list 15: hope_domain.local (hope_domain.local)
                      Jul 7 22:23:34 kernel: re0: link state changed to DOWN
                      Jul 7 22:23:34 dhclient[14902]: bound to 192.168.10.204 – renewal in 28800 seconds.
                      Jul 7 22:23:36 kernel: re0: link state changed to UP
                      Jul 7 22:23:36 dnsmasq[14519]: reading /etc/resolv.conf
                      Jul 7 22:23:36 dnsmasq[14519]: using nameserver 192.168.1.3#53
                      Jul 7 22:23:36 dnsmasq[14519]: using nameserver 192.168.10.3#53
                      Jul 7 22:23:36 dnsmasq[14519]: exiting on receipt of SIGTERM
                      Jul 7 22:23:37 dnsmasq[15017]: started, version 2.39 cachesize 150
                      Jul 7 22:23:37 dnsmasq[15017]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
                      Jul 7 22:23:37 dnsmasq[15017]: reading /etc/resolv.conf
                      Jul 7 22:23:37 dnsmasq[15017]: using nameserver 192.168.1.3#53
                      Jul 7 22:23:37 dnsmasq[15017]: using nameserver 192.168.10.3#53
                      Jul 7 22:23:37 dnsmasq[15017]: read /etc/hosts - 2 addresses
                      Jul 7 22:23:38 kernel: re0: link state changed to DOWN
                      Jul 7 22:23:38 php: : Processing start -
                      Jul 7 22:23:38 php: : Not a valid interface action ""
                      Jul 7 22:23:38 php: : Processing -
                      Jul 7 22:23:38 php: : Not a valid interface action ""
                      Jul 7 22:23:38 check_reload_status: rc.newwanip starting
                      Jul 7 22:23:38 php: : Informational: rc.newwanip is starting re0.
                      Jul 7 22:23:38 php: : rc.newwanip working with (IP address: 192.168.10.204) (interface: wan) (interface real: re0).
                      Jul 7 22:23:41 kernel: re0: link state changed to UP

                      1 Reply Last reply Reply Quote 0
                      • P
                        PaulS
                        last edited by

                        Sorry to make all these separate posts but I think I found the cause:

                        fxp0: promiscuous mode disabled
                        fxp0: promiscuous mode enabled
                        fxp0: promiscuous mode disabled
                        pflog0: promiscuous mode disabled
                        pflog0: promiscuous mode enabled
                        re0: promiscuous mode enabled
                        re0: link state changed to DOWN
                        re0: promiscuous mode disabled
                        re0: promiscuous mode enabled
                        re0: link state changed to UP
                        re0: link state changed to DOWN
                        re0: link state changed to UP
                        re0: link state changed to DOWN
                        re0: link state changed to UP
                        re0: link state changed to DOWN
                        re0: link state changed to UP
                        re0: link state changed to DOWN
                        re0: link state changed to UP
                        re0: link state changed to DOWN
                        re0: link state changed to UP
                        re0: link state changed to DOWN
                        re0: link state changed to UP

                        As soon as the re0 goes promiscuous it blows up.  I see the same from the above log.  That is the RealTek 8169S Single-chip Gigabit Ethernet Netgear card.  Any thoughts as to where I go?

                        1 Reply Last reply Reply Quote 0
                        • P
                          PaulS
                          last edited by

                          This is beginning to feel like more of a blog then a forum but in case this helps others:

                          I removed the Realtek 8169s based netgear ga311 nics from the system and replaced them with a single 3com 3c905tx.  I reconfigured and retested promiscous mode with darkstat and the 3com and everything is working now.  There appears to be something with the re driver and my setup which is an older micron P4 1.4 ghz tower.  I tried disabling ACPI but it had no effect.  Goodluck,
                          Paul

                          1 Reply Last reply Reply Quote 0
                          • K
                            kpa
                            last edited by

                            I'm probably not the only one saying this but imo realtek nics are junk and should not be used in firewall/server systems. Intel nics are recommended with pfSense and for a good reason too.

                            1 Reply Last reply Reply Quote 0
                            • P
                              PaulS
                              last edited by

                              Thanks for the feedback.  This is just a test box using what I had on hand.  I prefer intel nics but I would be hard-pressed to fault the realteks in this case.  I think they should be removed from the HCL.  Simply enabling promiscuous mode shouldn't cause a meltdown like this.  I looks like a freebsd driver issue though and not a pfsense specific issue as far as I can tell.  I just feel bad for anyone using an onboard 8169 in a small form factor setup.

                              Paul

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.