Hi,
My WiFi doesn't work when for some reason if at, boot up , the system detects and configures wlan0:avahi.  I'm using the Overo Fire WiFi, with the latest kernel build from last week. 

Here is the output of the ifconfig -a command, showing wlan0:avahi detect. WiFi doesn't work and I have no ip address allocated to wlan0.

wlan0     Link encap:Ethernet  HWaddr 00:19:88:10:F9:9C  
          inet6 addr: fe80::219:88ff:fe10:f99c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:410 (410.0 b)  TX bytes:2168 (2.1 KiB)

wlan0:avahi Link encap:Ethernet  HWaddr 00:19:88:10:F9:9C  
          inet addr:169.254.9.74  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1


Now, if I reboot and somehow the system doesn't detect that wlan0:avahi, the ip address gets assigned and I am able to ping. 

Here is the output of the ifconfig -a command:

wlan0     Link encap:Ethernet  HWaddr 00:19:88:10:F9:9C  
          inet addr:87.201.169.254  Bcast:87.201.169.255  Mask:255.255.255.0
          inet6 addr: fe80::219:88ff:fe10:f99c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2161 (2.1 KiB)  TX bytes:2530 (2.4 KiB)

root@overo:~# ping www.google.com
PING www.google.com (209.85.229.99): 56 data bytes
64 bytes from 209.85.229.99: seq=0 ttl=238 time=163.269 ms


Anybody else notice this behaviour? 

Best regards,

Elvis