On Mon, Feb 09, 2009 at 02:15:21AM -0800, Bernd Markgraf wrote: > > OK, it should be a known issue of iwh driver that heavey data transfer > > may cause driver dropping connection. But the driver should re-connect > > to the network again automatically. So I wonder does the re-connect > > failure happens frenquently? > I'd say so. I see this at home every day. Not so often when on the road > (Telekom access point without encryption). But as I said it's not only > happening under high network load. I don't know for sure if nwam ever > reconnects automatically at all. At least at home I always have the dladm > connect still in shell history and am faster than nwam ;-) (I waited a few > minutes in the beginning but it took too long so I declared it dead)
Your debug log showed nwam attempting to reconnect: > Feb 8 21:55:20 akuma nwamd[2858]: [ID 459249 daemon.error] > connect_chosen_lan: connect to 'BERNY' failed on 'iwh0': operation failed > Feb 8 21:55:20 akuma nwamd[2858]: [ID 200354 daemon.warning] could not > connect to chosen WLAN BERNY on iwh0, going to auto-conf ...but the reconnect failed. What's not clear is why that command failed; nwamd is simply using libdladm, much like the dladm command. I'm wondering if the driver (or wpad) is in a confused state, possibly related to the dropped link, and there's a delay before it gets sorted out. You could force nwam to try the connection again using the GUI's menu to select your WLAN. It would be good to know if that works; though it might not be faster than using your shell history. :-) > Feb 8 21:55:20 akuma wpad[2868]: [ID 702911 daemon.notice] Failed to disable > WPA in the driver. This message, which shows up immediately after the link down, is coming from wpad, the daemon that handles WPA. It's printed when wpa is cleaning up after disassociating; I'm guessing that failure is connected to whatever caused the original link down, but someone more familiar with wpad than I could dig further. -renee > > When scanning for available networks happens, the > > connection has been dropped. I think there should be some conflicting > > operations make the driver out of state and re-connect to network > > failure. > If scanning comes in the way of normal operation I would prefer not to scan > for networks as long as I am connected to an AP. > > Bernd > -- > This message posted from opensolaris.org > _______________________________________________ > laptop-discuss mailing list > laptop-discuss at opensolaris.org
