Bug 164816

Summary: configuration of multiple NICs broken ?
Product: [openSUSE] SUSE Linux 10.1 Reporter: Heiko Rommel <heiko.rommel>
Component: NetworkAssignee: Martin Vidner <mvidner>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Blocker    
Priority: P5 - None CC: jhill, suse-beta
Version: Beta 9   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Component Test Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 97395, 144304    
Attachments: YaST2 logs
/etc/sysconfig/network

Description Heiko Rommel 2006-04-10 09:58:28 UTC
During installation, I configured eth0 statically with 192.168.1.1 and on-link activation and eth1 dynamically via DHCP.

I deactivated the firewall.

After installation, I access the host remotely thru eth1.
There're two defects that I see:

1)

In the running system, no IPv4 is assigned to eth0.

Despite

boxer:~ # ethtool eth0
Settings for eth0:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: d
        Current message level: 0x000000ff (255)
        Link detected: yes


2)

In the running system, I reconfigued eth0 with "yast2 lan" to get up on boot (because of bug 1). In the moment that "yast2 lan" finishes the configuration the link on eth1 get's down.
Looking locally at the status of the network I see that eth1 has no IPv4 address.

Despite:

boxer:~ # dhcpcd-test eth1
dhcpcd: MAC address = 00:08:54:35:fe:ec
IPADDR=10.10.2.175
NETMASK=255.255.0.0
NETWORK=10.10.0.0
BROADCAST=10.10.255.255
GATEWAY=10.10.0.8
HOSTNAME='boxer'
DOMAIN='suse.de'
NISDOMAIN='suse.de'
ROOTPATH='/dist/8.1-i386'
DNS=10.10.0.1,10.10.2.88
DNSSEARCH='suse.de nue.novell.com'
NTPSERVERS=149.44.160.50,149.44.160.54,149.44.160.1
WINSSERVERS=149.44.160.39
NISSERVERS=149.44.160.146,10.10.0.1,149.44.160.50
LPRSERVERS=149.44.160.33
DHCPSID=149.44.160.72
DHCPGIADDR=10.10.255.254
DHCPSIADDR=149.44.160.50
DHCPCHADDR=00:08:54:35:FE:EC
DHCPSHADDR=00:03:47:97:4E:3A
DHCPSNAME='munin.suse.de'
LEASETIME=1296000
RENEWALTIME=648000
REBINDTIME=1134000
INTERFACE='eth1'
CLASSID='Linux 2.6.16-16-default i686'
CLIENTID=00:08:54:35:FE:EC
Comment 1 Heiko Rommel 2006-04-10 09:59:20 UTC
Created attachment 77471 [details]
YaST2 logs
Comment 2 Heiko Rommel 2006-04-10 10:03:35 UTC
Created attachment 77472 [details]
/etc/sysconfig/network
Comment 3 Heiko Rommel 2006-04-10 10:08:26 UTC
Sorry, I forget to mention: I tested this with build 907 (post beta9).
Comment 4 Martin Vidner 2006-04-10 12:05:26 UTC
Both cards are set up with ifplugd.
Christian, I am afraid our concept is broken.
Comment 5 Martin Vidner 2006-04-11 08:34:50 UTC
We introduced ifplugd as default to easily switch between wired and wireless (Bug 115448). I also always set IFPLUGD_PRIORITY...
I have found a mail from Sep 27 2005 about this:
> > > If you set
> > >   STARTMODE=ifplugd
> > > and
> > >   IFPLUGD_PRIORITY=...
> > > for multiple cable interfaces this will probably not be what the user
> > > wants. From all interfaces with IFPLUGD_PRIORITY, only one will be up;
> > > always that plugged interface that has highest priority.
> > > If you omit IFPLUGD_PRIORITY, the interface will be set up and down
> > > indepentently from others, when the cable of this interface is plugged
> > > and pulled.
> >
> > You are right. I need to think about it. Do you have a suggestion?
>
> Use ifplugd
>  - if computer is mobile (*)
>  - if there is one wired and one wireless interface
>
> (*) Afaik we have different ways to find out if a computer is a
> laptop. We should determine that, have a central flag during
> installation and write it to /etc/sysconfig/hardware and refer to that
> later.
> [some minutes later]
> Just heard that hal can detrmine if machine is a laptop. But i don't
> know if we get this info from hal early enough at installation time.
>
> For now:
> Only use ifplugd if there is one wired and one wireless interface.

But now that we have NetworkManager, we could turn ifplugd off by default again. How about that, Christian?

Comment 6 Christian Zoz 2006-04-11 14:34:49 UTC
Why can't you use ifplugd only on laptops?
Or omit IFPLUGD_PROPRITY if not a laptop?

I like to keep STARTMODE=ifplugd at least on laptops. There still are users that do not use NM.
Comment 7 Martin Vidner 2006-04-12 08:03:19 UTC
You are right.
Comment 8 Martin Vidner 2006-04-12 12:03:57 UTC
yast2-network-2.13.45 uses ifplugd by default only on laptops.
Comment 9 Martin Vidner 2006-04-24 09:09:12 UTC
*** Bug 166966 has been marked as a duplicate of this bug. ***