[SOLVED] ifup -a not working

grail · 03-01-2010, 12:42 AM

Hello

So I thought I was getting the hang of networking stuff, but, apparently not. Anyhoo, I have a startup script (very basic one liner)

ifup -a

Reading the man page for ifup it says this should bring up all devices listed in interfaces file (so contained in there I have):

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

After starting my machine I run ifconfig which returns no output.
If I do ifup eth0 I get: ifup: interface eth0 already configured

So finally, if I run dhcpcd this brings up my nic. If I then do ifdown -a and kill the dhcpcd process and then manually type ifup -a, it all magically comes back.

Would someone explain what step I am missing in the process to have all my cards startup as part of the boot process?

Cheers
Grail

PS. Let me know if anymore details are required?

dtlp · 03-01-2010, 10:04 AM

what's the output of your /etc/sysconfig/network-scripts/ifcfg-eth0 ?

ONBOOT=yes should be set.

grail · 03-02-2010, 12:16 AM

Hmmmm ... I do not have this file nor entry at all, but I have also found that after machine has booted
if I simply run ifup -a at the command line that nothing starts up either

So the file you have listed may / mat not be needed but I obviously have another underlying issue

davcefai · 03-02-2010, 12:28 AM

ifup is an executable program, not a script. On my Debian system it is /sbin/ifup.

Have you replaced this by your own script?

vinaytp · 03-02-2010, 12:40 AM

Hi Grail,

Quote:

Originally Posted by grail

Hmmmm ... I do not have this file nor entry at all,(

It seems you are using Ububtu, mostly you have to search for /etc/network/interfaces/ifcfg-eth0.

If you are getting IP, Netmask, DNS entries from DHCP server then contents of /etc/network/interfaces/ifcfg-eth0 should be similar to

Code:

DEVICE=eht0
TYPE=ethernet
BOOTPROTO=dchp
ONBOOT=yes

Now you can restart your network

Code:

# /sbin/services network restart

Then check

Code:

# /sbin/ifconfig

If the issue persists please paste the output of above commands.

evo2 · 03-02-2010, 01:12 AM

It seems all the advice (except #4) you have received so far is from people who are unfamiliar with Debian style networking. Your /etc/network/interfaces file seems to be ok. I suspect the problem is that the device is not seen. Can you please post the output of:

Code:

ifconfig -a
lspci | grep -i ether
uname -a
cat /etc/debian_version

Cheers,

Evo2.

zhjim · 03-02-2010, 02:32 AM

Maybe one should see what the situation is before and after the ifup -a in your script. Specially during boot things change very frequently as drivers getting loaded, daemons getting started and alike. So maybe just put a little script like this in front and after ifup -a

Code:

cat << EOF
#!/bin/bash
FIX=$1
/sbin/ip link > ipl.$FIX
/sbin/ip addr > ipl.$FIX
/sbin/lspci > ipl.$FIX
/sbinlsmod > ipl.$FIX
EOF > status
chmod a+x ./status

(Dunno if the pathes are right. just make sure they are absolute)

Then change your script to something like this

Code:

status before
ifup -a
status after

P.S. I just saw that you are using ifconfig so justs replace ip with the appropiate ifconfig lines.

grail · 03-02-2010, 09:11 PM

Ok ... thanks all for the replies.

1. I have not replaced the ifup executable, it is the one line in my bootup script
2. The system I am running into this issue on is not my Ubuntu system, but a source based distro of my own making (very early stages)

3. ifconfig -a yields:

Code:

eth0      Link encap:Ethernet  HWaddr 08:00:27:AE:BE:C5  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback  
          LOOPBACK  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lspic | grep -i ether:

Code:

 00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

uname -a:

Code:

 Linux ripclaw 2.6.27.10-SMGL-iso #1 Mon Feb 2 18:34:19 UTC 2009 i686 GNU/Linux

And as you can see from last entry, the cat is not an option as not debian.

All of the above is after a fresh install.

4. Will post output from script by zhjim if still required

Cheers Grail

evo2 · 03-02-2010, 09:14 PM

Does the following bring the interface up:

Code:

ifup eth0

If not the problem may be that you need to bring it down first (I know it is not really up)

Code:

ifdown eth0
ifup eth0

Evo2.

evo2 · 03-02-2010, 09:18 PM

I just reread you post #8. Regarding 2.
Are you using upstream sources and designing your networking in a similar fashion to Debian or are you actually using Debian sources?

Evo2.

grail · 03-03-2010, 12:18 AM

Code:

 ifup eth0
ifup: interface eth0 already configured

ifdown eth0
dhcpcd: dhcpcd not running

ifup eth0
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
dhcpcd: version 5.0.9 starting
dhcpcd: eth0: rebinding lease of 10.0.2.15
dhcpcd: eth0: acknowledged 10.0.2.15 from 10.0.2.2
dhcpcd: eth0: checking for 10.0.2.15
dhcpcd: eth0: leased 10.0.2.15 for 86400 seconds
dhcpcd: forking to background

And so now it is up??? So why does it have to go down first?

Yes to upstream sources.

evo2 · 03-03-2010, 12:41 AM

ifup tries to keep track of the whether the interface is up or down using the file /etc/network/run/ifstate
Sometimes this can get out of sync with the true state of the device. In such a case you can use "ifdown eth0" to get the ifstate file back in sync, or you can use the --force option to ignore the ifstate file. All of this is documented in the man page.

Cheers,

Evo2.