Also though it did not appear in the message the wlan0 interface is there but seems to have no ipv4 address though it does seem to have an ipv6 address. The router I have doesn't speak ipv6.
connmand seems to start a new wpa instance as well I saw 3 instances in the output of 'ps anx' when I looked...iirc there are normally 2 ;-/ *head-scratch* >AFAIK connman supports starting on a working connection since version > 0.68 > > from dmesg > > wlan0: authenticate with 00:1c:10:9c:32:87 (try 1) > wlan0: authenticated > wlan0: associate with 00:1c:10:9c:32:87 (try 1) > wlan0: RX ReassocResp from 00:1c:10:9c:32:87 (capab=0x411 status=0 > aid=1) > wlan0: associated > wlan0: disassociating from 00:1c:10:9c:32:87 by local choice (reason=3) > cfg80211: Calling CRDA to update world regulatory domain > wlan0: deauthenticating from 00:1c:10:9c:32:87 by local choice > (reason=3) > cfg80211: World regulatory domain updated: > cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, > max_eirp) > cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 > mBm) > cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 > mBm) > cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 > mBm) > cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 > mBm) > cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 > mBm) > skge 0000:03:15.0: eth1: disabling interface > > No idea why when using connman I get that disassociating local choice > message since starting the wlan0 interface works just fine without > connman > https://bugzilla.redhat.com/show_bug.cgi?id=503983 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/548992 Some users reported this was worked around by disabling ipv6 support in the kernel others by dropping dhcp for a static ip Those bug reports show this on a wide variety of hardware and several kernels the common denominator seems to be wpa2 and network-manager on this particular box the eth0 is not plugged in. I have not tried the workarounds At some point I did control-C to kill that connection restarted net.wlan0 and back on line Others have reported that manually reconfiguring the interface works, that I have experienced on my sole attempt (around 0.68) > ------------------------------ > > _______________________________________________ > connman mailing list > [email protected] > http://lists.connman.net/listinfo/connman > > End of connman Digest, Vol 28, Issue 5 > ************************************** _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
