Hi Grant, > I recently came across a use case in which connmand-0.64 generates two > conflicting network service entries for a wireless access point with an SSID > from the "special" list that ultimately results in not being able to connect > to the SSID at all. > > In this scenario, I bring up my user interface to configure and connect to a > network service via the D-Bus interface to connman. > > At times, the connection succeeds and other times the connection fails. If > the connection does succeed, on a subsequent reboot, the system will not > connect to the access point. > > I've discovered that this all appears to come down to two entries in > /var/lib/connman/default.profile. > > The first entry contains the expected key/value pairs from the user > interface connection attempt: Favorite=true, AutoConnect=true and > Passphrase=<...>. > > [wifi_000c294c56a2_6c696e6b737973_managed_psk] > Name=linksys > SSID=6c696e6b737973 > Favorite=true > Modified=2010-12-29T01:25:15.224273Z > Passphrase=<redacted> > IPv6.method=off > IPv6.netmask_prefixlen=0 > IPv4.method=dhcp > IPv4.netmask_prefixlen=0 > AutoConnect=true > > The second entry, named according to the "special SSID" rules, contains > neither AutoConnect nor Passphrase and has Favorite=false: > > [wifi_000c294c56a2_linksys_0012171baf73_managed_psk] > Name=linksys > SSID=6c696e6b737973
you should only see this one. We are mapping these vendor default SSID to unique services on purpose. Since you don't wanna roam between these SSIDs. So it seems there is a bug somewhere that leads to creating these twice and then confuse the system. This needs to be fixed, but I don't see that one right now. As a side node, it is never a good idea to keep the default name ;) Regards Marcel _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
