On Mon, Jan 05, 2015 at 07:11:07PM +0100, Clemens Goessnitzer wrote: > On 01/05/15 18:25, Stefan Sperling wrote: > >Not sure. Perhaps check if deactivating power-saving on the AP is possible. > >I don't believe the run(4) driver has support for it. > > Should be deactivated now. > > >Can you share information shown in dmesg after 'ifconfig run0 debug' while > >you're using the network? > > I hope this is what you meant.
This shows a scan. I don't see an association in there. You should also see WPA handshake on a successfull connect messages since your network uses WPA. In any case this should allow you to see exactly when the driver gets and drops link. These messages are also logged to /var/log/messages. > Is there a possiblity to set debug during boot? Put a single line saying 'debug' into /etc/hostname.run0. > # dmesg | grep run0 > run0 at uhub0 port 6 "Ralink 802.11 n WLAN" rev 2.00/1.01 addr 4 > run0: MAC/BBP RT3572 (rev 0x0223), RF RT3052 (MIMO 2T2R), address > 80:1f:02:9a:22:c2 > run0 detached I assume you switched devices here so no unexpected detach. > >Anything else unusual in dmesg? Does the run device detach unexpectedly? > > One unusual thing is the lack of consistency. Let's say it worked once every > 50 tries - for no obvious reason. But then, it would fail once again... > > Another very weird behavior is as follows: I have two wireless adapters > which have - according to dmesg - the same chip (Ralink RT3052). One is > Edimax EW-7722UnD (not officially supported - at least accoring to man run) > the other is ASUS N53 (listed as supported in man run). However, the Edimax > seems to work somehow "better". First, because IMHO it can successfully > establish a connection more often. And second, the ASUS N53 was not > recognized at boot sometimes. I am at a loss here. 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. There could be a bug in the run driver but that seems quite unlikely. The run driver works well for myself and others. > If you need anything else, let me know. > > And as a last resort, I would consider buying another wireless adapter. Do > you guys know any currently available, _good supported_ (meaning no more run > driver for me, preferably no Ralink chip (?), and your personal experience > with OpenBSD) wireless adapters? For 5Ghz on USB your options are limited to run(4), rum(4), uath(4), otus(4). I have a rsu(4) USB dongle (Conrad N150) with a little screw-on omni-directional antenna. That usually works where other USB or built-in wifi cards don't. I don't believe the driver makes a crucial difference, it's the antenna. This device is 2.4Ghz only though. For built-in PCI, hunt down a supported athn(4) or iwn(4) card (see the man page for model and chip names).
