eth0 always starts with rc.d/network start

dtw · 2005-03-08 09:26:38

Here is the relevant bit from my rc.conf

lo="lo 127.0.0.1"
eth0="eth0 192.168.1.5 netmask 255.255.255.0 broadcast 192.168.1.5"
#eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo !eth0 eth1)

but eth0 always starts. I am using a wireless card on eth1 to connect to the web and eth0 is a builtin NIC - it's really annoying!

jp_fielding · 2005-03-08 12:31:23

same here, twice actually a co-worker with the identical setup first noticed that problem.

skoal · 2005-03-08 16:12:51

Hmmm...I kind of remember this same problem a while back when using a Cisco wireless plus my eeepro100 integrated NIC.

I believe the issue in this case was the order in which I listed each NIC module in the MODULES array. There is a way to just get the interfaces loaded that you want. I did exactly what you want, but can't remember the specifics.

Make sure the order which you list your NIC modules matches your eth[x] interfaces. If that's not the case, rearrange the order (and definitions) of your NIC interfaces you listed. In other words, swap the definitions of eth1 with eth0 and match the order in your MODULES array.

I think that did it for me...but am not quite sure.

dtw · 2005-03-09 11:27:09

um - as you can see from my rc.conf - that isn't gonna work for me!

I'm going to file a bug report

lucke · 2005-03-09 12:50:38

Aren't you possibly using hotplug, dibble? I dunno if it interferes with static setup, but it does have its own scripts to up the interfaces.

dtw · 2005-03-10 11:01:52

really? I didn't know that - it could be that then! thanks - i'll check it out

skoal · 2005-03-10 18:58:06

dibblethewrecker wrote:

um - as you can see from my rc.conf - that isn't gonna work for me!

I saw your "rc.conf". What I'm trying to explain to you is an easy sol'n. You seem to have you integrated NIC disabled anyway. What I offered was what worked for me. Of course, this was before hotplug was being used, so I don't know how that adds into the mix...

I guess your post was more of a "concern as to why this is occuring" than a sol'n. What I meant, in case of confusion was this:

MODULES=(...,<wireless NIC>,<integrated NIC>...)
eth0="dhcp"
eth1="eth1 192.168.1.5 netmask 255.255.255.0 broadcast 192.168.1.5"
INTERFACES=(lo eth0 !eth1)

I believe that's what gave me a eth0 only interface, with no eth1, and eth0 was my wireless NIC. I don't think you'll have to worry what hotplug is doing that way. I may be wrong...

puntmuts · 2005-03-10 22:34:20

You could prevent hotplug from loading the module for that specific hardware if you add the module name to the hotplug blacklist located in /etc/hotplug.

dtw · 2005-03-12 12:16:37

i think i'll just try the new initscripts

apeiro · 2005-03-15 23:46:51

The new initscripts should fix this problem.

dtw · 2005-03-16 11:34:09

it does, thanks judd

Arch Linux

#1 2005-03-08 09:26:38

eth0 always starts with rc.d/network start

#2 2005-03-08 12:31:23

Re: eth0 always starts with rc.d/network start

#3 2005-03-08 16:12:51

Re: eth0 always starts with rc.d/network start

#4 2005-03-09 11:27:09

Re: eth0 always starts with rc.d/network start

#5 2005-03-09 12:50:38

Re: eth0 always starts with rc.d/network start

#6 2005-03-10 11:01:52

Re: eth0 always starts with rc.d/network start

#7 2005-03-10 18:58:06

Re: eth0 always starts with rc.d/network start

#8 2005-03-10 22:34:20

Re: eth0 always starts with rc.d/network start

#9 2005-03-12 12:16:37

Re: eth0 always starts with rc.d/network start

#10 2005-03-15 23:46:51

Re: eth0 always starts with rc.d/network start

#11 2005-03-16 11:34:09

Re: eth0 always starts with rc.d/network start

Board footer