Re: Connman not showing a wifi adapter as a technology

[Patrik Flykt]

On Tue, 2012-12-11 at 11:04 -0500, Gary Coulbourne wrote:


> > That sounds like a bug. Should work without rfkill support also.
> > 
> > Cheers,
> > 
> > Patrik
> > 
> 
> It would be good to verify that it happens generally, not just in my
> circumstance.  It's possible there is some other underlying thing that
> changed in my configuration that I didn't account for.

When starting up ConnMan for the first time (or removing its settings
file in /var), all wireless technologies are by default off. The safest
way to "fix" this is to do 'connmanctl enable wifi' or similar
incantation in a preferred programming language at first time startup.

I noticed that with rfkill enabled, there was a bug in handling the
initial WiFi state. It now also correctly defaults to WiFi off and
actually works as expected if WiFi is to be disabled when the device is
restarted. It now works the same way with and without rfkill support.


Cheers,

Patrik


___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman

Re: Connman not showing a wifi adapter as a technology

[Gary Coulbourne]

> Patrik Flykt 
> Tuesday, December 11, 2012 5:18 AM
>
> That sounds like a bug. Should work without rfkill support also.
>
> Cheers,
>
> Patrik

It would be good to verify that it happens generally, not just in my
circumstance.  It's possible there is some other underlying thing that
changed in my configuration that I didn't account for.

Peace,
Gary
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman

Re: Connman not showing a wifi adapter as a technology

[Patrik Flykt]

On Tue, 2012-12-11 at 08:49 +0100, Daniel Wagner wrote:
> Hi Gary
> 
> On 10.12.2012 23:40, Gary Coulbourne wrote:
> >> If I start connman, it will connect to either of the ethernet
> >> interfaces and dhcp correctly.  I can even disconnect and reconnect
> >> with no difficulty.  However, the wifi seems to be missing.
> >>
> > So, I was missing rfkill support in the kernel.  Adding that caused wifi
> > to appear as an entry in the technology list.
> 
> Thanks for reporting back. Just sent a patch for the README.

That sounds like a bug. Should work without rfkill support also.

Cheers,

Patrik

___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman

Re: Connman not showing a wifi adapter as a technology

[Daniel Wagner]

Hi Gary

On 10.12.2012 23:40, Gary Coulbourne wrote:

If I start connman, it will connect to either of the ethernet
interfaces and dhcp correctly.  I can even disconnect and reconnect
with no difficulty.  However, the wifi seems to be missing.


So, I was missing rfkill support in the kernel.  Adding that caused wifi
to appear as an entry in the technology list.


Thanks for reporting back. Just sent a patch for the README.

cheers,
daniel

___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman

Re: Connman not showing a wifi adapter as a technology

[Gary Coulbourne]

> If I start connman, it will connect to either of the ethernet
> interfaces and dhcp correctly.  I can even disconnect and reconnect
> with no difficulty.  However, the wifi seems to be missing.
>
So, I was missing rfkill support in the kernel.  Adding that caused wifi
to appear as an entry in the technology list.

Peace,
Gary
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman

Connman not showing a wifi adapter as a technology

[Gary Coulbourne]

I am using buildroot to bring up an embedded design.  The device has two
ethernets in the SoC (i.MX28) and a wifi adapter connected via USB.  When
linux boots, it brings up both ethernets, localhost, and the wifi adapter,
verified with "ifconfig -a".  I can manually configure any of the
interfaces and use dhcp to connect, with no trouble.

If I start connman, it will connect to either of the ethernet interfaces
and dhcp correctly.  I can even disconnect and reconnect with no
difficulty.  However, the wifi seems to be missing.

It appears in the logs

