From owner-freebsd-net Sat May 30 23:35:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12096 for freebsd-net-outgoing; Sat, 30 May 1998 23:35:18 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from coconut.itojun.org (root@coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12068 for ; Sat, 30 May 1998 23:34:50 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from localhost (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.8.8+3.0Wbeta12/3.6W) with ESMTP id PAA15731; Sun, 31 May 1998 15:32:58 +0900 (JST) To: listuser@seifried.org cc: "Pitcairn, Duncan" , "'dhcp-client@fugue.com'" , "'freebsd-net@freebsd.org'" In-reply-to: listuser's message of Sun, 31 May 1998 00:04:53 CST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: Move a value from dhcp client on interface to dhcp server on othe r interface From: Jun-ichiro itojun Itoh Date: Sun, 31 May 1998 15:32:58 +0900 Message-ID: <15727.896596378@coconut.itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >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