Unplugging Lan cable requires reboot to reconnect, 2.1RC1
-
The update URL is stored in the XML file so if you switch architectures then it may cause a problem, particularly on 2.1 with daily updates. If you restore an old config file make sure you manually select the update URL afterwards.
Steve
-
Where would I go to "manually select the update URL", Stephen, the WebGUI?
-
Yes, sorry.
System: Firmware: Updater Settings: Select the update URL from the drop down.Steve
-
Did an update. Now when ethernet is unplugged I still get popup errors every 2 seconds but instead of it toggling between "local area connection is now connected" and "a network cable is unplugged" it toggles between no error popup (normal desktop) to "a network cable is unplugged" popup. So I guess the RC1 snapshot fixed it 1/2 way, but still just as disfunctional.
I installed NotePad++ to do XML comparisons between a working factory config and my custom config. The free app has a nice compare plugin and search to next difference which makes short work of a 4000 line file. Before I tweek too much with this tool, I think first I'll work through a section restore of my custom config onto the working factory config one section at a time until the ethernet toggle issue comes to life. I'm hoping this will narrow down my search area in NotePad++.
Any other suggestions welcome.
Mark -
What is reported in the pfSense system log(s) when the ping-ponging occurs?
-
FINALLY !!! I did a section restore of my custom config onto the working factory config one section at a time until the ethernet toggle issue comes to life. The "interfaces" section was the culprit. Went into the GUI to look for something that "should" have been obvious and found it. Set the speed and duplex from auto to 100TxFull on Lan and Wan, since that's their capability, and the problem disappeared.
I can't believe the solution was this simple…. aarrrg!!!
-
Went into the GUI to look for something that "should" have been obvious and found it.
And the obvious thing was ….?
-
Yes, more details please. :)
I wouldn't fix the speed/duplex on any interface you don't have to. It can cause problems later.
Steve
-
I read a post sometime back that said on occasion there were problems with PfSense negotiating a connection and fixing the neg speed was the fix. It was the first thing I tried, on the interface page, and the problem went away. Negotiates the link and DHCP in seconds now.
I tried "no preference" and it works fine too. Just the auto-negotiate that seems to give it fits. Using 3 Intel adapters and one onboard RealTek. All four adapters exhibit the same behavior using 3 different drivers. Steve, your point is well taken, I set mine to "no preference". Not sure what will happen when I switch cables from a 100M to 1G adapter. It might envolk auto-negotiate and choke again. Yet to be seen. Can always revert to fixed-rate.
Thanks for working through this with me…
Mark -
I tried "no preference" and it works fine too. Just the auto-negotiate that seems to give it fits.
Thanks for the details.
-
Yes, thanks for coming back. A couple of things confuse me here though. This seemed like a speed/duplex negotiation problem from the beginning which is why I suggested:
@stephenw10:One thing you can try is forcing the speed on the pfSense NIC: http://doc.pfsense.org/index.php/Forcing_Interface_Speed_or_Duplex_Settings
That should stop it trying to re-negotiate the connection continually.
I was forgetting that there is a gui option for this in 2.1 at that point. ::)
However you then reported:
@markn62:I tried "ifconfig em0 media 10baseT/UTP mediaopt full-duplex" at the command line, the message on my laptop said 10mbps for a couple seconds, then onto the ping-pong.
It seems like that should have worked. Maybe an ifconfig down/up was required. :-\
Anyway glad you got it sorted, just trying to get a better idea of what happened. :)
Steve
-
Ya Steve, I didn't try long forcing 10m. It may have needed an ifconfig down/up. Though I was looking for a solution that didn't require anything manual after connection. When I have to cold swap to/from current/backup router I don't want any issues adding to customer downtime.
One more tidbit about how "no preference" would behave if I plugged into a 1G adapter. Today I finally got brave enough to take the 2.0.3 box out of production and…cringe...swap in the 2.1 box. I forgot my cablemodem has a 1G adapter. Appears PfSense had no problem negotiating a link. The swap-over took <5 seconds and no connections were lost.
Happy days again... 8)
-
Ha, nice. :)
Steve
