Skip site navigation (1)Skip section navigation (2)
Date:      13 Aug 2002 20:36:39 +0400
From:      "Vladimir B. " Grebenschikov <vova@sw.ru>
To:        Mike Makonnen <makonnen@pacbell.net>
Cc:        "current@freebsd.org" <current@freebsd.org>
Subject:   Re: rcNG and dhcp
Message-ID:  <1029256599.741.18.camel@vbook.express.ru>
In-Reply-To: <20020813090036.090538bf.makonnen@pacbell.net>
References:  <1029141620.800.14.camel@vbook.express.ru>  <20020813090036.090538bf.makonnen@pacbell.net>

next in thread | previous in thread | raw e-mail | index | archive | help
=F7 Tue, 13.08.2002, =D7 20:00, Mike Makonnen =CE=C1=D0=C9=D3=C1=CC:
> On Mon, 12 Aug 2002 12:40:20 +0400
> "Vladimir B.  Grebenschikov" <vova@sw.ru> wrote:
>=20
> >=20
> > Hi=20
> >=20
> > There is patch to teach rcNG do not try dhcp on not-connected ethernet.
> >=20
> > simply put
> > ifconfig_fxp0=3D"dhcp-if-carrier"
> > into rc.conf
> >=20
> > It will be interested to somebody
> >=20
> > Theoretically there are another solution for problem - add new key to
> > dhclient - check interface media before broadcasting.
>=20
> Yes, there is a simple solution: adjust the timeout in dhclient.conf.

It is not solution - it is workaround=20
  - I do not wand any dhcp activity if I have no media (say in car)
    And dhclient in case of failure of detecting network address will
    install lask seen one, with last seen default gateway and I will get
    very long timeout while any of my apps will try to reach network
    instead of instant 'no route to host'

> I will quote David Malone from PR conf/38559:
> <<<<
> I would have said that it would be a bug not to do DHCP if the
> interface has been configured for it and might upset people who
> want to be able to plug the network cable in at a more leasurely
> pace when they boot their laptops.
>=20
> It also means that dhclient won't be able to use a lease listed in
> its lease file, even if that lease is valid and the hub/switch/access
> point you're connected to happens to be temporally down or out of
> range.
>=20
> I'd suggest that you try reducing the timeouts if the long timeout
> isn't suitable for your setup. See the timeing options in dhclient.conf
> man page.
> >>>>
>=20
>=20
> Cheers,
> Mike.
>=20
> >=20
> > --=20
> > Vladimir B. Grebenschikov
> > vova@sw.ru, SWsoft, Inc.
> >=20
--=20
Vladimir B. Grebenschikov
vova@sw.ru, SWsoft, Inc.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1029256599.741.18.camel>