Help please! I need dhcp.conf file for Comcast...

I'm trying to get my Comcast cable modem to work. Supposedly, all
I need to do is to run dhcpd -d eth1, but I get errors (something
about undefined subnets). I gather that the problem is with my
/etc/dhcp.conf file (I'm using the default that was installed with
the dhcp package). In case it matters, my distro is Debian.

Thanks!

-Jill

Sorry, I meant to write dhcpd.conf.

-Jill

In <bkv1li$g4c$(E-Mail Removed)> J Krugman <(E-Mail Removed)> writes:



>I'm trying to get my Comcast cable modem to work. Supposedly, all
>I need to do is to run dhcpd -d eth1, but I get errors (something
>about undefined subnets). I gather that the problem is with my
>/etc/dhcp.conf file (I'm using the default that was installed with
>the dhcp package). In case it matters, my distro is Debian.

>Thanks!

> -Jill

In article <bkv1li$g4c$(E-Mail Removed)>, J Krugman wrote:
> I'm trying to get my Comcast cable modem to work. Supposedly, all
> I need to do is to run dhcpd -d eth1, but I get errors (something

You must have Googled to find that solution. And it is soOOOooo close!
Unfortunately we do grade on spelling errors, and in your case you are
missing just one little letter.

> about undefined subnets). I gather that the problem is with my
> /etc/dhcp.conf file (I'm using the default that was installed with

Yes, it would be very simple for me to tell you the correct command, but
I'd like to help you develop your own troubleshooting skills. The old
"teach to fish" v. "throw a fish" thing, you see.

See "man dhcpd" and read the description. Is this what you want to do?
No. But look at the end under "SEE ALSO". And then try "man -k dhcp",
wherein you will see the correct command listed.

Run that command and you will be a happy Comcastaway.

> the dhcp package). In case it matters, my distro is Debian.

Each distro will have its own way of configuring an interface, so yes,
you should consult the Debian documentation to see how to make this
interface come up every time you boot.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

In <(E-Mail Removed)> /dev/rob0 <(E-Mail Removed)> writes:

