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
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
Buchan Milne wrote:
Henri wrote:
Hi,
I upgraded from 9.0 to 8.1 rc2.
My notebook is dynamically configured when i'm linked to the lan via
dhclient.
When i'm not connected, i don't want dhclient to wait too long for the
dhcp server response. That's why i have added a shorter timeout in
On Sat, 15 Mar 2003, Henri wrote:
Buchan Milne wrote:
Henri wrote:
Does you NIC not support ifplugd?
What is this ? I don't know anything about it.
ifplugd watches to see if you are connected. If you were connected, and
you disconnect the network cable, it will take the interface
Buchan Milne wrote:
On Sat, 15 Mar 2003, Henri wrote:
Buchan Milne wrote:
Henri wrote:
Does you NIC not support ifplugd?
What is this ? I don't know anything about it.
ifplugd watches to see if you are connected. If you were connected, and
you disconnect the network cable,
Hi,
I upgraded from 9.0 to 8.1 rc2.
My notebook is dynamically configured when i'm linked to the lan via
dhclient.
When i'm not connected, i don't want dhclient to wait too long for the
dhcp server response. That's why i have added a shorter timeout in
dhclient.conf.
The problem is that after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henri wrote:
Hi,
I upgraded from 9.0 to 8.1 rc2.
My notebook is dynamically configured when i'm linked to the lan via
dhclient.
When i'm not connected, i don't want dhclient to wait too long for the
dhcp server response. That's why i have added
