mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
gferg
parent
f3f32d8b07
commit
a18a93f3f5
|
|
@ -16,11 +16,11 @@
|
|||
|
||||
<revhistory>
|
||||
<revision>
|
||||
<revnumber>v4.23</revnumber>
|
||||
<date>July 10, 2000</date>
|
||||
<revnumber>v4.24</revnumber>
|
||||
<date>August 23, 2000</date>
|
||||
<authorinitials>vv</authorinitials>
|
||||
<revremark>
|
||||
Addition of Liwest
|
||||
A lot of additions and updates
|
||||
</revremark>
|
||||
</revision>
|
||||
</revhistory>
|
||||
|
|
@ -199,6 +199,25 @@ other necessary configuration. DHCP mini-HOWTO can be found at
|
|||
url="http://www.oswg.org/oswg-nightly/DHCP.html">http://www.oswg.org/oswg-nightly/DHCP.html</ulink>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Most of Mediaone/RoadRunner tracks you're MAC (ethernet) address,
|
||||
and won't allow any other MAC address to use the CableModem.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
To get around this you could either call Mediaone and ask them to change
|
||||
you're MAC address to you're current one. They do allow you to have
|
||||
multiple allowed MAC addresses, but they might not allow more than two.
|
||||
Other approach is to tell your ethernet card what MAC address to use. Most
|
||||
cards will allow it. So first make sure you write down the MAC address of the
|
||||
card you used when Mediaone technicians showed up and they type something like
|
||||
this:
|
||||
</para>
|
||||
|
||||
<programlisting>
|
||||
ifconfig eth0 hw ether 00:23:56:74:25:12
|
||||
</programlisting>
|
||||
|
||||
<para>
|
||||
Information about MediaOne Service can be found at
|
||||
<ulink url="http://www.mediaone.com">http://www.mediaone.com</ulink>.
|
||||
|
|
@ -1637,7 +1656,7 @@ More information can be obtained from
|
|||
|
||||
<!-- S e c t i o n - - - - - - - - - - - - - - - B r e a k e r -->
|
||||
<sect2>
|
||||
<title>TVD, Belgium</title>
|
||||
<title>Chello Belgium, formerly TVD, Belgium</title>
|
||||
<para>
|
||||
This information is provided by Pierre-Yves Keldermans
|
||||
<email>pykeldermans@usa.net</email>:
|
||||
|
|
@ -1672,7 +1691,7 @@ FROM internet, small speed TO internet.
|
|||
</para></listitem>
|
||||
|
||||
<listitem><para>
|
||||
No so cheap : for small office use, same as 1) but not limited to 1
|
||||
Not so cheap : for small office use, same as 1) but not limited to 1
|
||||
user and more speed TO internet.
|
||||
</para></listitem>
|
||||
|
||||
|
|
@ -1688,7 +1707,7 @@ bandwidth TO internet following price.
|
|||
Speed :
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
From TVD's mirror site : up to 250Kbytes/sec, very nice ( and YES, they
|
||||
From TVD's mirror site : up to 30Kbytes/sec, very nice ( and YES, they
|
||||
have some Linux mirrors like redhat ... :-) )
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
|
|
@ -1699,10 +1718,33 @@ overloaded.
|
|||
</para></listitem>
|
||||
|
||||
<listitem><para>
|
||||
For more info : <ulink url="http://www.tvd.be">http://www.tvd.be</ulink> and
|
||||
<ulink url="http://www.tvd.net">http://www.tvd.net</ulink>.
|
||||
For more info : <ulink url="http://www.chello.be">http://www.chello.be</ulink> and
|
||||
<ulink url="http://www.upcbelgium.be/">http://www.upcbelgium.be/</ulink>.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>
|
||||
Note from another user:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
TVD gives you an IP via DHCP and when it is activated they log the
|
||||
MAC-Address. So if you want to connect to the internet via another
|
||||
computer with another ethernetcard it won't work. You have to change your
|
||||
MAC-Address to the 1 that can connect.
|
||||
I just put somewhere in a startupscript :
|
||||
</para>
|
||||
|
||||
<programlisting>
|
||||
ifconfig eth0 hw ether 00:23:56:74:25:12
|
||||
</programlisting>
|
||||
|
||||
<para>
|
||||
This was not all, TVD gives some problems with pump in RedHat 6.2 but with
|
||||
DHCPcd 1.3 it works like a charm. (that dhcpcd is on the install cd in
|
||||
Redhat/rpms)
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
|
||||
|
|
@ -2630,6 +2672,28 @@ SwissOnLine do not support Linux directly, but they are aware of its
|
|||
existance!
|
||||
</para>
|
||||
|
||||
<para>Notes from Thomas Holenstein <email>thomas@hex.ch</email>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
I had problems installing my cable modem as well under Linux and under
|
||||
Win98, because the DHCP server of swiss online did not to respond.
|
||||
If you encounter similar problems, you may want call the hotline (0848
|
||||
852 800). Hold the MAC number of your modem ready if you call, you
|
||||
can find it at the bottom of the modem. If you are only using linux,
|
||||
it might prove difficult to convince the hotline people you did things
|
||||
right. It was difficult with windows already. Be sure you get a
|
||||
number for your problem (Bearbeitungsnummer).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If you want to analyze the problems you may install a network sniffer:
|
||||
<ulink url="http://ethereal.zing.org/">ethereal</ulink> is available for
|
||||
linux and for windows. In my case, I saw that I was sending bootp
|
||||
packages to swissonline but did not receive bootp packages from them.
|
||||
However, I could get other packets.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<!-- S e c t i o n - - - - - - - - - - - - - - - B r e a k e r -->
|
||||
|
|
@ -2679,6 +2743,47 @@ Please contact Bernd if you have additional questions. He has kindly
|
|||
agreed to provide assistance to any current or new Linux user.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<!-- S e c t i o n - - - - - - - - - - - - - - - B r e a k e r -->
|
||||
<sect2>
|
||||
<title>Blueyonder from Telewest, United Kingdom</title>
|
||||
<para>
|
||||
Information provide by Mike Watson <email>mike@prog99.com</email>:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Plugged in the ethernet card, booted up and turned on
|
||||
<ulink
|
||||
url="http://www.oswg.org/oswg-nightly/DHCP.html">DHCP</ulink>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Worked first time!! Nameservers were added to resolve.conf so I had to
|
||||
do very little other than follow the home networking howto to get the
|
||||
IP masquerading working.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
They also dont mind people running masq'd connections or linux but
|
||||
will only support a win9x setup. But when it was this easy....
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<!-- S e c t i o n - - - - - - - - - - - - - - - B r e a k e r -->
|
||||
<sect2>
|
||||
<title>CableNet, Colombia</title>
|
||||
<para>
|
||||
Information provide by Marco Muskus <email>muskus@superpuertos.homeip.net</email>:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
CableNet uses CyberSurf from Motorola, and a 3Com 905 10Base-T
|
||||
Ethernet NIC. Set up is mostly done using
|
||||
<ulink url="http://www.oswg.org/oswg-nightly/DHCP.html">DHCP</ulink>
|
||||
but some people also receive static IPs.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
|
@ -3391,6 +3496,63 @@ url="http://www.oswg.org/oswg-nightly/DHCP.html">http://www.oswg.org/oswg-nightl
|
|||
|
||||
</sect2>
|
||||
|
||||
<!-- S e c t i o n - - - - - - - - - - - - - - - B r e a k e r -->
|
||||
<sect2>
|
||||
<title>Rock Hill Telephone (RHTC) and Fort Mill Telephone (FMTC), South Carolina</title>
|
||||
|
||||
<para>
|
||||
This information is provided by Ryan T Rhea <email>rhear@ruby.winthrop.edu</email>:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Rock Hill Telephone (RHTC) and Fort Mill Telephone (FMTC) offer hybid
|
||||
cable modem access through a partnership with the Info Avenue ISP. The
|
||||
cable modem is built by Hybrid, and offers high bandwidth downstream
|
||||
over the cable line (I've seen 900+ kpbs), and upstream over the builtin
|
||||
modem (around 33.6 kbps). The cable modem connects to an ethernet
|
||||
10baseT card and a regular phone line. The cable modem acts as a router
|
||||
from your machine to the internet.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
RHTC and FMTC 's tech support is performed by Info Avenue, and they
|
||||
offer no support for Linux whatsover. They were unable to provide any
|
||||
help or documentation regarding Linux and cable modems. Luckily, I was
|
||||
aware through my initial Win NT setup (as I looked over the tech's
|
||||
shoulder) that DHCP
|
||||
was used to assign IP addresses and
|
||||
DNS information. What I had to learn the hard way was that the cable
|
||||
modem apparently relies on the MAC address of the NIC that it is
|
||||
originally installed on. In otherwords, when I went to move the cable
|
||||
modem from my NT machine (which was using a proxy server and a second
|
||||
NIC to share internet access) to my new Linux firewall, I had to move
|
||||
the NIC into the new Linux computer. Without the same NIC, the network
|
||||
link light on the back of the cable modem will never come on, and the
|
||||
modem will not communicate with your computer at all. I assume if you
|
||||
bought a new computer with a new NIC, you could call RHTC or FMTC and
|
||||
ask them to update your MAC, however, they would probably not know what
|
||||
you were talking about, and want to send a technician. When the
|
||||
technician gets there, expect "we do not support Linux" to be the first
|
||||
words out of his mouth.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Anyway, after installing the original NIC (which probably won't be a
|
||||
problem for most of you, because you only have 1 NIC in your computer -
|
||||
which the tech setup under Windows), all I had to do was configure
|
||||
DHCP. Considering my NIC was already working under Linux, my Mandrake
|
||||
Linux distribution made this especially easy. I just type 'netconf',
|
||||
then choose 'Basic Host Information', then enable DHCP for the NIC in
|
||||
question (in my case 'Adapter 1'). The program should restart the
|
||||
device for you, if not, you may need to reboot, or manually restart the
|
||||
device with ifconfig.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If you have trouble with DHCP you could check out
|
||||
<ulink url="http://www.oswg.org/oswg-nightly/DHCP.html">DHCP mini-HOWTO</ulink>.
|
||||
</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
</article>
|
||||
|
|
|
|||
Loading…
Reference in New Issue