Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.lava.net!coconut!www.nntp.primenet.com!nntp.primenet.com!news.mathworks.com!worldnet.att.net!cbgw2.lucent.com!news.bu.edu!usenet From: tbuswell@bio.bu.edu (Theodore Buswell) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: DHCP & 2.1.5-RELEASE Date: 09 Mar 1997 14:26:32 -0500 Organization: Boston University Lines: 13 Sender: tbuswell@bio.bu.edu Message-ID: <lhcafocooif.fsf@bio.bu.edu> References: <lhcwwrj26gp.fsf@bio.bu.edu> <5fpgqk$s4f@ui-gate.utell.co.uk> <5fqloe$5sm@bali.seg.wj.com> NNTP-Posting-Host: bio.bu.edu In-reply-to: alan@bali.seg.wj.com's message of 7 Mar 1997 19:17:34 -0800 X-Newsreader: Gnus v5.0.15 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36807 All these posts saying how both clients worked great led me to the conclusion that I was screwing it up somehow. I didn't try very hard with the ISC client, since my server is RFC compliant and as I understand it, unpatched ISC client works to the draft specification. But I did get the WIDE client straight out of 2.1.5 ports working correctly. Turns out, it only misbehaves the way I described earlier when you already have the interface 'ifconfig'-ed. Deleting my device configuration lines from sysconfig and starting dhcpc out of rc.local seems to have it working fine. Thanks, -Ted