dhcpCd (was Re: (no subject))

[Spliced Networks]

On Fri, 28 Mar 2003, Beartooth wrote:

You don't need both the eth1 stuff and the iwconfig lines I posted.
Forget about the eth1 stuff for now, and use the iwconfig line and
the ip link and dhcpcd lines I posted.

Before you type dhcpcd, try typing iwconfig and see if you can see
the mac address of your access point. It should also display signal
strength and other information.

If it doesn't then, you should check your SSID, and make sure you have WEP 
turned off on the access point. You may also have to manually set the
channel.

If it still doesn't work, you might want to try changing the channel used 
on your access point. Especially if you have other 2.4GHz equipment, such 
as a cordless phone or wireless doorbell (or close neighbors that might 
have 2.4GHz equipment), as these can sometimes add too much noise to the 
channel being used :) 



> On Fri, 28 Mar 2003, Brian Waite wrote:
> 
> > Make sure you are doing dhcpcd and NOT dhcpd very different beasts
> 
> 	Could be: my aged eyeballs, trifocals and all, had indeed failed 
> to spot that!
> 
> 	Tried again (having meanwhile edited SN's whole nine yards fro 
> 3.0 into eth1). This time I just get a root prompt back. Tried to fire 
> up Phoenix. No connection; connection to 192.168.1.1 refused.
> 
> 	Will reboot 2.3; if no luck, will edit eth1 back and reboot 
> again ...
> 
>