From owner-freebsd-net@FreeBSD.ORG Tue Nov 23 12:35:43 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C7981065672 for ; Tue, 23 Nov 2010 12:35:43 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id E074F8FC1B for ; Tue, 23 Nov 2010 12:35:42 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 514BEBDC75 for ; Tue, 23 Nov 2010 04:35:42 -0800 (PST) To: freebsd-net@freebsd.org In-Reply-To: <4CEBAD46.2070301@acm.poly.edu> Date: Tue, 23 Nov 2010 04:35:42 -0800 Message-ID: <42097.1290515742@tristatelogic.com> From: "Ronald F. Guilmette" Subject: Re: Configuring for 1 static and 1 DHCP interface ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2010 12:35:43 -0000 In message <4CEBAD46.2070301@acm.poly.edu>, Boris Kochergin wrote: >Hi. I hypothesize that ntpd is started before your rc.local script is >run, so it uses the NAT IP and default route. Take a look at the >dhclient.conf man page for how to ignore certain DHCP-provided >information for an interface. Thanks Boris. I _did_ actually look over that man page before I posted, but I could not really make heads or tails out of it, due to the lack of any actual examples. >For example: > ># cat /etc/dhclient.conf >... >interface "wlan0" { > supersede domain-name "poly.edu"; > supersede domain-name-servers 128.238.9.202; >} > >The above overrides any DHCP-provided domain name and DNS servers with >what I have above on the wlan0 interface. Whoa! OK, I see now... I failed to take note of the small SEE ALSO annotation down at the bottom of the man page for dhclient.conf(5)... you know... the one that says SEE ALSO dhcp-options(5). Obviously, that's where all of the magic symbols that can be diddled are listed. (And that's the main thing I didn't know.) Well, OK, so now I'll try and see if I can get a proper outcome by using interface "rl0" { supersede routers 69.62.255.254; supersede domain-name-servers 127.0.0.1; } Thanks for giving me something I can work with. I should say however that even this is going to produce a slightly sub-optimal result, because (I guess) the DHCP client is _still_ going to wipe out my eisting /etc/resolve.con file and then write its own. Now that will at least have the proper IP address in it _however_ there does not seem to be any way to entice the DHCP client to place certain "options" into the /etc/resolv.conf file. That's a pity, because I wanted one in there. (Oh well, I guss I can append it from my /etc/rc.local file.) Anyway, thanks again. I should know soon if this fixes that ntpd problem. Regards, rfg