mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
gferg
parent
d53abebe28
commit
275614495d
|
|
@ -16,11 +16,11 @@
|
|||
|
||||
<revhistory>
|
||||
<revision>
|
||||
<revnumber>v4.15</revnumber>
|
||||
<date>April 24, 2000</date>
|
||||
<revnumber>v4.17</revnumber>
|
||||
<date>May 16, 2000</date>
|
||||
<authorinitials>vv</authorinitials>
|
||||
<revremark>
|
||||
Many changes
|
||||
Additions to @home and new provider in Bombay, India
|
||||
</revremark>
|
||||
</revision>
|
||||
</revhistory>
|
||||
|
|
@ -380,6 +380,28 @@ mini-HOWTO for cable modems and Cox@Home at
|
|||
<ulink
|
||||
url="http://www.kernel-panic.com/user_files/cox.at.home.html">http://www.kernel-panic.com/user_files/cox.at.home.html</ulink>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Update from James Stormes <email>jstormes@gtfcu.com</email>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@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.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
|
|
@ -418,10 +440,36 @@ dynamic to everyone else. Don't ask me why.
|
|||
</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Notes from Richmond, VA and its surroundings by Robert Marshall <email>no_robmars_spam@yahoo.com</email>
|
||||
</title>
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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".
|
||||
</para>
|
||||
|
||||
</sect3>
|
||||
|
||||
<para>
|
||||
Information about @Home Service can be found at
|
||||
<ulink url="http://www.home.com/">http://www.home.com/</ulink>
|
||||
.
|
||||
<ulink url="http://www.home.com/">http://www.home.com/</ulink>.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
|
@ -2065,8 +2113,93 @@ mailing me direct (but I don't promise to be able to respond).
|
|||
</sect2>
|
||||
|
||||
|
||||
<!-- S e c t i o n - - - - - - - - - - - - - - - B r e a k e r -->
|
||||
<sect2>
|
||||
<title>Virtua, São Paulo, Brazil</title>
|
||||
|
||||
<para>
|
||||
This information is provided by Thiago Macieira <email>thiagom@mail.com</email>:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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
|
||||
<ulink url="http://www.oswg.org/oswg-nightly/DHCP.html">DHCP mini-HOWTO</ulink>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Notes: operator blocks incoming connections to ports below 1024
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<!-- S e c t i o n - - - - - - - - - - - - - - - B r e a k e r -->
|
||||
<sect2>
|
||||
<title>Hathway, Bombay, India</title>
|
||||
|
||||
<para>
|
||||
This information is provided by Rishi Gangoly <email>rishi@w-o-i.com</email>:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Even the DNS and Gateway address was manually entered.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
I even got the workstation to hook up on the LAN successfully in Linux. So I
|
||||
knew that the Lan Card was working.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
.......... Guess what..... The problem got solved ;-)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
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
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
<!-- S e c t i o n - - - - - - - - - - - - - - - B r e a k e r -->
|
||||
|
||||
|
||||
<!-- S e c t i o n - - - - - - - - - - - - - - - B r e a k e r -->
|
||||
<sect1 id="hybrid">
|
||||
<title>Hybrid Cable modem ISPs</title>
|
||||
<para>
|
||||
|
|
|
|||
Loading…
Reference in New Issue