connmand[673]: wlan0 {create} index 4 type 1 
connmand[673]: wlan0 {update} flags 4099 
connmand[673]: wlan0 {newlink} index 4 address 7C:DD:90:20:BC:81 mtu 1500
connmand[673]: wlan0 {newlink} index 4 operstate 2 
connmand[673]: Adding interface wlan0 [ wifi ]
connmand[673]: src/technology.c:technology_find() type 3
connmand[673]: src/detect.c:detect_newlink() type 1 index 4
connmand[673]: src/device.c:connman_device_create() node 7cdd9020bc81 type 2
connmand[673]: src/device.c:connman_device_create() device 0x6cb080
connmand[673]: src/device.c:connman_device_set_string() device 0x6cb080 key
Address value 7C:DD:90:20:BC:81
connmand[673]: src/device.c:connman_device_register() device 0x6cb080 name
Wireless
connmand[673]: src/rtnl.c:rtnl_message() buf 0xbefe3ac0 len 1024
connmand[673]: src/rtnl.c:rtnl_message() NEWLINK len 1024 type 16 flags
0x seq 0 pid 0
connmand[673]: src/ipconfig.c:__connman_ipconfig_newlink() index 2

So, a cursory glance at the source seems to indicate that it should have
registerred itself as an available technology, but no dice...

# connmanctl technologies
{ /net/connman/technology/ethernet }
  [Name] = Wired
  [Type] = ethernet
  [Powered] = True
  [Connected] = False
  [Tethering] = False

I've tried doing "enable wifi"... nothing.  It seems to be communicating
with the wpa_supplicant (running with -u so it can use dbus), as here's
what I get when I plug
the usb wifi dongle back in after having disconnected it:

connmand[678]: src/rtnl.c:rtnl_message() buf 0xbeca5ac0 len 1020
connmand[678]: src/rtnl.c:rtnl_message() NEWLINK len 1020 type 16 flags
0x seq 0 pid 0
connmand[678]: src/ipconfig.c:__connman_ipconfig_newlink() index 5
connmand[678]: wlan0 {create} index 5 type 1 
connmand[678]: wlan0 {update} flags 4098 
connmand[678]: wlan0 {newlink} index 5 address 7C:DD:90:20:BC:81 mtu 1500
connmand[678]: wlan0 {newlink} index 5 operstate 2 
connmand[678]: Adding interface wlan0 [ wifi ]
connmand[678]: src/technology.c:technology_find() type 3
connmand[678]: src/detect.c:detect_newlink() type 1 index 5
connmand[678]: src/device.c:connman_device_create() node 7cdd9020bc81 type 2
connmand[678]: src/device.c:connman_device_create() device 0xfcd228
connmand[678]: src/device.c:connman_device_set_string() device 0xfcd228 key
Address value 7C:DD:90:20:BC:81
connmand[678]: src/device.c:connman_device_register() device 0xfcd228 name
Wireless
connmand[678]: src/rtnl.c:rtnl_message() buf 0xbeca5ac0 len 1016
connmand[678]: src/rtnl.c:rtnl[   40.48] IPv6: ADDRCONF(NETDEV_UP):
wlan0: link is not ready
_message() NEWLINK len 1016 type 16 flags 0x seq 0 pid 0
connmand[678]: src/ipconfig.c:__connman_ipconfig_newlink() index 5
connmand[678]: wlan0 {update} flags 4163 
connmand[678]: wlan0 {newlink} index 5 address 7C:DD:90:20:BC:81 mtu 1500
connmand[678]: wlan0 {newlink} index 5 operstate 0 
connmand[678]: src/detect.c:detect_newlink() type 1 index 5
connmand[678]: src/rtnl.c:rtnl_message() buf 0xbeca5ac0 len 1016
connmand[678]: src/rtnl.c:rtnl_message() NEWLINK len 1016 type 16 flags
0x seq 0 pid 0
connmand[678]: src/ipconfig.c:__connman_ipconfig_newlink() index 5
connmand[678]: wlan0 {update} flags 4099 
connmand[678]: src/ipconfig.c:__connman_ipconfig_lower_down() ipconfig ipv4
(nil) ipv6 (nil)
connmand[678]: wlan0 {newlink} index 5 address 7C:DD:90:20:BC:81 mtu 1500
connmand[678]: wlan0 {newlink} index 5 operstate 2 
connmand[678]: src/detect.c:detect_newlink() type 1 index 5

I've been wrestling with this for a couple hours, but haven't found any
references to similar trouble in the archives.  If anyone has any
suggestions, I could really use them.

Thanks!

Peace,
Gary
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman