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

    WAN interface keeps dropping after upgrade to 1.2.1

    Scheduled Pinned Locked Moved General pfSense Questions
    43 Posts 6 Posters 21.5k 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.
    • R
      rigius
      last edited by

      @wallabybob:

      I'm using a Zyxel 660H-61 as a router, not half bridge.

      Ok. So it's pointless to try router mode here, something I had been considering. Thankyou.

      MAYBE a similar thing has happened with your box and you have an older box and have been looking at newer documentation.

      Yes, that's possible. That's why I said that I was not sure of my network cards ;-)

      I have sent the question to Fabiatech. They say on their site that they will reply in 24 hours…

      I think the 8100C should be controlled by the rl driver because I've been looking at the re and rl driver sources recently. The rl driver appears to include recognition of an 8100 device.

      Even if system.log says that our box has RTL8139 ports, they are controlled byt the rl driver (rl0 & rl1). That seems to indicate that they are 8100C.

      1 Reply Last reply Reply Quote 0
      • R
        rigius
        last edited by

        @wallabybob:

        This sounds like a hardware problem or a driver bug. Do you get the same behaviour on other ports?

        Yes, at least on the 10/100 ports (RTL8100C or RTL8139).

        1 Reply Last reply Reply Quote 0
        • R
          rigius
          last edited by

          @wallabybob:

          When this happens can you ssh into the pfSense box?

          Yes.

          If you can login while this is happening, type command

          netstat -i -I rl1

          a few times and watch what happens to the rl1 error counters.

          Not very much, I think:

          
          Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  Coll
          rl1    1500 <link#2>00:04:a7:__:__:__    54513     0    27948     0    94
          rl1    1500 fe80:2::___:_ fe80:2::___:____:        0     -        1     -     -
          rl1    1500 80.___.___.0   LRouen-___-___-9-2      410     -        0     -     -
          [... after about 5 minutes]
          Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  Coll
          rl1    1500 <link#2>00:04:a7:__:__:__    54520     0    27954     0    94
          rl1    1500 fe80:2::___:_ fe80:2::___:____:        0     -        1     -     -
          rl1    1500 80.___.___.0   LRouen-___-___-9-2      582     -        0     -     -</link#2></link#2> 
          
          1 Reply Last reply Reply Quote 0
          • R
            rigius
            last edited by

            Ok. I have no more ideas.

            No answer from Fabiatech after their "guaranteed 24 hour reply delay" (not too surprised).

            "pciconf -lv" shows:

            
            rl0@pci0:0:12:0:	class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00
                class      = network
                subclass   = ethernet
            
            

            So apparently the 10/100 cards are "RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter" and they seem to be supported by the "rl" driver. I have found several posts showing problems with this card under freeBSD 7.0 that were solved after upgrading to freeBSD 7.1 (like this one: <http: daemonforums.org="" showthread.php?p="10070">.

            I'm not very willing to go back to 1.2, so any idea of when pfsense 1.2.3 will be released?</http:>

            1 Reply Last reply Reply Quote 0
            • jahonixJ
              jahonix
              last edited by

              Have you tried a current pfSense 1.2.3 Pre-Release snapshot to see if it helps with your problem?
              http://blog.pfsense.org/?p=364

              1 Reply Last reply Reply Quote 0
              • R
                rigius
                last edited by

                No. This is a "production environment" that keeps working even if it's somewhat handicapped and the statement "Please test in a non-production environment and let us know how it goes on the forum." scares me. Unfortunately, I have only one of these Fabiatech devices :-(

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

                  If it is a on board nic I would check for bios update.

                  /Perry
                  doc.pfsense.org

                  1 Reply Last reply Reply Quote 0
                  • M
                    MrEmbedded
                    last edited by

                    I am having a similar issue with a new 1.2.2 box.  The buildup was done on an old Dell Optiplex 260 with P4 and 512MB RAM plus the onboad NIC (lan).  Its a multiwan setup with pppoe on the wan and cable on opt1.  Both are on pci dlink DFE-538TX cards (brand spanking new).  The vr0 card (pppoe) has a bunch of collisions.  After 7 hours the total collision count is around 1700.  I get the same style arpresolve messages in the logs and the load balancer is constantly up/downing links (in the logs).  I plan to leave things alone overnight to see if it is a provider issue that sorts itself out as I am not sure what else to look at.  That is the only thing that is wrong with this box, everything else is working fine it seems.  For now I have added some outgoing lan rules to direct the critical traffic toward the cable modem interface until I figure this out.

                    One more thing, the modem is at least 4 years old on the pppoe connection so I am wondering if it is starting to get flakey.

                    1 Reply Last reply Reply Quote 0
                    • R
                      rigius
                      last edited by

                      @Perry:

                      If it is a on board nic I would check for bios update.

                      Done. I was already on the last version.

                      I was also having problems with DNS resolution (SLOOOOOW, in the order of several seconds), so I have transfered everything I could to the working WAN connection and now I'm rebooting the pfsense box from time to time and just waiting for the 1.2.3 release, hoping that it will fix this problem.

                      1 Reply Last reply Reply Quote 0
                      • M
                        MrEmbedded
                        last edited by

                        My issue was completely resolved by a modem replacement.  Thought I would mention that.

                        1 Reply Last reply Reply Quote 0
                        • R
                          rigius
                          last edited by

                          Hi,

                          I tried to make half bridge work on OPT1 (apparently Realtek 8139 recognised as rl1) with versions 1.2.1 and 1.2.3-RC1 using two different modems (Linksys AM200 and Zyxel P660R). I was not successful, even if everything worked perfectly with pfsense v1.2. Finally, I put one of the modems on router mode and pfsense in its DMZ and since then everything is working fine.

                          Cheers,

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