invalid iftab for aironet card

[Byron Clark]

Upon installing breezy on a laptop with a cisco aironet wireless card the
following iftab file was created:

eth0 mac 00:40:96:35:52:26

This entry is valid for almost any other card, but the airo driver usually
creates an eth0 and a wifi0 device. The created entry maps wifi0 to eth0 and
the usual eth0 to eth1. wifi0 cannot do tcp/ip. The fix is to change the line
to read like this:

eth0 mac 00:40:96:35:52:26 mac 1

This line maps the correct device to eth0 and tcp/ip is again possible.

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

Is there any way we can know that cards are behaving like this? Do both MACs
show up in "ifconfig -a" ?

[Byron Clark (byron-theclarkfamily)]

I mistyped the fixed version of /etc/iftab; it should read:

eth0 mac 00:40:96:35:52:26 arp 1

[Byron Clark (byron-theclarkfamily)]

Created an attachment (id=4677)
original ifconfig output

[Byron Clark (byron-theclarkfamily)]

Created an attachment (id=4678)
ifconfig output after adding "arp 1" to /etc/iftab

[Jacob Winski (winski)]

Thank you for the fix Byron Clark!

This was a real pain in Breezy (it worked in Hoary for whatever reason). This
problem was usually caused by an rmmod/modprobe. When using the card and having
it boot, it worked until rmmod/modprobe, whether manually by hand, or whether
done by a script such as suspend or hibernation. This meant that if suspend were
used, wifi would die on resume and would be difficult to recover because the
problem continues even after reboot. After messing around, rebooting, and
shutting down, it somehow sometimes fixed itself. This may possibly be to some
setting being reset.

Needless to say, this fix should be incorporated into Ubuntu when using module airo.

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

Fixed in netcfg_1.23ubuntu2 ... I've unconditionally written the "arp" line if there is any other network device with the same MAC address.

This should fix for the aironet cards, and also the madwifi-ng cards which have the same problem.

You'll need the latest udev to gain the support for this selector (also uploaded)