Sabayon Community

by **davemc** » Mon Jul 23, 2007 14:34

Actually, I am having this same sort of problem here as well (Dell 1390 Broadcom chipset). Ive been having it since I got this thing (hp dv2415us) where it will connect for a couple of hours (WPA2 shared key, auto dhcp, etc). I turned off the GNOME network manager cuz its garbage and connect up via cli w/manual configs. This worked fine for a couple weeks but it would always disconnect after a few hours with weird errors. Something like "dns lease already exists in blah blah blah, disconnecting". So I pulled out all the stops and threw every dirty trick on the books at it and still no dice. Googling turned up ALOT of people complaining about this very thing! Mainly those using the latest Ndiswrapper (1.46). Nobody seems to have figured this out yet either.

by **WarraWarra** » Mon Jul 23, 2007 20:20

davemc wrote:Actually, I am having this same sort of problem here as well (Dell 1390 Broadcom chipset). Ive been having it since I got this thing (hp dv2415us) where it will connect for a couple of hours (WPA2 shared key, auto dhcp, etc). I turned off the GNOME network manager cuz its garbage and connect up via cli w/manual configs. This worked fine for a couple weeks but it would always disconnect after a few hours with weird errors. Something like "dns lease already exists in blah blah blah, disconnecting". So I pulled out all the stops and threw every dirty trick on the books at it and still no dice. Googling turned up ALOT of people complaining about this very thing! Mainly those using the latest Ndiswrapper (1.46). Nobody seems to have figured this out yet either.

Downgrade/upgrade to dhcp ? 3.0.6 , as 3.0.3 and 3.0.10-rc2 has this we are trying to find where it is so it can be propperly reported and marked = bad.
3.0.6 works good and is part of the stable version " x86 " not " ~x86 " unstable in make.conf

emerge -s dhcp
to search and should show installed and available.

PS> I had to go back to bcm43xx in 1.0 BE with 1390 or seeing it is not in the /lib/.../net/wireless I just used ndiswrapper bcmwl5.inf and work like a charm with dhcp3.0.6 and stable.
Will zip and upload driver if you need for 1390.
This time bug in forums keeps comming back.

by **davemc** » Mon Jul 23, 2007 20:25

PS. Im using wpa_supplicant. Not sure if that would have anything to do with it.

Edit to your Edit

It DOES work...for a while. You will need to leave it up for maybe a day or so before you will see this bug.

by **WarraWarra** » Mon Jul 23, 2007 20:29

Not sure as I do not and had the same bugs so the common thing is dhcp and somone else also reported this dhcp downgrade worked not sure at all.
This seems to work for the time being 6 hours and going strong even after restart no more time out's , is there not a log for errors vixie cron o0r something that can show what is causing or initiating the time out's ?

Router set to 180mins or 360min then dhcp ip change so as long as the connection runs I am okay for now. We would have to get to the bottom of this bug though

Shout of you find somethign more.
Will see when seeding 3.4a how it goes.

by **davemc** » Mon Jul 23, 2007 20:31

Ill give it a go. BTW, this bug is not specific to Gentoo as Ive seen tons of reports of it over at the Buntu and SuSe forums as well. Nobody seems to know whats going on but ive seen some pretty radical workarounds that im not quite willing to try out yet.

by **WarraWarra** » Mon Jul 23, 2007 20:37

Could it be the recent dns security bug from last week or 2 causing this as most isp's have not updated yet and or the something we are using has this still in it ?

I know dyndns.org has updated teir server's about this past friday.

by **davemc** » Tue Jul 24, 2007 13:48

No dont think so. The problem is specific to my laptop wireless card. Upgrade/downgrade dhcp didnt do a thing to fix it. I think the culprit was Ndiswrapper. I found a guide on Ubuntu forums I followed yesturday and I havent dropped offline ever since, so I think that fixed the issue. Also, now the Gnome-network-manager seems to be able to connect up to WPA on its own as well and the keyrings are functioning properly.

by **pluto** » Tue Aug 07, 2007 18:57

davemc wrote:PS. Im using wpa_supplicant. Not sure if that would have anything to do with it.

I've seen this problem when more than one wpa_supplicant is running. When that happens, each instance of the process is fighting to get the connection. My not so elegant solution is to do a "sudo killall wpa_supplicant" and then reestablish conenction form knetworkmanager.

by **davemc** » Tue Aug 07, 2007 21:18

pluto wrote:
davemc wrote:PS. Im using wpa_supplicant. Not sure if that would have anything to do with it.

I've seen this problem when more than one wpa_supplicant is running. When that happens, each instance of the process is fighting to get the connection. My not so elegant solution is to do a "sudo killall wpa_supplicant" and then reestablish conenction form knetworkmanager.

My issue with that fix is that 1) Im in GNOME so no knetworkmanager, and 2) sudo killall wpa_supplicant wont fix anything for more than a single session. The problem was with the bcm driver that comes default now. Blacklisting that solved it all.

Sabayon Community

Wireless Anoyances

Who is online