You are not logged in.
Hi,
My wireless (a Broadcom BCM4313) has always been a little slow to connect (in Linux at least), but now that I have the boot time down to about 15 seconds it's really noticeable, as I have to wait another 10 - 20 seconds or so for the wireless interface to come up. I have several options/questions that I wondered if a knowledgeable person could comment on:
* Are Broadcom chipsets particularly slow to connect? (I am using the new brcm80211 kernel driver, I have also used the Broadcom-wl driver which didn't seem any different.) I have a spare Intel card which I can try, but unfortunately it's not very easy to swap them in my laptop, so I will only try this as a last resort.
* Am I being unrealistic? Will all wireless connections take this long to connect?
* Would a static IP help? I forgot to try this last night, will try tonight.
* Could changing the protocol help? At the moment our router is running a mixed network, could changing to just g or n help?
Thanks, Jamie
Offline
I have the same wireless card in my notebook and I`m using 2.6.37 with the brcm80211 driver and it connects pretty fast [ ~5-8 sec ] using wicd. Also, it gets an IP via dhcp (not static).
I do not have any other ideas why it takes that much.
Peace, out
Their Momma Made Em, Their Momma Gave em & now she can`t even SAVE`em | My WebLog
Offline
Thanks for your reply, mine's taking about 12-15 seconds with DHCP and about 8 seconds with a static ip.
Offline
I finally got around to looking at this recently and it turns out that it's netcfg that is slow. I wrote a simple script to bring up wpa_supplicant and dhcp, put it in rc.d and added it to the DEAMONS line in rc.conf.
Offline