Example session: $ sudo connmanctl scan wifi Scan completed for wifi $ sudo connmanctl services *AR LV-426 wifi_c4d987b634ba_4c562d343236_managed_psk [ others... ] $ sudo connmanctl connect wifi_c4d987b634ba_4c562d343236_managed_psk Error /net/connman/service/wifi_c4d987b634ba_4c562d343236_managed_psk: Input/output error $ sudo connmanctl connect wifi_c4d987b634ba_4c562d343236_managed_psk Error /net/connman/service/wifi_c4d987b634ba_4c562d343236_managed_psk: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
This is Linux 3.13, with a Centrino Advanced-N 6235 wifi module, on a modern Intel Q87 chipset motherboard. Mike On 14 July 2014 10:27, Mike Purvis <[email protected]> wrote: > I have never seen this error. Did this work earlier and you have not >> upgraded your dbus or rest of the system? Anyway, this does not look >> like a connman issue. > > > Yes, it worked previously. No updates have been applied to the system; the > only changes have been fiddling this the various config files in service of > the static IP objective. > > Is it possible that one of these having funky permissions or wrong > settings could be a problem? > > Could this be resolved by redoing the make install step of connman 1.24? > > > $ sudo connmanctl connect wifi_c4d987b634ba_4c562d343236_managed_psk >> > Error /net/connman/service/wifi_c4d987b634ba_4c562d343236_managed_psk: >> > Input/output error >> >> This looks like your wifi AP was not found in the scans so the connect >> just failed because of that. >> >> Make sure you see your AP in "connmanctl services" list before trying to >> connect, otherwise the connect will just fail. >> > > Hmm, I definitely did— the string was copy-pasted directly from the > services output. > > The log also says that system tries to auto connect to LV-426, but dhcp >> server does not give a lease. Then the log ends so I do not know what >> happened next. > > > Interesting; I'll follow this up with my network administrator. > > Mike > _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
