From 275614495d3f7e339ec12ffba455f58b04ecf0e8 Mon Sep 17 00:00:00 2001 From: gferg <> Date: Thu, 18 May 2000 12:31:05 +0000 Subject: [PATCH] updated --- LDP/howto/docbook/Cable-Modem.sgml | 145 +++++++++++++++++++++++++++-- 1 file changed, 139 insertions(+), 6 deletions(-) diff --git a/LDP/howto/docbook/Cable-Modem.sgml b/LDP/howto/docbook/Cable-Modem.sgml index 0ba27de7..135a16e4 100644 --- a/LDP/howto/docbook/Cable-Modem.sgml +++ b/LDP/howto/docbook/Cable-Modem.sgml @@ -16,11 +16,11 @@ - v4.15 - April 24, 2000 + v4.17 + May 16, 2000 vv - Many changes + Additions to @home and new provider in Bombay, India @@ -380,6 +380,28 @@ mini-HOWTO for cable modems and Cox@Home at http://www.kernel-panic.com/user_files/cox.at.home.html + + +Update from James Stormes jstormes@gtfcu.com + + + +@Home has been upgrading the cable modem system in Bedford Texas (the area +around Dallas Texas). I have found that with the new system your NIC's MAC +address must match what the cable system has. That is the Linux system you +plug into the cable modem must use the same MAC that is programmed into the +board you got from @Home. I use two diffrent computers on the cable modem +(Linux and Windows) so this was a problem. + + + +For some NIC drivers you can specify the MAC. For example in +n REDHAT 6.1 in the /etc/sysconfig/network-scripts/ifcfg-eth0 you can add +the line MACADDR="0F4F3E54A659". Where eth0 is the NIC card attached to the +cable modem and the 0F4F3E54A659 is the MAC that the cable modem system is +expecting. + + @@ -418,10 +440,36 @@ dynamic to everyone else. Don't ask me why. + +Notes from Richmond, VA and its surroundings by Robert Marshall <email>no_robmars_spam@yahoo.com</email> + + +In Chesterfield County, Virginia (a suburb of Richmond), @Home offers cable +modem service through the local cable provider, Comcast. The service runs very +well with Linux. As with many @Home locations, IP addresses are assigned via +dhcp, and they require that all dhcp request packets contain the user's +@Home-assigned hostname. The dhcpcd package works well for this, using the -h +parameter. Personal best download - 16Mbytes in 54 seconds. + + + +In Henrico County, Hanover County, and the city of Richmond, Virginia, MediaOne +is offerring their Road Runner service. IP addresses are assigned using dhcp, +but are exclusively reserved by MAC address. This requires that the user call +MediaOne support if the MAC address attached to the cable modem ever changes. +The MediaOne people refused to re-register my friend's new MAC address when he +told them that he had purchased a personal firewall from NetGear. They even +tried to insist that he purchase commercial service, even though he was only +going to have one PC connected to the service. Thus, I strongly agree with your +wording in the HOWTO that MediaOne customers carefully avoid mentioning the +words "router", "firewall", or "Linux". + + + + Information about @Home Service can be found at -http://www.home.com/ -. +http://www.home.com/. @@ -2065,8 +2113,93 @@ mailing me direct (but I don't promise to be able to respond). + + +Virtua, São Paulo, Brazil + + +This information is provided by Thiago Macieira thiagom@mail.com: + + + +IP is assigned dynamically via DHCP. Just run dhcpcd or pump to get +the IP and you're done. For more detailed instructions on how to get DHCP running +read the +DHCP mini-HOWTO. + + + +Notes: operator blocks incoming connections to ports below 1024 + + + + + +Hathway, Bombay, India + + +This information is provided by Rishi Gangoly rishi@w-o-i.com: + + + +The tech support guys at Hathway were not Linux Savvy at all, but I must say +were quite helpful. They even referred me to another customer who got Linux to +work with it. However, that person was only able to get it to work on Linux as a +stand-alone workstation and not as a gateway (as a router) for his entire +network. + + + +Since I was not even able to get it to work as a stand-alone workstation I knew +I had a long way to go. The Windows 98 Workstation configuration was a Celeron +Workstation and it had a +10/100 D-Link Lan Card Chipset RTL 8139 . The IP address was manually entered, +so I knew that there was no DHCP Client required etc. + + + +Even the DNS and Gateway address was manually entered. + + + +I was able to do a ping without any problem in Windows to any site and things +were just happening. However, I had no luck with it in Linux. I installed Linux +on the same machine (Dual Boot) to make sure there was any Hardware +compatibility problems. + + + +I even got the workstation to hook up on the LAN successfully in Linux. So I +knew that the Lan Card was working. + + + +I noticed that when I connected the Cable Modem to the LAN card I was not able +to see any of the Link LED light up on the LAN Card. So I figured that could be +part of the problem. I booted the PC in DOS and ran the DIAG DOS based utility +to check the configuration of the Card. I just decided to take a chance and +re-configured the LAN Card. I configured it to operate in 10 MBPS Half Duplex +Mode instead of Auto Sense. + + + +.......... Guess what..... The problem got solved ;-) + + + +Even the lights (LED Link indicators) started to work, so all was good. ;-) +At the end of everything it all worked out. I plugged that lan card into the +linux server (since I knew it worked) and got it to work as a router / gateway +too. I still wonder why the other customer was not able to get the Linux Box to work +as a gateway for the rest of his network. That was no big deal at all. It just +worked. The Cable Modem that was used (provided by Hathway) was a SurfBoard 3100 + + + - + + + Hybrid Cable modem ISPs