[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: DHCP on @home



On Thu, Jun 01, 2000 at 12:42:54PM -0700, Jordan Melville wrote:
> Hi all,
> 
> I've finally got the NIC working, and I was about to get it going when 
> suddenly my @home connection went dead. 36 hours later it came back up, and 
> now my @home connection requires DHCP for configuration. (before it used 
> static IPs, and I had two of them). I went into linuxconf and set eth0 to 
> use DHCP for configuration. No problem I think...
> 
> I can't seem to get it to work. It gets to eth0, stops for a minute or so, 
> then says it can't configure itself. Both my Win2k and Win98 machines work 
> perfectly with DHCP, but their IP addresses are the same (go figure). I 
> think it may have something to do with the computer name (CR-909xxx) or the 
> domain they gave me (@home) to use to identify myself to the DHCP server. 
> Where would I put this info into the config?
> 
> Alternatively, is there some way I can set this computer to a private IP 
> and have it use my Win2K box as a proxy or router? I really only want to do 
> some very minor surfing. I also will need to be able to sniff packets 
> coming into my other machines for security and educational reasons.

I am not sure how to confiure it. @home still uses static ip addresses here even though they encourage you to use DHCP. For now, you can type as root "dhcpcd -h <FQDN>" That should at least get you connected, until you can change the scripts.

Victor

-- 
"If you're sick and tired of the politics of cynicism and polls and
principles, come and join this campaign."

		--George W. Bush 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]