wifi0 has Ethernet Link-encap

[Eli Criffield]

When using updated madwifi drivers from svn (verison 1475) with a freshly updated version of dapper (current as of today, march 24th 2006) /sbin/udevplug hangs for 3 mins and exits with non zero exit code.

No errors are reported.
This maybe similar to bug #36010 but its not exacly the same as it doesn't pause in the initrd, but in the udev startup script. And its in 079-0ubuntu21 and 079-0ubuntu22

Once it fails after 3 mins everything works fine.

Eli Criffield <lauchpad at zendo dot net>

[Scott James Remnant (Canonical) (canonical-scott)]

Locate the line in /etc/iftab that renames your WiFi card (it's probably the ath0 one) and add "arp 1" to the end.

[Eli Criffield (launchpad-zendo)]

i just tried adding "arp 1" and i had the same results

[Eli Criffield (launchpad-zendo)]

If i run /sbin/udevplug once booted and loged every once in a while it hangs for 3 mins, but not like on boot where it hanges for 3 mins every time.

Is there anyway to reproduce how it would run at boot? Ive tried unloading all wifi related modules and it almost never hangs, just like if they where loaded.

Eli

[Eli Criffield (launchpad-zendo)]

Just tried udev-079-0ubuntu23

And i still have the 3 min hang on boot while waiting for /sbin/udevplug to fail

Eli

[Scott James Remnant (Canonical) (canonical-scott)]

Please attach your /etc/iftab file.

[Eli Criffield (launchpad-zendo)]

I tried two iftabs the orginal, this one and the second with arp 1 on the end of the ath0 line

[Eli Criffield (launchpad-zendo)]

this is the second iftab i tried
only diffrence is the arp 1 on the end of the ath0 line

[Scott James Remnant (Canonical) (canonical-scott)]

What happens if you comment out the ath0 line?

[Elias Oltmanns (oltmanns)]

Scott James Remnant <email address hidden> wrote:
> What happens if you comment out the ath0 line?

That makes all the difference. Just added the line to my iftab (since
I never had it in there and thus didn't suffer from the problem). The
problem is that with madwifi_ng two interfaces are set up at the same
time:
wifi0 serves as the "real" interface to the hardware whereas
ath0 is a virtual device which may share the same hardware with other
virtual devices.

Initially, wifi0 and ath0 have the same mac address and thus both
match the selector in /etc/iftab. udevd keeps hanging around trying to
sort things out -- in vain.

[Eli Criffield (launchpad-zendo)]

Yes THAT WORKED!

commenting out the ath0 line works, now there's no delay.

what creates the iftab anyway?

Eli

[Scott James Remnant (Canonical) (canonical-scott)]

The installer creates it; as Elias comments it's because madwifi-ng creates both a wifi0 and ath0 device for your card so both try to get renamed to the same thing. However the "arp 1" was supposed to stop that ...

Could you attach the output of "ifconfig -a" for me, also just for sanity the output of "dpkg-query -W udev"

Thanks

[Eli Criffield (launchpad-zendo)]

$ ifconfig -a
ath0 Link encap:Ethernet HWaddr 00:05:4E:4B:D3:2E
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:11:25:45:EA:3B
          inet addr:179.16.102.248 Bcast:179.16.255.255 Mask:255.255.0.0
          inet6 addr: fe80::211:25ff:fe45:ea3b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:335196 errors:0 dropped:0 overruns:0 frame:0
          TX packets:151671 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:130355045 (124.3 MiB) TX bytes:48221575 (45.9 MiB)
          Base address:0x8000 Memory:c0240000-c0260000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:272 (272.0 b) TX bytes:272 (272.0 b)

sit0 Link encap:IPv6-in-IPv4
          NOARP MTU:1480 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.88.88.2 P-t-P:10.88.88.1 Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
          RX packets:4169 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5067 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1198764 (1.1 MiB) TX bytes:866001 (845.7 KiB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
          inet addr:10.9.9.1 Bcast:10.9.9.255 Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
          inet addr:10.8.8.1 Bcast:10.8.8.255 Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wifi0 Link encap:Ethernet HWaddr 00:05:4E:4B:D3:2E
          inet6 addr: fe80::205:4eff:fe4b:d32e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:8...

[Scott James Remnant (Canonical) (canonical-scott)]

*censored: very rude comment about madwifi-ng*

"Gee, why don't we make the wifi0 phantom device claim to be an ordinary Ethernet device, that'll be fun! OH YES!"

Commenting out or removing the ath0 line from /etc/iftab is the only solution to this at the moment I'm afraid; fortunately the installer won't generate it if you'd installed from fresh.

When we supply madwifi-ng ourselves, we'll have to remember to purge any iftab line for it *sigh* unless it's something we can fix -- have subscribed Matthew Garrett and Adam Conrad to answer that one.

[Scott James Remnant (Canonical) (canonical-scott)]

I'm prematurely assigning this to lrm; when/if we ship madwifi-ng, we need to make sure that this bug has been fixed. The Link-encap of the wifi0 device should *not* be Ethernet because it cannot be used as an ethernet device, like wlan-ng it should just be anything else like UNSPEC.

[Elias Oltmanns (oltmanns)]

This problem has been fixed upstream as of r1497. Type is set to
ARPHRD_IEEE80211 now.

[Elias Oltmanns (oltmanns)]

Just verified that a setup like
---/etc/iftab---
wifi0 mac 00:0a:ae:... arp 801
ath0 mac 00:0a:ae:... arp 1
---/etc/iftab---

wroks just fine. Not sure how to change the status of this bug report now.