Re: [Cooker] dhclient config "broken" after 9.0 -> 9.1RC2 upgrade

[Henri]

Buchan Milne wrote:

On Sun, 16 Mar 2003, Henri wrote:

 

If it does, that is even better, and
should work out-the-box. The installer should know which ones don't (may
be your case), and in that case will try bring up dhcp anyway. You can
check with :
# ifstatus -v
    
         

it answers unplugged when i'm unplugged...great !
  
       

But does it answer that you are plugged when you are plugged?

     

Yes !

   

Col! Which card? (I want to replace this 3c589B I have with something that 
supports ifplugd ...)

My card is a RealTeck 8139too. It suppors all three features shown b 
ifplugd. THAT'S REALLY COOOLL ! now at boot time, if i'm not connected 
it just says "failed" and don't wait for any server to answer. I load 
the interface without any ip adresse, and when i plug the network cable, 
the network get working immediatly ! THANKS mandrake !!!!

 

add in /etc/sysconfig/network:
NOZEROCONF="yes"
    

         

this does not work. I made a service network stop, ifdown eth0, ifdown 
"eth0:9".
then added what you said to the config file and while i'm NOT connected 
i enter service network restart. It looks for a dhcp server, does not 
find it of course and...create a zeroconf interface "eth0:9" with 
ipadress = 169.254.xxx.xxx (don"t remember the end...) and the 
associated defaut route.
any idea ?

       

Maybe the installer put MII_NOT_SUPPORTED=yes in your 
/etc/sysconfig/network-scripts/ifcfg-eth?, thinking your card does not 
support ifplugd. If ifstatus always gives you the right answer, either 
remove this, or run drakconnect in expert mode and enable "network 
hotplugging", which should do the same thing.

     

done tonight via drakconf after upgrade from cooker. Zeroconf seems 
desactivated now, but i'll have to redo some tests tomorow.
I'll check tomorow if there is something about MII_NOT_SUPPORTED 
too...but i don't think there is one, as the nic card does suport ifplugd.
   

But, the thing is that ifstatus sometimes can't tell if it is supported, 
so the installer decides whether it thinks ifstatus will work or not, 
because enabling ifstatus on cards which lie about their status can be 
very bad ...

 

If you have MII_NOT_SUPPORTED=yes (like I do, my card does not give any 
output for ifstatus), then dhcp/zeroconf will be used, since the system 
can't tell that you are not connected, and wants to make sure you get a 
connection if you are.

     

Thanks. I read the man page of ifplugd after having ask the 
question...but i'm still not sure to know what it exactly does : when it 
detect the cable is plugged, it reads the config file and launch dhcp 
(or use a static ip depending on the config) and modify the defaut 
gateway ? what if you plug the network cable while surfing the net via a 
modem ?
   

If the cable is disconnected, and you connect it, it runs 'ifup <device>'. 
Then, if you disconnect the cable, it will run 'ifdown <device>'.

If you are browsing on your modem, and you connect, either
1)Your dhcp server tells you about a gateway, in which case it will 
probably be set as the default route
2)Your dhcp server doesn't tell you about a gateway, and nothing changes.
 

I'll try to make a test ASAP...thanks !

So, make sure your dhcp server only tells you about a gateway that is 
faster than your modem ;-).

Of course, I haven't tested all of this extensively, but that is how it 
should work. If your dhcp servers lie, get your admin to fix it ...

Of course, ideally dhcp servers should be able tell you the 'metric' of 
the gateway, so that multiple 'default' routes could be setup, and the 
faster one will 'win'. But I am not sure if the RFCs support that, and if 
they do, if the server and client software supports it.

Regards,
Buchan