Date: Mon, 10 Aug 1998 16:26:36 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Dan Langille <junkmale@xtra.co.nz> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: DHCP configuration (was "changes to file are lost") Message-ID: <Pine.BSF.4.00.9808101624470.29015-100000@resnet.uoregon.edu> In-Reply-To: <199808072040.IAA05754@cyclops.xtra.co.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 8 Aug 1998, Dan Langille wrote: > On 6 Aug 98, at 11:50, Doug White wrote: > > > > However, if I add single prepend commands to /etc/dhclient.conf before > the > > > interface "ep0" command, I do get partial success. Here's what I > supply > > > and what I get: > > > > > > prepend domain-name "mydomain.com"; > > > prepend domain-name-servers 10.0.0.1; > > > > > > gives: > > > > > > search mydomain.commyisp.com > > > nameserver 10.0.0.10 > > > nameserver 11.22.33.44 # my ISP > > > nameserver 11.22.33.45 # my ISP > > > > > > This is strange. There are references in the man pages that I can > request > > > that the DHCP server not send me certain information (i.e. the search > > > statement), but it is not clear to me how to tell it that. > > > > > > How do I eliminate the search command, replace it with "domain > > > mydomain.com" and not have it suffixed with "myisp.com". > > > > Maybe prepend is the wrong keyword, or try > > > > prepend domain-name "mydomain.com " > > Note extra space ^ > > > > Hint: dhclient's magic is done via a script, /etc/dhclient-script. If you > > don't want both in the search path then use the `supercede' keyword > > instead of `prepend'. > > I tried the extra space and got: > > search mydomain.com myisp.com > > Then I tried the supersede instead of prepend and got: > > search mydomain.com > > Which is not quite what I wanted (domain mydomain.com), but at least my > system will be running after a reboot. > But reading man resolv.conf shows that "search" should be sufficient > instead of "domain" as the hostname in question contains "mydomain.com". Yup. > > > Another issue is that after initiating dhclient edo, I must manullay > redo > > > my ed1 details via ifconfig ed1 10.0.0.5 255.255.255.0. Is that to be > > > expected? > > > > No. dhclient configures all Ethernet interfaces by default, but you can > > specify with interfaces to listen on via the command line, like > > > > dhclient ep0 > > > > to specifically listen on ep0. > > This is interesting. I have ed0 (outside world) and ed1 (my subnet) on > this box. If I issue "dhclient ed0", ed1 is also reconfigured and I must > issue "ifconfig ed1 10.0.0.5 255.255.255.0" before comms work again . > This appears to conflict with the man pages on dhclient. Any ideas? If ed1 ever obtained a DHCP lease, the system may try to re-acquire it. Try quitting dhclient and removing /var/db/dhclient.leases. > I have only ed1 and ed0. No 3Com cards in this box. OK. I give up. > Perhaps dhclient didn't find ep0 but found ed0, so it configured that. I think my ep0 should have been ed0, a typo crept in somewhere. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.00.9808101624470.29015-100000>