Public bug reported:
Binary package hint: network-manager
Since upgrading to Ubuntu 6.10, NetworkManager does no longer fallback
to zerconf addressing (self-assigned IP addressing from the
169.254.0.0/16 range, as per RFC3330 and RFC3927) for the WLAN NIC. This
although package zeroconf is installed and it's script is in
/etc/network/if-up.d.
Zeroconf actually works for eth1 (which is the onboard nic with module
tg3) on my laptop: when I plug it into a non-DHCP LAN, syslog shows how
DHCP fails and then a RFC3927 address is being assigned.
With ath0 (madwifi-ng), syslog output looks the similar upt to the point
where the DHCP-DISCOVER messages aren't answered. If there's other WLAN
SSIDs "in the air", another one from the list is picked an joined. If no
other WLANs are detected, ath0 is deactivated - although it had joined
the DHCP-less WLAN successfully. The WLAN Access Point [Cisco Aironet
1231-G, IOS 12.2(8)JA] shows a fully associated WLAN client.
What is the reasoning behind deactivating the WLAN NIC after a
successful join but a failed attempt at getting an address via DHCP? Why
is there no fallback to zeroconf (if it is installed)?
After all, in 6.06, this did work, and I made use of it extensively to
work around the "no static IP adressing" limitation of NetworkManager.
regards
Marc
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
can't join non-DHCP WLANs, no fallback to zeroconf addressing
https://launchpad.net/bugs/71748
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
