Date: Sun, 31 May 1998 15:32:58 +0900 From: Jun-ichiro itojun Itoh <itojun@itojun.org> To: listuser@seifried.org Cc: "Pitcairn, Duncan" <DuncanP@Cairnwood.com>, "'dhcp-client@fugue.com'" <dhcp-client@fugue.com>, "'freebsd-net@freebsd.org'" <freebsd-net@FreeBSD.ORG> Subject: Re: Move a value from dhcp client on interface to dhcp server on othe r interface Message-ID: <15727.896596378@coconut.itojun.org> In-Reply-To: listuser's message of Sun, 31 May 1998 00:04:53 CST. <Pine.LNX.3.96.980531000036.8489A-100000@seifried-gateway.v-wave.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>In Linux it writes the DNS info to /etc/resolv.conf: >domain blah.com >nameserver 2.2.2.2 >nameserver 2.3.3.2 >etc...... I would imagine you could write a script that would start the >client dhcp up, attach to the cablemodem, get the info, you're now on the >network, then strip the needed info from resolv.conf (or bsd equiv) and >write it to the dhcpd.conf file. Wide dhcp client (/usr/ports/net/wide-dhcp) updates resolv.conf on receipt of dns server info. However, I believe updating resolv.conf is not a best solution. To make several daemons work properly we must perform kill -HUP after the update of resolv.conf. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15727.896596378>