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. Is there a possiblity to set debug during
boot?
# 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
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
10:bf:48:5b:4e:56
run0: begin active scan
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 3 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 4 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 1 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 1 mode 11g
run0: received beacon from c0:25:06:3d:97:79 rssi 51 mode 11g
run0: received beacon from 9c:97:26:8c:69:b5 rssi 47 mode 11g
run0: received beacon from c0:25:06:3d:97:79 rssi 49 mode 11g
run0: received beacon from 9c:97:26:8c:69:b5 rssi 47 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 6 mode 11g
run0: received probe_resp from 44:32:c8:34:24:18 rssi 19 mode 11g
run0: received beacon from 44:32:c8:34:24:18 rssi 21 mode 11g
run0: received beacon from 00:24:d1:82:74:57 rssi 57 mode 11g
run0: received beacon from d4:6e:5c:68:ac:34 rssi 49 mode 11g
run0: received beacon from 44:32:c8:34:24:18 rssi 21 mode 11g
run0: received beacon from 00:24:d1:82:74:57 rssi 55 mode 11g
run0: received beacon from d4:6e:5c:68:ac:34 rssi 51 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 7 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 8 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 9 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 10 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 11 mode 11g
run0: received beacon from 80:1f:02:b7:3a:ee rssi 45 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 12 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 13 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 14 mode 11g
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 36 mode 11a
run0: received beacon from 80:1f:02:b7:3a:ef rssi 37 mode 11a
run0: received beacon from 80:1f:02:b7:3a:ef rssi 37 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 38 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 40 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 44 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 46 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 48 mode 11a
run0: received beacon from c0:25:06:3d:97:75 rssi 59 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 52 mode 11a
run0: received beacon from c0:25:06:3d:97:75 rssi 59 mode 11a
run0: received beacon from c0:25:06:3d:97:75 rssi 59 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 54 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 56 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 60 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 62 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 64 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 100 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 102 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 104 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 108 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 110 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 112 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 116 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 118 mode 11a
run0: sending probe_req to ff:ff:ff:ff:ff:ff on channel 120 mode 11a
run0 at uhub3 port 2 "Ralink 802.11 n WLAN" rev 2.00/1.01 addr 3
run0: MAC/BBP RT3572 (rev 0x0223), RF RT3052 (MIMO 2T2R), address
10:bf:48:5b:4e:56
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.
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?
