[nSLUG] Eastlink cable modem access
me at jonwatson.ca
Thu Jan 31 13:39:49 AST 2008
On Jan 31, 2008 1:27 PM, Gerald <linux at zdoit.airpost.net> wrote:
> I'm sorry it was not clear before the problem is the IP address of the
> DHCP server that is issuing my address, not with the address I receive.
> The IP address I am getting is a valid Eastlink address. The IP address
> issued is the same from both DHCP servers. No problems with getting
> anywhere on the Internet.
> I looked at my logs where I sometimes see:
> Jan 28 16:22:21 x dhclient: DHCPREQUEST on eth0 to 24.x.x.x port 67
> Jan 28 16:22:25 x dhclient: DHCPREQUEST on eth0 to 24.x.x.x port 67
> Jan 28 16:22:25 x dhclient: DHCPACK from 24.x.x.x
> Jan 28 16:22:25 x dhclient: bound to 24.y.y.y -- renewal in 68428 seconds.
> And sometimes something similar to:
> Jan 30 17:24:52 x dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
> Jan 30 17:24:57 x dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
> Jan 30 17:24:57 x dhclient: DHCPACK from 10.6.z.z
> Jan 30 17:24:57 x NET: /sbin/dhclient-script : updated /etc/resolv.conf
> Jan 30 17:24:57 x dhclient: bound to 24.y.y.y -- renewal in 78329 seconds.
Interesting. Granted, I don't spend a lot of time watching DHCP logs, but I
would think that the second example is more indicative of a 'normal' DHCP
request as it is a broadcast request on port 67. This is designed to hit any
DHCP server on the network in the hopes that it will give out an address.
Given that a computer without an IP address cannot communication on a TCP/IP
network. I can't see how a DHCP request to a specific address (like in your
first snippet) would succeed. Perhaps it's a refresh request in that the
interface already has an IP assigned to it and can therefore query a
specific DHCP server.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nSLUG