Navigation

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

    WAN interface going DOWN and UP

    Hardware
    2
    7
    3357
    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.
    • L
      lklaus last edited by

      Hi,

      I did a fresh install of 1.2.3 on my Alix board this morning, and since then I'll have those DOWN's and UP's. I disabled the hardware checksum offload, but to no avail. I also changed the cable. The release candidates were running flawlessly (I started with a release from July, and did an update in October)

      Any ideas, except going back?

      Klaus

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

        What exactly do you mean by down and up? Post your system log.

        1 Reply Last reply Reply Quote 0
        • L
          lklaus last edited by

          Sorry, forgot this…

          lot's of:

          Dec 12 19:47:52 alix kernel: vr1: link state changed to DOWN
          Dec 12 19:47:52 alix racoon: INFO: 10.64.64.6[500] used as isakmp port (fd=14)
          Dec 12 19:47:52 alix racoon: INFO: 10.64.64.2[500] used as isakmp port (fd=15)
          Dec 12 19:47:52 alix racoon: INFO: 93.104.186.241[500] used as isakmp port (fd=16)
          Dec 12 19:47:52 alix racoon: INFO: 127.0.0.1[500] used as isakmp port (fd=17)
          Dec 12 19:47:52 alix racoon: INFO: 192.168.0.75[500] used as isakmp port (fd=18)
          Dec 12 19:47:55 alix kernel: vr1: link state changed to UP
          Dec 12 19:47:55 alix racoon: INFO: 10.64.64.6[500] used as isakmp port (fd=14)
          Dec 12 19:47:55 alix racoon: INFO: 10.64.64.2[500] used as isakmp port (fd=15)
          Dec 12 19:47:55 alix racoon: INFO: 93.104.186.241[500] used as isakmp port (fd=16)
          Dec 12 19:47:55 alix racoon: INFO: 127.0.0.1[500] used as isakmp port (fd=17)
          Dec 12 19:47:55 alix racoon: INFO: 192.168.0.75[500] used as isakmp port (fd=18)
          Dec 12 19:47:59 alix check_reload_status: rc.linkup starting
          Dec 12 19:48:01 alix php: : Processing vr1 - start
          Dec 12 19:48:01 alix php: : DEVD Ethernet attached event for vr1
          Dec 12 19:48:01 alix php: : Processing start -
          Dec 12 19:48:01 alix php: : Processing  -

          Regularly:
          …
          Dec 12 21:22:37 alix kernel: vr1: link state changed to UP
          Dec 12 21:22:46 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:22:48 alix kernel: vr1: link state changed to UP
          Dec 12 21:25:09 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:25:11 alix kernel: vr1: link state changed to UP
          Dec 12 21:25:19 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:25:21 alix kernel: vr1: link state changed to UP
          Dec 12 21:25:33 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:25:35 alix kernel: vr1: link state changed to UP
          Dec 12 21:25:56 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:25:58 alix kernel: vr1: link state changed to UP
          Dec 12 21:26:05 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:26:08 alix kernel: vr1: link state changed to UP
          Dec 12 21:28:26 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:28:28 alix kernel: vr1: link state changed to UP
          Dec 12 21:30:14 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:30:16 alix kernel: vr1: link state changed to UP
          Dec 12 21:31:12 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:31:15 alix kernel: vr1: link state changed to UP
          Dec 12 21:31:24 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:31:26 alix kernel: vr1: link state changed to UP
          Dec 12 21:31:34 alix kernel: vr1: link state changed to DOWN
          Dec 12 21:31:36 alix kernel: vr1: link state changed to UP

          vr1 is the WAN link, using pppoe. But as stated before, this did not happen with RCs up to (in my case) october...

          1 Reply Last reply Reply Quote 0
          • L
            lklaus last edited by

            Still more information… I tested yet another cable, and I switched LAN and WAN ports (incl. cables :-). The Up/Down problem follows the WAN port, i.e. is now on the other NIC.
            WAN is using pppoe.

            I did a bios upgrade to 0.99h, but to no avail. The rest looks fairly standard to me, except probably for a wireless card
            Copyright (c) 1992-2009 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 7.2-RELEASE-p5 #0: Mon Dec  7 23:21:27 EST 2009
                sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.7.i386
            Timecounter "i8254" frequency 1193182 Hz quality 0
            CPU: Geode(TM) Integrated Processor by AMD PCS (498.05-MHz 586-class CPU)
              Origin = "AuthenticAMD"  Id = 0x5a2  Stepping = 2
              Features=0x88a93d <fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>AMD Features=0xc0400000 <mmx+,3dnow!+,3dnow!>real memory  = 268435456 (256 MB)
            avail memory = 248639488 (237 MB)
            pnpbios: Bad PnP BIOS data checksum
            wlan: mac acl policy registered
            K6-family MTRR support enabled (2 registers)
            ACPI Error (tbxfroot-0308): A valid RSDP was not found [20070320]
            ACPI: Table initialisation failed: AE_NOT_FOUND
            ACPI: Try disabling either ACPI or apic support.
            cryptosoft0: <software crypto="">on motherboard
            padlock0: No ACE support.
            pcib0: <host to="" pci="" bridge="">pcibus 0 on motherboard
            pci0: <pci bus="">on pcib0
            Geode LX: PC Engines ALIX.2 v0.99h tinyBIOS V1.4a (C)1997-2007
            pci0: <encrypt decrypt,="" entertainment="" crypto="">at device 1.2 (no driver attached)
            vr0: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1000-0x10ff mem 0xe0000000-0xe00000ff irq 10 at device 9.0 on pci0
            vr0: Quirks: 0x2
            vr0: Revision: 0x96
            miibus0: <mii bus="">on vr0
            ukphy0: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus0
            ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
            vr0: Ethernet address: 00:0d:b9:14:20:e4
            vr0: [ITHREAD]
            vr1: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1400-0x14ff mem 0xe0040000-0xe00400ff irq 15 at device 11.0 on pci0
            vr1: Quirks: 0x2
            vr1: Revision: 0x96
            miibus1: <mii bus="">on vr1
            ukphy1: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus1
            ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
            vr1: Ethernet address: 00:0d:b9:14:20:e5
            vr1: [ITHREAD]
            ath0: <atheros 5212="">mem 0xe0080000-0xe008ffff irq 9 at device 12.0 on pci0
            ath0: [ITHREAD]
            ath0: WARNING: using obsoleted if_watchdog interface
            ath0: Ethernet address: 00:14:85:b7:c1:de
            ath0: mac 7.9 phy 4.5 radio 5.6
            isab0: <pci-isa bridge="">port 0x6000-0x6007,0x6100-0x61ff,0x6200-0x623f,0x9d00-0x9d7f,0x9c00-0x9c3f at device 15.0 on pci0
            isa0: <isa bus="">on isab0
            atapci0: <amd cs5536="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.2 on pci0
            ata0: <ata 0="" channel="">on atapci0
            ata0: [ITHREAD]
            ata1: <ata 1="" channel="">on atapci0
            ata1: [ITHREAD]
            ohci0: <ohci (generic)="" usb="" controller="">mem 0xefffe000-0xefffefff irq 12 at device 15.4 on pci0
            ohci0: [GIANT-LOCKED]
            ohci0: [ITHREAD]
            usb0: OHCI version 1.0, legacy support
            usb0: <ohci (generic)="" usb="" controller="">on ohci0
            usb0: USB revision 1.0
            uhub0: <amd 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb0
            uhub0: 4 ports with 4 removable, self powered
            ehci0: <amd cs5536="" (geode)="" usb="" 2.0="" controller="">mem 0xefffd000-0xefffdfff irq 12 at device 15.5 on pci0
            ehci0: [GIANT-LOCKED]
            ehci0: [ITHREAD]
            usb1: EHCI version 1.0
            usb1: companion controller, 4 ports each: usb0
            usb1: <amd cs5536="" (geode)="" usb="" 2.0="" controller="">on ehci0
            usb1: USB revision 2.0
            uhub1: <amd 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usb1
            uhub1: 4 ports with 4 removable, self powered
            cpu0 on motherboard
            orm0: <isa option="" rom="">at iomem 0xe0000-0xea7ff pnpid ORM0000 on isa0
            ppc0: parallel port not found.
            sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
            sio0: type 16550A, console
            sio0: [FILTER]
            sio1 at port 0x2f8-0x2ff irq 3 on isa0
            sio1: type 16550A
            sio1: [FILTER]
            Timecounter "TSC" frequency 498054650 Hz quality 800
            Timecounters tick every 10.000 msec
            IPsec: Initialized Security Association Processing.
            ad0: 977MB <sandisk sdcfh-1024="" hdx="" 3.17="">at ata0-master PIO4
            WARNING: Expected rawoffset 0, found 63
            WARNING: Expected rawoffset 0, found 922383
            Trying to mount root from ufs:/dev/ufs/pfsense0
            glxsb0: <amd geode="" lx="" security="" block="" (aes-128-cbc,="" rng)="">mem 0xefff4000-0xefff7fff irq 9 at device 1.2 on pci0
            bridge0: Ethernet address: 86:5b:e2:6e:33:82
            pflog0: promiscuous mode enabled</amd></sandisk></isa></amd></amd></amd></amd></ohci></ohci></ata></ata></amd></isa></pci-isa></atheros></generic></mii></via></generic></mii></via></encrypt></pci></host></software></mmx+,3dnow!+,3dnow!></fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>

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

              Strange, not much of anything changed between October and release. Any mpd logs or any other logs around the same time as the up/down logs?

              1 Reply Last reply Reply Quote 0
              • L
                lklaus last edited by

                Hi,

                no, nothing else. One caveat though, it looks like this happens now with pfSense-1.2.3–20090718-2234-nanobsd.img.gz also. I will make some tests, still it started with switching to 1.2.3... and probably put a switch in between, to isolate probable hardware causes. But I will not have much time until the weekend. Thank you,

                Klaus

                1 Reply Last reply Reply Quote 0
                • L
                  lklaus last edited by

                  Hi all,

                  sorry for crying wolf, but it definitely is not pfSense. I tried 3 cables, and different hardware, and the effect stays the same. Only thing was that it happene immediately after the upgrade. I'm now investigating different paths, but pfSense is – as usual -- running flawlessly

                  Klaus

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post

                  Products

                  • Platform Overview
                  • TNSR
                  • pfSense Plus
                  • Appliances

                  Services

                  • Training
                  • Professional Services

                  Support

                  • Subscription Plans
                  • Contact Support
                  • Product Lifecycle
                  • Documentation

                  News

                  • Media Coverage
                  • Press
                  • Events

                  Resources

                  • Blog
                  • FAQ
                  • Find a Partner
                  • Resource Library
                  • Security Information

                  Company

                  • About Us
                  • Careers
                  • Partners
                  • Contact Us
                  • Legal
                  Our Mission

                  We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                  Subscribe to our Newsletter

                  Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                  © 2021 Rubicon Communications, LLC | Privacy Policy