WAN interface keeps dropping after upgrade to 1.2.1
-
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).
-
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> -
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 = ethernetSo 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:>
-
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 -
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 :-(
-
If it is a on board nic I would check for bios update.
-
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.
-
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.
-
My issue was completely resolved by a modem replacement. Thought I would mention that.
-
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,
