Hi Daniel, On Sat, Dec 03, 2011 at 03:39:28PM +0100, Daniel Mack wrote: > Hi, > > I'm testing connman on an ARM embedded board and I'm having trouble > getting tethering to work. In my setup, I'm using a Ralink based USB > device which runs fine with hostapd, so I assume it should also be > possible with connman in tethering mode. Correct me if I'm wrong here. You're right.
> [Following up on earlier discussions on this list, I have to admit that > Ad-Hoc modes are indeed no option here due to the fact that Android > phones can't cope with them at all. So the ability to act as 'real' > access point now became a requirement for the system. Which has it's > good sides too, as there's no need to modify connman in that way.] > > When playing with the python-based command line tools, I can connect to > my local Wifi networks just fine by calling 'connect-service ssid > secret'. However, when calling 'enable-tethering wifi testtest > 12345678', the tool returns 'Enabling wifi tethering', and connman > (started as 'connmand -nd') shows this output: > > http://pastebin.com/jR79Bz79 > > After that, the device doesn't seem to have switched its mode ... > > # iwconfig wlan0 > wlan0 IEEE 802.11bg ESSID:off/any > Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm > Retry long limit:7 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:on The connmand logs don't show any specific failure, so at that point, we'd need to get the wpa_supplican logs as well (-ddd -t) in order to see where it failed. > .. and attempts to connect to existing networks as before now fail > constantly, even after the damon was restarted. The full output with > debug information of a freshly started daemon can be found here: > > http://pastebin.com/vumFk7eR > > A reboot is needed to recover from that state. > > On a more general note: what I'm trying to achieve here on a higher > level is a system that connects to a set of preconfigured services > (wired, wireless) if they are available. As a fallback, the system > should switch back to tethering, serving its own wireless LAN with DHCP > server features and so on. Can anyone elaborate on what would be the > easiest way to implement this? You're going to need some code listening to ConnMan and checking if it's attempting to connect to your known networks. ConnMan sends D-Bus signals for that and will let you know if it's associating, ready or online. If that fails, you'd then switch to tethering mode. You may also consider looking at the current (incomplete though) session API for doing so. Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
