[ Next-in-Thread ]  [ Next Message ] 

Package name confusion, and a fix 

Forum: PCMCIA Network Adapter Issues
Re: Question: route add unnecessary for dhclient? (Adam Goode)
Re: I'm not sure (David Hinds)
Re: Feedback: dhclient for Linux (Adam Goode)
Date: 2000, Feb 24
From: David Hinds <dhinds@pcmcia.sourceforge.org> 

Oh, Debian calls it dhcp-client, which threw me off.  It appears to me
that the right fix is just to change that route command to:

  route add default dev $DEVICE netmask 0.0.0.0

which should work for any DHCP client that needs it, and should be
harmless for any client that does it on its own.

-- Dave

[ Next-in-Thread ]  [ Next Message ] 

Messages Inline: [ 0 ]  [ All ]  Outline: [ 1 ]  [ 2 ]  [ All ] 

More: Hmmm, almost, but not quite

Re: Package name confusion, and a fix (David Hinds)
Date: 2000, Feb 24
From: Adam Goode <goodea@rpi.edu>

Yes, but this still switches the default route from the first ethernet card inserted to the second. Basically, whichever card is added last becomes default route.

My main trouble is that the second ethernet card is a wireless card, so that if I am not near an access point, dhcp fails and shouldn't change any route. This preserves my wired ethernet card as default. In general, though, I think I want to be able to select an interface to be preferred default route (because the default should be the wired card if that's active).

Is there a better solution to this (perhaps) more general problem of picking an interface to be default route?

Let me know if I've confused anyone terribly. (Besides myself.)

Adam Goode

1. Argh by David Hinds, 2000, Feb 24
Package name confusion, and a fix

[ Add Message ]  to: "Package name confusion, and a fix"

[ Members ]  [ Subscribe ]  [ Admin Mode ] 
[ Show Frames ]  [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]