On Mon, Jan 05, 2015 at 08:20:28PM +0100, Clemens Goessnitzer wrote: > driver to try getting a connection for a longer time? The following shows > that run0 gets a connection/handshake, but after the "no link........... > sleeping". And why would it try getting and successing getting a connection > after it is supposingly "sleeping"?
The "no link" message is printed by dhclient. dhclient is sleeping since it can't do anything until the device has a link. I suspect the device is just spending a long time scanning all 11b/g/a channels before it finds the AP you want to connect to. > Jan 5 19:58:58 openbsd /bsd: run0: sending assoc_req to 44:32:c8:34:24:18 > on channel 44 mode 11a > Jan 5 19:58:58 openbsd /bsd: run0: received assoc_resp from > 44:32:c8:34:24:18 rssi 23 mode 11a > Jan 5 19:58:58 openbsd /bsd: run0: received msg 1/4 of the 4-way handshake > from 44:32:c8:34:24:18 > Jan 5 19:58:58 openbsd /bsd: run0: sending msg 2/4 of the 4-way handshake > to 44:32:c8:34:24:18 > Jan 5 19:58:58 openbsd /bsd: run0: associated with 44:32:c8:34:24:18 ssid > "clumsy5" channel 44 start 6Mb short preamble short slot time > Jan 5 19:58:58 openbsd /bsd: run0: received msg 3/4 of the 4-way handshake > from 44:32:c8:34:24:18 > Jan 5 19:58:58 openbsd /bsd: run0: sending msg 4/4 of the 4-way handshake > to 44:32:c8:34:24:18 Seems to work fine. > >Hard to tell from over here. > > > >Have you ever tested with a different AP in a different environment? > >The tiny USB dongle antennas could be too weak for your environment > >e.g. due to interference from other radio sources. > > > >Sometimes small changes in positioning can make a difference. I have a > >tiny urtwn(4) USB dongle which connects if I lean forward on my couch but > >doesn't connect when I sit back and relax :( I settled on not using this > >device rather than moving the couch. > > No, not with a different AP, but with different settings (2.4GHz, 5GHz, > 20/40 MHz channel width, different channels). And both of my Thinkpads with > wpi supported chips get a connection to the same AP perfectly, and really > fast (running OpenBSD -current i386, haven't tried amd64 though). > > I have a desktop PC meaning it doesn't move at all - and we hardly have any > earthquakes here in Austria :) > > And the distance from adapter to AP is less than a meter. IMHO perfect > conditions for functional wireless networking > > And when I boot into Ubuntu, both wireless adapters work perfectly, so I > don't think it's a hardware thing. Hmm, that makes a driver bug more likely. Can you try with FreeBSD? Their driver has essentially become the upstream version of run(4). If their driver works better we might be able to fix ours.
