Net issue - can't start wireless w/o an AP [SOLVED]

[abacker]

I am having a problem that I think is related to the new baselayout, but not sure. I had to recompile tons of stuff because of the new xml parser. I now get some strange networking stuff going on, but I can make eveyrthing work manually if I try. Here is what is happening :

net.eth0 = wired (never used)
net.eth1 = wireless (used always, and in 'default' runlevel).
net.lo = well, of course. as 'boot' level.

I get "Device initiated servce : net.eth0" on boot. This brings up the interface, which is never actually connected to anything. No biggie, I hope, but I hate waiting for it to DHCP. Is there any way to figure out what is trying to start it? I don't have it loading at boot.

After that, the system tries to bring up net.eth1, which it should. However, it fails when there is no AP that it can get on, and so it says the interface can not start. Because of this, apache/netmount both can not start.

Is there any way to fix this? It doesn't matter if there is no wireless, but that shouldn't stop me from loading apache and using it locally, right? The interface should start, just not be on any particular AP. It works great at home, where It picks up my local net just fine, and everythign starts as it should.

Thanks,
Andrew

[jubajuba]

I have the "same" problem. I've got two wired NICs, eth0 and eth1, I only use eth1 and accordingly I only start net.eth1 with rc. After a baselayout update (since after 1.12.4-r3 I think) both NICs start on boot and I have to stop net.eth0 after boot and restart/start the network services. Really annoying. Anyone know why and/or have a fix? I'm using baselayout 1.12.4-r6 now.

[jubajuba]

Solved this one now, don't know if it's a good solution, but it should work for you too. I edited /etc/conf.d/rc RC_PLUG_SERVICES and added !net.eth0 , this stops the loading of net.eth0 and works brilliantly here. See the file for more usage info.

[UberLord]

I get "Device initiated servce : net.eth0" on boot. This brings up the interface, which is never actually connected to anything. No biggie, I hope, but I hate waiting for it to DHCP. Is there any way to figure out what is trying to start it? I don't have it loading at boot.

Look into coldplug options in /etc/conf.d/rc or emerge netplug to manage wired intrfaces.
This question is currently being asked once a day

After that, the system tries to bring up net.eth1, which it should. However, it fails when there is no AP that it can get on, and so it says the interface can not start. Because of this, apache/netmount both can not start.

Is there any way to fix this? It doesn't matter if there is no wireless, but that shouldn't stop me from loading apache and using it locally, right? The interface should start, just not be on any particular AP. It works great at home, where It picks up my local net just fine, and everythign starts as it should.

You can use the RC_STRICT_NET_CHECKING var in /etc/conf.d/rc.
none or lo are probably what you want.

[abacker]

Thanks for your help, and I wish I had not bothered everyone again

I was playing with this last night after I posted, and I found something in another topic that made me look at the RC file again. Reading the comments it was obvious what I had to do! Here is what I did :

/etc/conf.d/rc
Edit this to make LO be counted as an UP interface, so nothing needs to be connected at boot. This makes netmount/apache/others start up even if there are networks other than local/127.0.0.8.

Code: Select all

RC_NET_STRICT_CHECKING="lo"

I will address the other issue in a minute, since I just go the little gentooey laptop running again.

- Andrew

[James Wells]

Greetings,

I get "Device initiated servce : net.eth0" on boot. This brings up the interface, which is never actually connected to anything. No biggie, I hope, but I hate waiting for it to DHCP. Is there any way to figure out what is trying to start it? I don't have it loading at boot.

Pretty much everything else has been answered for you, but I thought I would add an extra bit here. I too use a laptop with both wired and wireless. I almost never use the wired, however, I still start it up on boot, but I use netplugd to test the link. This way, DHCP doesn't fire unless there is a network link.

Strangely, I did this simply to ensure that Xen always has an ethernet device to link to, besides loopback of course.

[abacker]

Netplugd sounds like just what I need. For the moment I have just disabled anything from starting net.eth0 by

Code: Select all

RC_PLUG_SERVICES="!net.eth0"

This might not be exactly what I want, but I need it to stop trying to get an IP, since I can't stand the wait

Thanks for the tip

- andrew