Date: Mon, 3 Jan 2000 02:46:51 -0500 (EST) From: Daniel L Quigley-Skillin <dskillin@totalconnect.net> Cc: Kavi Tanna <candirect@home.com>, freebsd-questions@FreeBSD.ORG Subject: Re: @home cable modem installation using dhcp on freebsd Message-ID: <Pine.LNX.4.10.10001030232530.6806-100000@totalconnect.net> In-Reply-To: <Pine.NEB.3.96.1000102234608.59378A-100000@shell-1.enteract.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 3 Jan 2000, David Scheidt wrote: > > > 3. I AM USING @HOME, THIS HAS A SPECIAL DHCP CONFIGURATION > > Not in my experience, it hasn't. You probably want to increase timeout > values, since the @home DHCP servers suck That they do! @Home actually needs the host name of the machine to issue it an IP address. I tried to get this information a couple of days ago to help out, but you know how things go. :/ From here you have two options. First: Find out your stack info and set the stack static. <--- My favorite option as @Home doesn't switch your IP very often, in fact, my IP has never changed in 3 years. Second: Invoke dhcp using the -h flag. Similar to this. /sbin/dhcpcd -h CRxxxxxx-A -c /etc/sysconfig/network-scripts/ifdhcpc-done eth0 CRxxxxxx-A being your propper host name, given by @Home. Your script locations may vary, but you get the main point of it. You should be able to get your host name and or stack info from the member services page in the @Home content. I'd only use the dhcp option if you really feel you have to. @Home DHCP servers are know to die. 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.LNX.4.10.10001030232530.6806-100000>