Date: Sat, 8 Aug 1998 08:40:56 +1200 From: "Dan Langille" <junkmale@xtra.co.nz> To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: DHCP configuration (was "changes to file are lost") Message-ID: <199808072040.IAA05754@cyclops.xtra.co.nz> In-Reply-To: <Pine.BSF.4.00.9808061146170.28098-100000@resnet.uoregon.edu> References: <199807312331.LAA26654@cyclops.xtra.co.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
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".
> > 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?
> > BTW: I notice that if I change the 'interface "epo" {' to be
'interface
> > "ed0" {', things still work. It's always been ep0, and worked. I
would
> > have thought it should have to be ed0 in order to work.
>
> Perhaps you have both?
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.
--
Dan Langille
DVL Software Limited
http://www.dvl-software.com/freebsd : my [mis]adventures
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?199808072040.IAA05754>