Linux and Cox Cable Modem (@home)

Linux and Cox Cable Modem (@home)

Post by Charles Onsto » Tue, 15 Jul 1997 04:00:00



Has anyone been able to get Linux working with the Cox Cable Modem

I've tried the following:

1.) dhcpcd (errors out saying no DHCP server) although this works fine in
Windows NT/95.
2.) Manually config ifconfig and routes.  When I do this, I can't see
anything.

There's nothing wrong with the network card I'm using since I had (just
previously) been using it as a LAN connection.

I'm at a loss as to why this isn't working.  Anyone have any ideas?

Thanks,
Charles

 
 
 

Linux and Cox Cable Modem (@home)

Post by Charles Onsto » Tue, 15 Jul 1997 04:00:00



says...

> Has anyone been able to get Linux working with the Cox Cable Modem

> I've tried the following:

> 1.) dhcpcd (errors out saying no DHCP server) although this works fine in
> Windows NT/95.
> 2.) Manually config ifconfig and routes.  When I do this, I can't see
> anything.

> There's nothing wrong with the network card I'm using since I had (just
> previously) been using it as a LAN connection.

> I'm at a loss as to why this isn't working.  Anyone have any ideas?

Let me give more details.  This message amounts to "I configured it and
it doesn't work."

My linux machine is dual-homed.  It has two SMC Ultra Elite cards:  eth0
and eth1.

eth0 is used for LAN and eth1 will (hopefully) be used for WAN via cable
modem.

Please note that I have been able to get the cable modem service to work
properly using Windows NT Workstation.  There are no problems with DHCP
server or the modem itself.  Also note that eth1 has worked when
configured for a LAN IP.  I have been able to connect to the machine
through eth1.  I can therefore rule out hardware issues associated with
the modem and the card.  I can also rule out problems on the remote end
with DHCP.

I have tried two approaches:

1.) dhcp using "dhcpcd eth1"

allocate them.  DHCP, they said, is used to ease administration on their
end.  It is probably also in place to allow further growth of their
network.

So, lets say my IP address is: 204.115.177.40.  My netmask would be
255.255.255.0 and my gateway should be 204.115.177.1.

Now I'm not sure how they assign the IP address using DHCP if it is
fixed.  So I have to assume that it goes by the hostname.  I assume that
DHCP has some facility for transferring the hostname to the DHCP server
so that the DHCP server knows which address to return.

I will note that I was not able to get DHCP working properly on Windows
machines until Microsoft Networking was installed, WINS server addresses
were correctly configured, and the Microsoft Network Node name was set to
the DNS name.  Perhaps the method they use for assign DHCP goes through
Microsoft Networking.  I am rather ignorant of how DHCP gets the job
done, so any clarification would be greatly appreciated.

When running "dhcpcd eth1" with my hostname correctly set, ifconfig
reveals the IP address is 0.0.0.0 and it remains there until dhcpcd times
out.  I get an error in /var/adm/syslog saying that it was not able to
receive a DHCP command (the name which I forget) which appears to be
related to replying to the DHCP request.

Accordingly, I gave up with DHCP since there doesn't appear to be a lot
you can do with it on the client side.

2.) I decided to configure eth1 directly using the assigned network
information:

hostname# ifconfig eth1 204.115.177.40 -nopointopoint
hostname# ifconfig
doing this will report back that the interface is configured for that
address with the correct subnet (255.255.255.0) and an acceptable
broadcast address.  However, it appears to have a ton of options on which
I did not specify, things like "MASTER" and "SLAVE" and "PROMISC"
I'm not sure why these items are being turned on.  Anyone who can fill me
in on those details would be greatly appreciated.  Also note that I must
specifically disable pointtopoint or else the interface trys to set
itself up as a point-to-point interface.  Perhaps someone can enlighten
me on this as well.

hostname#route add -net 204.115.177.0 eth1
hostname#route add default gateway 204.115.177.1
hostname#route
doing this will report back the correct routing table configuration.

This should be all there is to it, unless I'm missing something glaring.
At this point pings to 204.115.177.40 (my IP) will respond.  However,
pings to ANY other address including the router never respond.

I would appreciate any insight into what may be my problem with either
the dhcpcd or the manual configuration.  If you have been able to get

Thanks again!

Also note that I have tried configuring all of this on eth0 (substituting
the interface above) to no avail.

I will monitor this newsgroup as well as email for replies.

Thanks,
Charles

 
 
 

Linux and Cox Cable Modem (@home)

Post by David Christens » Wed, 16 Jul 1997 04:00:00




>Has anyone been able to get Linux working with the Cox Cable Modem

>I've tried the following:

>1.) dhcpcd (errors out saying no DHCP server) although this works fine in
>Windows NT/95.
>2.) Manually config ifconfig and routes.  When I do this, I can't see
>anything.

I was able to get Linux to work with the cable modem on the first try.
In my situation, I was given a dedicated IP address, so when I
configured Linux, I simply used the name and address Cox gave me.  I
am using Red Hat 4.1, so I don't run ifconfig manually.  Here is a
printout from route and ifconfig if it helps:


lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:7960 errors:0 dropped:0 overruns:0
          TX packets:7960 errors:0 dropped:0 overruns:0

eth0      Link encap:10Mbps Ethernet  HWaddr 00:AA:00:13:A5:A0
          inet addr:24.1.139.35  Bcast:24.1.139.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6099332 errors:0 dropped:0 overruns:0
          TX packets:5042462 errors:0 dropped:12 overruns:0
          Interrupt:5 Base address:0x320

eth1      Link encap:10Mbps Ethernet  HWaddr 00:A0:C9:48:DE:35
          inet addr:192.168.0.1  Bcast:192.168.0.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11069662 errors:0 dropped:0 overruns:0
          TX packets:7352279 errors:0 dropped:0 overruns:0
          Interrupt:15 Base address:0xff80


Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref
Use Iface
24.1.139.0      *               255.255.255.0   U     0      0
953 eth0
192.168.0.0     *               255.255.255.0   U     0      0
725 eth1
127.0.0.0       *               255.0.0.0       U     0      0
4 lo
default         cr3-hfc1.msnv1. 0.0.0.0         UG    0      0
43362 eth0    

I've set up my system for IPMasq to allow other systems in the house
access to the internet.  If you have any specific questions about my
config, let me know.

David Christensen

 
 
 

Linux and Cox Cable Modem (@home)

Post by Charles Onsto » Thu, 17 Jul 1997 04:00:00


Thanks to everyone who replied.  Apparently I needed to reset my cable
modem when moving the 10BaseT jack from one network card to another.  I
have not been able to get DHCP working, but then again, I haven't tried
it again.  I was able to get it working by supplying a fixed IP address,

subscribers running Linux.

Thanks again!

Charles

 
 
 

Linux and Cox Cable Modem (@home)

Post by Vladimir Vuks » Sun, 20 Jul 1997 04:00:00



>>Has anyone been able to get Linux working with the Cox Cable Modem

>>I've tried the following:

>>1.) dhcpcd (errors out saying no DHCP server) although this works fine in
>>Windows NT/95.
>>2.) Manually config ifconfig and routes.  When I do this, I can't see
>>anything.

Run the netconfig script (if you use Slackware). Prior to that of course
make sure you get in Windows all the appropriate numbers such as
IP number, Gateway number (very important, that might be the reason
why you don't see anybody) and Netmask.

Vladimir