Re: NM looses connection and/or doesn't use dhcp

Ok, I understand this when it applies to wireless. But as I have said in my post I am talking about my wired connection. With wireless, yes, it makes sense. But with a wired connection that IS NOT dropping then I would expect NetworkManager to stay connected to it. I sometimes leave my laptop on at home and connected to the wired connection. Then at work I attempt to ssh into it only to find that it is "down". This is the reason I posted on here as it looks to be a serious bug. Now in all honesty it has stayed connected today for at least three hours so this is good. One possibility is that my wired connection becomes congested and very slow sometimes, but that shouldn't matter because it is still UP.

Dan Williams wrote:

If the connection to the AP gets dropped, NM will connect to the last AP
you connected to that it can see because it attempts to preserve
connectivity.  If you don't want to connect to that other network,
remove it from the saved networks list.  If NM switched away from the
connection it had when you saw it, then something caused the wireless
card and driver to drop the connection to the AP, and NM was not able to
reconnect to that AP again in enough time.  If your AP crashes or
reboots, for example, it might take a while to do so, during which it
can't be connected to.  For example, sometimes my WRT54G crashes, and
after a reboot, the ipw2200 driver is stuck in a state where it won't
connect to the AP, requiring a module unload/reload before it can
connect again, _even_ without NetworkManager at all.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]