(Dapper) Changed interface name after wpa_supplicant upgrade

[crimsun at fungus.sh.nu]

Hi,

On Sun, Nov 27, 2005 at 12:20:19PM -0500, Stephen R Laniel wrote:
> I'm not sure if they're connected, but there was just a
> wpa_supplicant upgrade in Dapper, and now my wireless
> interface is called eth1; it used to be eth0. This is quite
> annoying: it means, among other things, that I have to
> change a bunch of my scripts to use eth1 rather than eth0,
> have to change /etc/default/wpasupplicant to apply to the
> correct interface, have to modify /etc/network/interfaces to
> apply the wireless-tools settings to the appropriate
> interface, etc.

The change is related to the detection order. As the person who touched
wpasupplicant in Breezy and Dapper last, one of the outstanding issues
that has been reported both in Debian and in Ubuntu is the fact that
wpasupplicant was started _after_ networking is started (and also after
ntpdate), which means that people who have only wireless connectivity
could not receive a DHCP lease. This situation has been handled
gracefully in the postinst script so that wpasupplicant is started at
boot prior to networking.

In other words, the change in interface order is a red herring and is
not related to the wpasupplicant update(s).
-- 
Daniel T. Chen            crimsun at ubuntu.com
GPG key:   www.sh.nu/~crimsun/pubkey.gpg.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20051127/e9d2b3c1/attachment.sig>