Your message dated Sun, 10 Jan 2016 21:56:38 +0100
with message-id <[email protected]>
and subject line Re: Bug#444194: ifupdown not configuring second e1000 card
has caused the Debian Bug report #444194,
regarding ifupdown not configuring second e1000 card
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
444194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444194
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: hello
Version: 1.3-16

After a sarge->etch upgrade, eth1 is not being configured upon reboot.  
/etc/init.d/networking restart configures the card.  My work-around is to put 
"/sbin/ifup eth1" at the start of /etc/init.d/portmap

Here is my interfaces file:

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
        address 216.7.88.132
        netmask 255.255.255.0
        network 216.7.88.0
        broadcast 216.7.88.255
        gateway 216.7.88.1
        dns-nameservers 216.7.88.71
        dns-search chinoc.net

auto eth1
iface eth1 inet static
        address 10.10.10.210
        netmask 255.255.255.0
        network 10.10.10.0
        broadcast 10.10.10.255

I am using Debian GNU/Linux 4.0, kernel 2.6.18-4-686 and ifupdown 0.6.8.

-- 
Ward... James Ward
Linux System Administrator
System Administration
Phone:  520-290-0910 ext 268
Fax:    520-546-3442
ICQ:    201663408
Jabber: [email protected]




--- End Message ---
--- Begin Message ---
ifupdown doesn't create interfaces, it only configures them. So if eth1
is not there during boot, there is nothing ifupdown can do about it. If
it is a hotplugging interface, use "allow-hotplug eth1" instead of "auto
eth1".

Since it's such an old bug, I'm just closing it right now. I suspect
it's not an issue anymore. But if the problem still exists, feel free to
reopen this bug.

-- 
Met vriendelijke groet / with kind regards,
      Guus Sliepen <[email protected]>

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to