Joel Hammer wrote:
>
> Still trying to get connected with dhcpcd -d eth1 to the new or old
> @HOME service. My cable modem is on eth1.
>
> This command, dhcpcd -d eth0, talking to my intranet dhcpd linux server,
> gets assigned an IP address without trouble.
>
> Here is what I see with tcpdump -i eth1 -n | grep .67.
>
> 0.0.0.0.68 > 255.255.255.255.67: xid:0xf34afb2f secs:5 [|bootp]
<SNIP>
> 0.0.0.0.68 > 255.255.255.255.67: xid:0xf34afb2f secs:5 [|bootp]
>
> So, it looks like the dhcpd server sees my request, and responds, but
> the negotiations break down.
>
> Adding the -DH options didn't fix the problem.
>
> Any insight appreciated.
On my install of eS2.31 and IIRC on all my Caldera installs, dhcpcd is
called from a script found in /etc/sysconfig/setwork-sccripts called
'ifup-dhcp'.
To make my dhcpcd work on @home I had to change the call to dhcpcd as
shown below by changing the -HD to instead tell the server the @home ID
was given 'cr######-a', and they would assign the IP according to
hostname supplied.
>>> #/sbin/dhcpcd -HD $interface >/dev/null || {
>>> /sbin/dhcpcd -h cr######-a $interface >/dev/null || {
You might want to try two things, using this script to call dhcpcd
(which is what should happen if you set it up using COAS, and the option
to supply your @home hostname, which Comcast may still be expecting. If
their windows install instructions include adding a specific 'computer
name' under Network Neighborhood -> Properties -> Ident. , this could
well be the case.
--
Linux SxS [http://sxs.webhop.net]
_______________________________________________
Linux-users mailing list
Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
