Package: ifupdown
Version: 0.6.8
Severity: important

*** Please type your report below this line ***
My box has two network cards, one ethernet card (using sky2) and one 
wireless card (ipw2200).  The ethernet connection is faster than the 
wireless (802.11b) but I keep the wireless around as the router it is 
attached to is easier to configure vis-a-vis port forwarding.

The sky2 is eth0, the ipw2200 is eth1.  They have both coexisted 
succesfully for a long while.  As of recently though they do not (since 
the problem  is intermittent and networking sometimes works, I can't 
pinpoint exactly when the change occurred, but was I believe in the 
last couple weeks). 

Both interfaces are assigned addresses from their respective routers via 
DHCP: sky2 gets 10.0.9.*, ipw2200 gets 192.168.0.*

The problem is ifup seems to be getting the interfaces mixes up.

ifconfig currently shows 
eth0      Link encap:Ethernet  HWaddr 00:16:E6:82:E4:E0
          inet addr:192.168.0.107  Bcast:192.168.0.255  
Mask:255.255.255.0
...
eth1      Link encap:Ethernet  HWaddr 00:16:6F:B0:53:E9
          inet addr:10.0.9.3  Bcast:255.255.255.255  Mask:255.255.255.0

and my connection works, even though eth1 (supposed to be ipw2200) has 
an address in the range assigned by the router to which eth0 (sky2) is 
physically attached.  

iwconfig shows 
eth0      no wireless extensions.

eth1      IEEE 802.11b  ESSID:"dlink"

According to iwconfig, eth1 is the wireless card (as it should be) but 
ifconfig shows that eth1 has an address assigned by the wired router.  
This _works_ but is highly strange.  

Worse is that running ifup -a again (through /etc/init.d/networking 
restart, or directly, or by rebooting or whatever) returns completely 
random results.  Running ifdown -a and then ifup -a right now shows
dhcpcd.sh: interface eth0 has been configured with new IP=10.0.9.4
dhcpcd.sh: interface eth1 has been configured with new IP=10.0.9.3

so now both interfaces have an address in the range assigned by eth0 
(sky2)'s router.  Doing the same thing again may show both with a 
192.168.0.* address.  It is completely inconsistent.  The practical 
effect is a 50/50 chance of no working network connection on any 
reboot/networking restart/ifup -a

ifconfig now shows
eth0      Link encap:Ethernet  HWaddr 00:16:E6:82:E4:E0
          inet addr:10.0.9.4  Bcast:255.255.255.255  Mask:255.255.255.0
...
eth1      Link encap:Ethernet  HWaddr 00:16:6F:B0:53:E9
          inet addr:10.0.9.3  Bcast:255.255.255.255  Mask:255.255.255.0


From what I understand modules may not always load in the same 
order, and that sky2 might not always be eth0, and ipw2200 might not 
always be eth1. But without even rebooting, to run ifup -a and come up 
with different results each time is very disconcerting, and certainly never 
happened before.  

I just can't figure out why ifup gives different results each time 
(not something that happened previously) and why both cards, connected 
to different routers can appear to have an address assigned by the 
same router, or both with an address assigned by the router to which 
they are not connected, etc.  

If the bug is elsewhere, I'd appreciate any assistance tracking it down.

/etc/network/interfaces:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
wireless-essid dlink


/etc/udev/rules.d/z25_persistent-net.rules:
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:16:e6:82:e4:e0", 
NAME="eth0"

SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:16:6f:b0:53:e9", 
NAME="eth1"


dmesg | grep sky2
[   41.241870] sky2 0000:04:00.0: v1.14 addr 0xf4000000 irq 16 Yukon-EC (0xb6) 
rev 2
[   41.241949] sky2 eth0: addr 00:16:e6:82:e4:e0
...

dmesg | grep eth1
[  650.750267] eth1: no IPv6 routers present



-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.22.1 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages ifupdown depends on:
ii  debconf [debconf-2.0]         1.5.14     Debian configuration management 
sy
ii  libc6                         2.6.1-1+b1 GNU C Library: Shared libraries
ii  lsb-base                      3.1-24     Linux Standard Base 3.1 init 
scrip
ii  net-tools                     1.60-17    The NET-3 networking toolkit

ifupdown recommends no packages.

-- debconf information:
  ifupdown/convert-interfaces: true


Reply via email to