On Thu, Jan 14, 2016 at 07:41:59PM -0700, Chris Wojo wrote: > Here is a one liner from the beacons at home:
It seems this AP does not support 802.11n and is using WEP. Is this correct? > Here are a few beacons from work: There's nothing unusual in these beacons as far as I can tell. > This would be a selection of dmesg output for the work AP's: It looks as if your connection failures at work could be related to authentication failures. The OpenBSD client won't move from ASSOC to RUN state. This usually means WPA authentication is failing. Let's try to confirm this theory. Which authentication mechanism is used on this network? It's using some form of WPA but I'm not sure which exactly. Can you show the lines 'ifconfig iwm0 scan' displays for these APs? These lines should indicate the authentication method used. If the lines contain '802.1x' you'll need to install wpa_supplicant from packages and configure it before connecting. See http://undeadly.org/cgi?action=article&sid=20130128142215 for details. Can you run 'ifconfig iwm0 debug' before trying to connect, and show the WPA 'handshake' messages which should now end up in dmesg? Upon success, 4 handshake messages are exchanged and the 'status:' line displayed by 'ifconfig iwm0' becomes 'active'. Note that dhclient cannot do anything before the link becomes active, so if you've only been checking dhclient output that's not the right place to look. Can you show what 'ifconfig iwm0' (as non-root user so passwords remain hidden) looks like while you're trying to connect at work? Perhaps you have a WEP key and a WPA set at the same time after moving from home to the office while the laptop is suspended? Switching from a WEP network to a WPA network requires clearing the WEP key with 'ifconfig iwm0 -nwkey' in addition to the commands which set up WPA. I've fallen into this trap myself many many times. If none of the above help, did you ever manage to use any OpenBSD client in this environment? Can you connect to this network with an OpenBSD client using a wifi device supported by a driver other than iwm(4)?
