It isn't uncommon for laptops to have multiple NICs, but only have one plugged in at a time. I.e. Their is the built-in NIC and the user might have a PCMCIA wireless nic. Currently if either NIC is not plugged in any service that "needs" virutal/net fails to start. This shouldn't be the case since the machine DOES have network access via the other card. The only potential problem I see here is that loopback is also a net script and just having loopback started probably should't be enough to be considered metting the requirements for virutal/net. Maybe if Loopback and one other deivce start succesfully it could be considered up.....Any ideas? Thanks, Sean
I dont understand ... how does it have networking if *both* NICs fails to initialize ? I can understand that you want it to give the ok if one net.eth? started, but there should be at least one net.eth? started besides net.lo for what I consider a working network ...
I said if EITHER nic fails, not both. The assumption you might making is that they are both ETH devices, which is not the case. One shows up as eth0 and one shows up as wlan0 (the wireless card). And I assume that at least a few other net.* devices are avaliable (maybe ppp0 or slip0). So, basically virtual/net should be considered up if I can ping the internet, not just if all net.* devices comes up which is currently the case. If either net.eth0 or net.wlan0 fails the virtual/net fails and all services requriing virtual/net fail. Sean
So I gathered, but just wanted to make sure. We are trying to resolve the whole pcmcia and rc-scripts issue currently, as it needs some special handeling. I will look into this while we figure pcmcia out. Thanks
Thanks. I'd be happy to help or test some things out if you would like. Sean
On my to-do list if anybody wondered.
Another thought on this: If I have net.eth0 and net.wlan0 as it stands now, I typically only have net.eth0 start in the default init so that my services requiring virtual/net will start. However, if I bring up net.wlan0 and then bring down net.eth0 all my services relying on virtual/net also come down even though I still have network access. A restart may be appropriate so they grab any new network information, but they shouldn't stop. Sean
*** Bug 4752 has been marked as a duplicate of this bug. ***
It would nice too to stop one net-service without stopping all other services depending on net, if at least one net-device is left. E.g. stopping net.ppp0 shouldn't stop other services it net.eth0 or something other net.* is still active.
This two is maybe not 100% the same, but I think they have at the core the same problem. Anyhow, as for the stopping without everything depending on net stopping as well, try: # /etc/init.d/net.eth? pause that is what the "pause" command is for .... stopping stuff without their dependancies.
What is the status on that? I have the same trouble. Every time I eject my wireless card, all the services that depend on virtual/net will be shutdown, even if eth0 is up. I can see 2 fixes: * Change the "stop" to "pause" in the network pcmcia script. * Have a reference counting on the script that provide virtual/net and only stop the depending services when the count is <1
This should be fixed with baselayout-1.8.5.5 and later.