>In article <bkv1li$g4c$(E-Mail Removed)>, J Krugman wrote:
>> I'm trying to get my Comcast cable modem to work. Supposedly, all
>> I need to do is to run dhcpd -d eth1, but I get errors (something

>You must have Googled to find that solution. And it is soOOOooo close!
>Unfortunately we do grade on spelling errors, and in your case you are
>missing just one little letter.

OK, I fixed the typo, but still 'dhcpcd -d eth1' doesn't work.
The logfile says:

Sep 26 21:16:09 luna dhcpcd [1282]: dhcpStart: ioctl SIOCGIFHWADDR: No such device

>Yes, it would be very simple for me to tell you the correct command, but
>I'd like to help you develop your own troubleshooting skills. The old
>"teach to fish" v. "throw a fish" thing, you see.

I appreciate the sentiment, but in this case the guy is starving
to death: no time to teach fishin'... Just think about it for a
minute: the machine in question has no internet access. I have to
travel far from home (where this machine is, and has to be if it's
going to use a cablemodem) to where I can access the web.
Troubleshooting that involves using Google, etc., is out of the
question... If you want to help me, I am *most* grateful, but
please don't play with me. This problem is costing me money and
a lot of aggravation...

-Jill

In article <bl9r8h$r22$(E-Mail Removed)>, J Krugman wrote:
> OK, I fixed the typo, but still 'dhcpcd -d eth1' doesn't work.
> The logfile says:
>
> Sep 26 21:16:09 luna dhcpcd [1282]: dhcpStart: ioctl SIOCGIFHWADDR: No such device

You have a different problem: no driver loaded.

/sbin/ifconfig -a # is eth1 listed?
/sbin/ifconfig eth1 # pointless if there is no eth1
/sbin/lsmod
/sbin/lspci -v # look for the eth1 device. Is it PCI?

If you don't know what module to load for your eth1 NIC, Google, or
someone here, might. "modprobe $DRIVER" and try again with dhcpcd.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

J Krugman wrote:
> In <(E-Mail Removed)> /dev/rob0 <(E-Mail Removed)> writes:
>
>
>>In article <bkv1li$g4c$(E-Mail Removed)>, J Krugman wrote:
>>
>>>I'm trying to get my Comcast cable modem to work. Supposedly, all
>>>I need to do is to run dhcpd -d eth1, but I get errors (something
>
>
>>You must have Googled to find that solution. And it is soOOOooo close!
>>Unfortunately we do grade on spelling errors, and in your case you are
>>missing just one little letter.
>
>
> OK, I fixed the typo, but still 'dhcpcd -d eth1' doesn't work.
> The logfile says:
>
> Sep 26 21:16:09 luna dhcpcd [1282]: dhcpStart: ioctl SIOCGIFHWADDR: No such device
>
>
-------- SNIP Fish Story ------------
Do you actually have more than one ethernet interface? If not, then the
only one you have is actually eth0.

I know I've already used up more than my share of the NG's patience
and goodwill... I hope this is the last time I come begging for
more...

In <(E-Mail Removed)> "@(none)" <""root\"@(none)"> writes:

>J Krugman wrote:

>> OK, I fixed the typo, but still 'dhcpcd -d eth1' doesn't work.
>> The logfile says:
>>
>> Sep 26 21:16:09 luna dhcpcd [1282]: dhcpStart: ioctl SIOCGIFHWADDR: No such d
evice

>Do you actually have more than one ethernet interface? If not, then the
>only one you have is actually eth0.

Thanks, things began to move when I used eth0 instead of eth1:

$ sudo dhcpcd -d eth0
dhcpcd: MAC address = 00:03:f7:ca:cc:b2
dhcpcd: your IP address = 66.46.30.27

....but the logfile suggests that not all is well:

Oct 1 08:13:24 luna dhcpcd[820]: broadcasting DHCP_REQUEST for 66.46.30.27
Oct 1 08:13:24 luna dhcpcd[820]: dhcpIPaddrLeaseTime=345600 in DHCP server response.
Oct 1 08:13:24 luna dhcpcd[820]: dhcpT1value is missing in DHCP server response. Assuming 172800 sec
Oct 1 08:13:24 luna dhcpcd[820]: dhcpT2value is missing in DHCP server response. Assuming 302400 sec
Oct 1 08:13:24 luna dhcpcd[820]: DHCP_ACK received from (24.34.240.34)


Indeed, ping fails everywhere I try:

$ ping -c 1 166.84.1.72
PING 166.84.1.72 (166.84.1.72): 56 data bytes

--- 166.84.1.72 ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss

All the physical connections look good. Below are the outputs of
ifconfig -a and route -n.

$ sudo ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:02:3F:7C:AC:CB
inet addr:66.46.30.27 Bcast:255.255.255.255 Mask:255.255.248.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4117 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:247358 (241.5 KiB) TX bytes:1084 (1.0 KiB)
Interrupt:11 Base address:0xd000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:604 (604.0 b) TX bytes:604 (604.0 b)

$ sudo route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
66.30.24.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
0.0.0.0 66.30.24.1 0.0.0.0 UG 0 0 0 eth0


If anyone can spot the problem here I'd be very grateful.

TIA,

-Jill

J Krugman wrote:
> I know I've already used up more than my share of the NG's patience
> and goodwill... I hope this is the last time I come begging for
> more...
>
> In <(E-Mail Removed)> "@(none)" <""root\"@(none)"> writes:
>
>
>>J Krugman wrote:
>
>
>>>OK, I fixed the typo, but still 'dhcpcd -d eth1' doesn't work.
>>>The logfile says:
>>>
>>>Sep 26 21:16:09 luna dhcpcd [1282]: dhcpStart: ioctl SIOCGIFHWADDR: No such d
>
> evice
>
>
>>Do you actually have more than one ethernet interface? If not, then the
>>only one you have is actually eth0.
>
>
> Thanks, things began to move when I used eth0 instead of eth1:
>
> $ sudo dhcpcd -d eth0
> dhcpcd: MAC address = 00:03:f7:ca:cc:b2
> dhcpcd: your IP address = 66.46.30.27
>
> ...but the logfile suggests that not all is well:
>
> Oct 1 08:13:24 luna dhcpcd[820]: broadcasting DHCP_REQUEST for 66.46.30.27
> Oct 1 08:13:24 luna dhcpcd[820]: dhcpIPaddrLeaseTime=345600 in DHCP server response.
> Oct 1 08:13:24 luna dhcpcd[820]: dhcpT1value is missing in DHCP server response. Assuming 172800 sec
> Oct 1 08:13:24 luna dhcpcd[820]: dhcpT2value is missing in DHCP server response. Assuming 302400 sec
> Oct 1 08:13:24 luna dhcpcd[820]: DHCP_ACK received from (24.34.240.34)
>
>
> Indeed, ping fails everywhere I try:
>
> $ ping -c 1 166.84.1.72
> PING 166.84.1.72 (166.84.1.72): 56 data bytes
>
> --- 166.84.1.72 ping statistics ---
> 1 packets transmitted, 0 packets received, 100% packet loss
>
> All the physical connections look good. Below are the outputs of
> ifconfig -a and route -n.
>
> $ sudo ifconfig -a
> eth0 Link encap:Ethernet HWaddr 00:02:3F:7C:AC:CB
> inet addr:66.46.30.27 Bcast:255.255.255.255 Mask:255.255.248.0
> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4117 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:247358 (241.5 KiB) TX bytes:1084 (1.0 KiB)
> Interrupt:11 Base address:0xd000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:10 errors:0 dropped:0 overruns:0 frame:0
> TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:604 (604.0 b) TX bytes:604 (604.0 b)
>
> $ sudo route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 66.30.24.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
> 0.0.0.0 66.30.24.1 0.0.0.0 UG 0 0 0 eth0
>
>
> If anyone can spot the problem here I'd be very grateful.
>
> TIA,
>
> -Jill
>
Well, I don't run Debian myself (RH 7.3) I don't think at this point
your issue is that specific so
hang in there awhile longer.
A couple of questions first off.
Are you currently running a firewall/iptables on this system? If so, try
taking it down temporarily until your testing is completed.
Your system is connected directly to your modem?
If you look in your hosts file, are there any entries for your Comcast
DNS servers?
When you tried the ping, did you use a fully qualified domain name or
the IP address?
I've been reading some stuff on various forums about the fact that a lot
of ISP's have "temporarily" disabled the ICMP protocol (ping) in and out
of their networks due to the blaster and nachi worms, so it may just be
that for your ISP that you can't ping for the time being.

Regards

none wrote:
> J Krugman wrote:
>
>> I know I've already used up more than my share of the NG's patience
>> and goodwill... I hope this is the last time I come begging for
>> more...
>>
>> In <(E-Mail Removed)> "@(none)" <""root\"@(none)">
>> writes:
>>
>>
>>> J Krugman wrote:
>>
>>
>>
>>>> OK, I fixed the typo, but still 'dhcpcd -d eth1' doesn't work.
>>>> The logfile says:
>>>>
>>>> Sep 26 21:16:09 luna dhcpcd [1282]: dhcpStart: ioctl SIOCGIFHWADDR:
>>>> No such d
>>
>>
>> evice
>>
>>
>>> Do you actually have more than one ethernet interface? If not, then the
>>> only one you have is actually eth0.
>>
>>
>>
>> Thanks, things began to move when I used eth0 instead of eth1:
>>
>> $ sudo dhcpcd -d eth0
>> dhcpcd: MAC address = 00:03:f7:ca:cc:b2
>> dhcpcd: your IP address = 66.46.30.27
>>
>> ...but the logfile suggests that not all is well:
>>
>> Oct 1 08:13:24 luna dhcpcd[820]: broadcasting DHCP_REQUEST for
>> 66.46.30.27 Oct 1 08:13:24 luna dhcpcd[820]:
>> dhcpIPaddrLeaseTime=345600 in DHCP server response. Oct 1 08:13:24
>> luna dhcpcd[820]: dhcpT1value is missing in DHCP server response.
>> Assuming 172800 sec Oct 1 08:13:24 luna dhcpcd[820]: dhcpT2value is
>> missing in DHCP server response. Assuming 302400 sec Oct 1 08:13:24
>> luna dhcpcd[820]: DHCP_ACK received from (24.34.240.34)
>>
>> Indeed, ping fails everywhere I try:
>>
>> $ ping -c 1 166.84.1.72
>> PING 166.84.1.72 (166.84.1.72): 56 data bytes
>>
>> --- 166.84.1.72 ping statistics ---
>> 1 packets transmitted, 0 packets received, 100% packet loss
>>
>> All the physical connections look good. Below are the outputs of
>> ifconfig -a and route -n.
>>
>> $ sudo ifconfig -a
>> eth0 Link encap:Ethernet HWaddr 00:02:3F:7C:AC:CB
>> inet addr:66.46.30.27 Bcast:255.255.255.255 Mask:255.255.248.0
>> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:4117 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:100 RX bytes:247358
>> (241.5 KiB) TX bytes:1084 (1.0 KiB)
>> Interrupt:11 Base address:0xd000 lo Link
>> encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0
>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>> RX packets:10 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0 RX bytes:604 (604.0
>> b) TX bytes:604 (604.0 b)
>> $ sudo route -n
>> Kernel IP routing table
>> Destination Gateway Genmask Flags Metric Ref
>> Use Iface
>> 66.30.24.0 0.0.0.0 255.255.248.0 U 0
>> 0 0 eth0
>> 0.0.0.0 66.30.24.1 0.0.0.0 UG 0
>> 0 0 eth0
>>
>> If anyone can spot the problem here I'd be very grateful.
>>
>> TIA,
>>
>> -Jill
>>
>
> Well, I don't run Debian myself (RH 7.3) I don't think at this point
> your issue is that specific so
> hang in there awhile longer.
> A couple of questions first off.
> Are you currently running a firewall/iptables on this system? If so, try
> taking it down temporarily until your testing is completed.
> Your system is connected directly to your modem?
My BAD. the info is not in the hosts file. On my system it is in a file
called "dhcpcd-eth0.info"
> If you look in your hosts file, are there any entries for your Comcast
> DNS servers?
Another BAD, you already stated you used the IP address.
> When you tried the ping, did you use a fully qualified domain name or
> the IP address?
> I've been reading some stuff on various forums about the fact that a lot
> of ISP's have "temporarily" disabled the ICMP protocol (ping) in and out
> of their networks due to the blaster and nachi worms, so it may just be
> that for your ISP that you can't ping for the time being.
>
> Regards
>

In article <blf5d3$n1u$(E-Mail Removed)>, J Krugman wrote:
> I know I've already used up more than my share of the NG's patience
> and goodwill... I hope this is the last time I come begging for

I'm fine, how are you? Did you learn something? If so then it's not
wasted effort, is it?

>>Do you actually have more than one ethernet interface? If not, then the
>>only one you have is actually eth0.
>
> Thanks, things began to move when I used eth0 instead of eth1:

And this would explain why there was no driver loaded for eth1.

> ...but the logfile suggests that not all is well:

No, nothing wrong in the log. It says that dhcpT1value and dhcpT2value
are missing from the DHCP server's response. That is not an error, that
is information.

> Indeed, ping fails everywhere I try:

I'm not aware of Comcast blocking ICMP, but perhaps they do it in some
regions. You could call your tech support and ask. The first tier TS
people are adequate at handling physical problems with the cable modem,
and some of the 2nd-tier ones actually know some things.

> $ sudo ifconfig -a

BTW we only need eth0, not -a.

> eth0 Link encap:Ethernet HWaddr 00:02:3F:7C:AC:CB
> inet addr:66.46.30.27 Bcast:255.255.255.255 Mask:255.255.248.0

Very different from the Comcast accounts I'm familiar with, which have a
standard broadcast address (the top IP in the subnet) and are on a /24
or /25 netmask.

> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4117 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7 errors:0 dropped:0 overruns:0 carrier:0

Wow, that's a large disparity in RX and TX, suggesting you can't route
out.

> $ sudo route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 66.30.24.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
> 0.0.0.0 66.30.24.1 0.0.0.0 UG 0 0 0 eth0
>
> If anyone can spot the problem here I'd be very grateful.

I think your route table is FUBAR. For one thing there's no route to the
lo interface. For another, your eth0 subnet is not the subnet of your IP
address. Your network address should be 66.46.24.0, and the typical
broadcast address for that subnet would be 66.46.31.255. Note that your
IP address falls between them.
http://www.cotse.com/networkcalculator.html

Normally a DHCP client will configure the interface, and the kernel will
set up the routing. I have no idea why that would be as it is. Try doing
"dhcpcd -k" and "dhcpcd -d" again?
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply