LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

More, but many, minor cleanups. Broke out FAQ to separate page.

This commit is contained in:
hal 2000-09-01 02:06:31 +00:00
parent 2abdb3ba76
commit 69c213a7cb
1 changed files with 172 additions and 131 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

303
LDP/howto/docbook/DSL-HOWTO.sgml
View File

@ -91,6 +91,9 @@ LRP, etc.???
</Comment>
** Draft Comments *************************************************
Thu 08/31/00 08:00:27 PM
Broke off FAQ into separate page. More miscellaneous fine tuning.
Thu 08/31/00 12:12:29 AM
More minor cleanups. Added some DYN DNS links. Spellchecked.
@ -109,28 +112,6 @@ Moved DSL Overview to Appendix.
A few very minor cleanups, and most of GregL's suggestions.
Sun 08/13/00 22:38:26 PM
Mostly done now. Spellchecked and linkchecked. Maybe a few lose
ends to tie up. Maybe minor additions to link and FAQ sections. Security
section is now 'done'.
Tue 08/08/00 08:12:40 PM
Started on troubleshooting section.
Mon 08/07/00 08:55:40 PM
More odds and ends. Security is roughed out. Layout changes. Verified all
links. Will probably remove the ipfwadm stuff at some point.
Sun 08/06/00 02:09:38 PM
More PPPoX stuff. Started on security section.
Sun 08/06/00 01:55:47 AM
More stuff here and there. Some layout changes. More system config.
Fri 08/04/00 06:26:36 PM
Add some FAQs, and started on PPP, and system config stuff.
*** Thu 08/03/00 06:59:50 PM EDT *********************
Note to interested readers:
@ -230,7 +211,7 @@ Wow! We are missing that!
attention to the <Link LinkEnd="usage">Terminology and Conventions</Link>
section, as some of this terminology may be used somewhat differently in
other contexts. Also, there is a <Link LinkEnd="glossary">Glossary</Link> if
you get lost in the world of TA (telco acronyms) &nbsp; ;-).
you get lost in the world of TA (telco acronyms) ;-).
</Para>
@ -244,8 +225,8 @@ Wow! We are missing that!
section. You may want to start with the <Link LinkEnd="overview">DSL
Overview</Link> section in the Appendix, and then the <Link
LinkEnd="faq">FAQ</Link>. The DSL Overview explains how the various pieces
of the puzzle fit together. DSL networks are more complex than traditional
dialup networks.
of the puzzle fit together. DSL network implementations are more complex
than traditional dialup networks.
</Para>
</ListItem>
@ -265,7 +246,7 @@ Wow! We are missing that!
<ListItem>
<Para>
If you have ordered service already, and are awaiting delivery, you can
probably skip the sections on choosing a Provider. If you will be doing a
skip the sections on choosing a Provider. If you will be doing a
self-install, you should read the pertinent parts of the <Link
LinkEnd="installation">Installation </Link> section, the <Link
LinkEnd="configure">Configuring Linux</Link> section, and the <Link
@ -287,7 +268,7 @@ Wow! We are missing that!
<ListItem>
<Para>
If trying decide between cable and DSL, read the
If trying to decide between cable and DSL, read the
<Link LinkEnd="cable">Cable vs DSL</Link> section, and possibly the
<Link LinkEnd="overview">DSL Overview</Link> section.
@ -414,13 +395,13 @@ Wow! We are missing that!
<title>Disclaimer</title>
<para>
No liability for the contents of this documents will be accepted. Use the
The authors accept no liability for the contents of this document. Use the
concepts, examples and other content at your own risk. As this is a new
edition of this document, there may be errors and inaccuracies.
Hopefully these are few and far between. The author(s) do not accept any
responsibility for incorrect or misleading information, and would appreciate
any corrections. Also, this type of technology dates itself very quickly.
What may be true today, is not guaranteed to be true tomorrow.
edition, there may be errors and inaccuracies. Hopefully these are few and
far between. The author(s) do not accept any responsibility for incorrect or
misleading information, and would certainly appreciate any corrections. Also,
this type of technology dates itself very quickly. What may be true today, is
not guaranteed to be true tomorrow.
</para>
@ -433,8 +414,8 @@ Wow! We are missing that!
</para>
<para>
The naming of any particular product, brand, or company should not be viewed
as an endorsement.
The naming of any particular product, brand, or company should not be construed
as an endorsement or recommendation.
</para>
@ -453,10 +434,11 @@ Wow! We are missing that!
Version .99 addresses some of the many changes that have occurred since the
original ADSL mini HOWTO was published. Originally, ADSL was the primary DSL
technology being deployed, but more and more some of the other DSL flavors are
entering the picture -- IDSL, SDSL, and RADSL. Thus the renaming from 'ADSL
mini HOWTO' to the 'DSL HOWTO'. There have been many other changes in DSL
technology as well. PPPoE/A encapsulation has become more and more
common as many ISPs are jumping on this bandwagon.
entering the picture -- IDSL, SDSL, G.Lite, and RADSL. Thus the renaming from
'ADSL mini HOWTO' to the 'DSL HOWTO'. There have been many other changes in
DSL technology as well. PPPoE/A encapsulation has become more and more common
as many ISPs are jumping on this bandwagon.
</Para>
<Para>
@ -803,7 +785,7 @@ Added a brief new section here. HB.
make sure it can handle the DSL signal, and possibly what level of service
may be available to you. This may take some time, especially if the telco
encounters problems with the loop. If no problems are found during this
phase, then possibly a two-three week wait for the installation.
phase, then possibly there will be a two to three week wait for the installation.
</Para>
@ -1361,7 +1343,7 @@ eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
<!-- ~~~~~ New Section ~~~~~ -->
<Sect2>
<Sect2 id="bridgevsppp">
<Title>Bridged vs PPPoX Networks</Title>
<Para>
@ -1371,21 +1353,60 @@ eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
possibility and the steps involved are quite different for each. This may not
be the kind of thing the ISP is advertising, and since you are not using
Windows, you may not have access to the setup disk that the ISP provides. If
not sure, ask the ISP's tech support staff, or other users. To muddy the
waters even more, some ISPs may be offering more than one kind of service
(over and above the various bit rate plans). Example: Bell Atlantic
originally offered static IPs with a Bridged connection. Now all new installs
use PPPoE. For installation and configuration purposes, this is very
different.
not sure, ask the ISP's tech support staff, or other users.
</Para>
<Para>
To muddy the waters even more, some ISPs may be offering more than one kind
of service (over and above the various bit rate plans). Example: Bell
Atlantic originally offered static IPs with a Bridged connection. Now all new
installs use PPPoE with dynamic IPs. For installation and configuration
purposes, this is very different.
</Para>
<Para>
The two most common DSL network implementations are Bridged/DHCP and PPPoX.
Both have mechanisms for obtaining an IP address and other related networking
configuration details so we shouldn't have to worry about this. Our job will
be finding the right client, and doing what we have to, to get it up and
running.
</Para>
<Para>
<Emphasis>Important!</Emphasis> You need to know beforehand how your ISP is
setup for connecting to his network. To re-iterate, the two main
possibilities are Bridged/DHCP and PPPoE. These are mutually exclusive
implementations. So you will need either one or the other, and it must be the
right one or you will waste a lot of time and effort. You cannot choose which
one either. It is a matter of how the ISP is doing his network. Note that
PPPoE can run over Bridged networks, so just knowing whether you are Bridged
or not, is not necessarily good enough. PPPoA is yet another alternative. If
your provider is giving you a router, there is a good chance that the
router's firmware will handle all of this for you.
</Para>
<!-- ~~~~~ New Section ~~~~~ -->
<Sect3>
<Title>Bridged/DHCP</Title>
<Para>
In the good old days of a year or two ago, 'Bridged' connections were the
norm. This type of network puts you on a local subnet just like a big
LAN. You are exposed to much of the local subnet traffic, especially ARP and
broadcast traffic. The typical means of authenticating in this set up, is via
DHCP. DHCP is a standard, established networking protocol for obtaining an IP
DHCP.
</Para
<Para>
DHCP is a standard, established networking protocol for obtaining an IP
address and other important network parameters (e.g. nameservers). This is a
very standard, well documented networking scheme and is very easy to set up
from the end user's perspective. It is also a very stable connection. You
@ -1394,63 +1415,76 @@ eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
</Para>
</Sect3>
<!-- ~ End Section ~ -->
<!-- ~~~~~ New Section ~~~~~ -->
<Sect3>
<Title>PPPoX</Title>
<Para>
The main alternative now is PPPoX, meaning either PPPoE (PPP over Ethernet)
or PPPoA (PPP over ATM). Both of these related protocols are currently being
deployed, but at the moment, PPPoE seems to be the more common of the two.
PPPoX is a relative newcomer, and, as the name implies, is a form of
Point-to-Point Protocol adapted specifically for DSL networks. From the ISPs
perspective, PPP is much easier to maintain and troubleshoot. From the end
user's perspective, it is more work to set up, and the connection is maybe
not as stable. So anyway, this seems to be the coming trend. Many of the
large telcos, especially the RBOCs (Baby Bells), have committed to PPPoX
already. Setting up a PPPoX connection is completely different from setting
up a bridged/DHCP connection.
PPPoX is a relative newcomer, and, as the name implies, is a variation of
Point-to-Point Protocol that has been adapted specifically for DSL providers.
</Para>
<Para>
There are several PPPoE clients for Linux (<Link LinkEnd="pppoe">see
below</Link>). At this moment, PPPoA support is in beta, but should be
available very soon. PPPoX simulates a dialup type environment. The user is
authenticated by user id and password which is passed to a RADIUS server,
just like good ol' dialup PPP. A routable IP address, and other related
information, is returned to the client. Of course, no actual dialing takes
place. The mechanics of how this is handled, will vary from client to client,
so best to RTFM closely. Typically you will set up configuration files like
<Filename>pap-secrets</FileName>, etc.
</Para>
<Para>
There are several PPPoE clients for Linux (see below). At this moment, PPPoA
support is in beta, but should be available very soon. These all simulate a
dialup type environment. The user is authenticated by user id and password
which is passed to a RADIUS server, just like good ol' dialup PPP. Of course,
no actual dialing takes place. The mechanics of how this is handled, will
vary from client to client, so best to RTFM closely. Typically you will set
up configuration files like <Filename>pap-secrets</FileName>, etc.
From the ISPs perspective, PPP is much easier to maintain and troubleshoot.
From the end user's perspective, it is more work to set up, and the
connection is maybe not as stable. So anyway, this seems to be the coming
trend. Many of the large telcos, especially the RBOCs (Baby Bells), have
committed to PPPoX already. Setting up a PPPoX connection is completely
different from setting up a bridged/DHCP connection.
</Para>
<Para>
Both DHCP and PPPoX have mechanisms for obtaining an IP address and other
related networking configuration details so we shouldn't have to worry about
this. Our job will be finding the right client, and doing what we have to, to
get it up and running.
</Para>
</Sect3>
<!-- ~ End Section ~ -->
<!-- ~~~~~ New Section ~~~~~ -->
<Sect3>
<Title>ATM</Title>
<Para>
A raw ATM connection is yet another possibility, but this is rare, if
implemented at all, in the U.S. This would require a modem in addition to a
Since the traffic on the wire from the DSLAM to the modem is ATM, a raw ATM
connection would seem to make sense. While possible, this is rare, if
implemented at all, in the U.S, and would require a modem in addition to a
PCI ATM card, such as the Efficient Networks 3010. There is an ATM project
for Linux, that is being incorporated into the 2.4 kernel. (See the <Link
LinkEnd="links">Links section</Link> for more.)
LinkEnd="links">Links section</Link> for more.)
</Para>
<Para>
<Command>Important!</Command> You need to know beforehand how your ISP is
setup for connecting to his network. To re-iterate, the two main
possibilities are Bridged/DHCP and PPPoE. These are mutually exclusive
implementations. So you will need either one or the other, and it must be the
right one or you will waste a lot of time and effort. You cannot choose which
one either. It is a matter of how the ISP is doing his network. Note that
PPPoE can run over Bridged networks, so just knowing whether you are Bridged
or not, is not good enough. PPPoA is yet another alternative. If your
provider is giving you a router, there is a good chance that the router's
firmware will handle all of this for you.
This may be a viable solution at some point, but it is just not 'there' yet.
</Para>
</Sect3>
</Sect2>
<!-- ~ End Section ~ -->
@ -1474,7 +1508,7 @@ eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
</Para>
<Para>
With PPPoE/A, once the connection comes up, there will be a 'ppp0' interface,
With PPPoX, once the connection comes up, there will be a 'ppp0' interface,
just like dialup. This will become the WAN interface, but for configuration
purposes we will we still be concerned with 'eth0' initially.
@ -1530,13 +1564,15 @@ eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
<!-- ~~~~~ New Section ~~~~~ -->
<Sect3>
<Title>Static IP</Title>
<Title>Static IP Configuration</Title>
<Para>
A 'static' IP address is an IP that is guaranteed not to change. This is the
preferred way to go for those wanting to host a domain or run some type of
public server, but is not available from all ISPs. Skip this section if you
do not have a static IP.
do not have a static IP, or if you have a router, and the router will be
assigned the static IP.
</Para>
<Para>
@ -1574,14 +1610,14 @@ eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
<!-- ~~~~~ New Section ~~~~~ -->
<Sect3>
<Title>Bridged/DHCP</Title>
<Title>Bridged/DHCP Configuration</Title>
<Para>
ISPs that have Bridged networks typically use DHCP to assign an IP addresses,
and authenticate the user. All distributions come with one or more DHCP
clients. <Command>dhcpcd</Command> seems to be the most common.
<Command>pump</Command> comes with Redhat based distributions as of Redhat
6.0. The client will obtain an IP 'lease' from the ISP's server as well as
6.0. The DHCP client will obtain an IP 'lease' from the ISP's server as well as
other related information: gateway address, DNS servers, and network mask.
The lease will be 'renewed' at regular intervals according to the ISP's
configuration.
@ -1634,8 +1670,8 @@ eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
<!-- ~~~~~ New Section ~~~~~ -->
<Sect3 id="ppoe">
<Title>PPPoE</Title>
<Sect3 id="pppoe">
<Title>PPPoE Configuration</Title>
<Para>
PPPoE (PPP over Ethernet) is an alternate way for ISPs to control your
@ -1644,7 +1680,7 @@ eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
DHCP above. Some distros are now shipping PPPoE clients. If this is not the
case for you, then you will have to download one. Check any Linux archive
site like <Ulink URL="http://freshmeat.net">http://freshmeat.net</Ulink>,
etc.
etc. or look below.
</Para>
@ -1757,28 +1793,27 @@ eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
<Para>
PPPoA (PPP over ATM) is a cleaner solution than PPPoE since most of the work
is done in hardware. There is no client necessary to manage the connection as
with PPPoE. Authentication is still the same: user id and password to
connect, but the mechanics are different since no ethernet encapsulation takes
place.
is done in hardware, and since the raw DSL traffic is ATM. There is no client
necessary to manage the connection as with PPPoE. Authentication is still the
same: user id and password to connect, but the mechanics are different since
no ethernet encapsulation takes place.
</Para>
<Para>
As of this moment, there is not really a viable, working implementation of
PPPoA for Linux. There is an ATM patch for 2.2 kernels, support
for ATM in the 2.4.x kernel, and a project based on the Efficient Networks
3010 [possibly out of production], as well as other ATM cards. The ATM on
Linux homepage is here: <Ulink URL="http://lrcwww.epfl.ch/linux-atm/">
http://lrcwww.epfl.ch/linux-atm/</Ulink>. And even more info is at <Ulink
URL="http://www.sfgoth.com/~mitch/linux/atm/pppoatm/">
http://www.sfgoth.com/~mitch/linux/atm/pppoatm/</Ulink> from the kernel
developer of this project. Existing PPPoA implementations are
hardware/driver based, and Linux PPPoA modem drivers are scarce as hen's teeth
at this time. The above modem does not seem to be available through normal
retail channels. This may well be a problem, if this is the only protocol an
ISP delivers. At the very least, some rather serious hoop jumping is in order.
As of this moment, there is not really a viable, working implementation of
PPPoA for Linux. There is an ATM patch for 2.2 kernels, support for ATM in
the 2.4.x kernel, and a project based on the Efficient Networks 3010
[possibly out of production], as well as other ATM cards. The ATM on Linux
homepage is here: <Ulink URL="http://lrcwww.epfl.ch/linux-atm/">
http://lrcwww.epfl.ch/linux-atm/</Ulink>. And even more info is at <Ulink
URL="http://www.sfgoth.com/~mitch/linux/atm/pppoatm/">
http://www.sfgoth.com/~mitch/linux/atm/pppoatm/</Ulink> from the kernel
developer of this project. Existing PPPoA implementations are hardware/driver
based, and Linux PPPoA modem drivers are scarce as hen's teeth at this time.
The above modem does not seem to be available through normal retail channels.
This may well be a problem, if this is the only protocol an ISP delivers. At
the very least, some rather serious hoop jumping is in order.
</Para>
@ -1839,8 +1874,11 @@ ISP delivers. At the very least, some rather serious hoop jumping is in order.
since your first 'hop' will be the router's interface and not the ISP's
gateway. Routers will actually have two interfaces -- one that you
connect to from the LAN side, and one that connects to your ISP on the WAN
side. Your point of exposure here is the WAN interface of the router. The
router will also have a pre-configured, private IP address that you will
side. Your point of exposure here is the WAN interface of the router.
</Para>
<Para>
The router will also have a pre-configured, private IP address that you will
connect to from the LAN side. This will be your gateway. The public IP
address will be assigned to the WAN side interface. Typically these devices
also act as DHCP servers for the LAN side as well. So possibly all you have
@ -1856,10 +1894,10 @@ ISP delivers. At the very least, some rather serious hoop jumping is in order.
If you are a PPPoX customer, and the router is handling this part of the
connection, then you will have to configure at least your user id and
password before connecting. If a Bridged/DHCP customer, you should just have
to activate DHCP on the router, and register the MAC (hardware address) of
the router with your provider. Some routers have 'MAC cloning' which means
that they will report the MAC address of the attached NIC. If static IP,
then you will have to configure this as well.
to activate DHCP on the router, and possibly register the MAC (hardware
address) of the router with your provider. Some routers have 'MAC cloning'
which means that they will report the MAC address of the attached NIC. If
static IP, then you will have to configure this as well.
</Para>
@ -1920,7 +1958,7 @@ ISP delivers. At the very least, some rather serious hoop jumping is in order.
<!-- ~~~~~ New Section ~~~~~ -->
<Sect2 id="connect">
<Title>Connection</Title>
<Title>Connect</Title>
<Para>
Everything should be in place now. You probably have already tested your
@ -3170,7 +3208,7 @@ ISP delivers. At the very least, some rather serious hoop jumping is in order.
typically provides dedicated, 'always on' access, it can be used for
interconnecting low to mid range bandwidth servers, and provides a great
access solution for small LANs. It is also great for those Linux power users
that just want a fast pipe &nbsp; :-).
that just want a fast pipe :-).
</Para>
@ -3943,7 +3981,7 @@ Downstream/Upstream
<ListItem>
<Para>
<Emphasis>Connection Limits</Emphasis>. Is it 'always on' (at least
theoretically &nbsp; :-)? Are there session limits, or idle timeouts? Is
theoretically :-)? Are there session limits, or idle timeouts? Is
bandwidth metered and limited to so much per month? Do they forbid a LAN
behind the connection (dumb!)?
</Para>
@ -4011,15 +4049,10 @@ Downstream/Upstream
<!-- ~~~~~~~~ New Section Header ~~~~~~~~~ -->
<Sect1 id="appendix">
<Title>Appendix: Miscellaneous</Title>
<Sect2 id="faq">
<Title>FAQs</Title>
<Sect1 id="faq">
<Title>Appendix: FAQs</Title>
<Para>
Some Frequently Asked Questions about DSL and Linux.
@ -4072,7 +4105,7 @@ Downstream/Upstream
<Para>
If an incompatible modem puts you in a bind, hopefully you will take the
time to politely harass the manufacturer &nbsp; :-).
time to politely harass the manufacturer :-).
</Para>
@ -4543,18 +4576,26 @@ Downstream/Upstream
<Para>
This is but a very small sampling. These are NOT endorsements of the products
listed, just provided for illustration. &nbsp; ;-).
listed, just provided for illustration. ;-).
</Para>
</Sect2>
</Sect1>
<!-- ~ End Section ~ -->
<!-- ~~~~~~~~ New Section Header ~~~~~~~~~ -->
<Sect1 id="appendix">
<Title>Appendix: Miscellaneous</Title>
<!-- ~~~~~ New Section ~~~~~ -->
<Sect2 id="links">
@ -4698,7 +4739,7 @@ Downstream/Upstream
<ListItem>
<Para>
A white paper from Redback on the technology and rational behind PPPoE can
A white paper from Redback on the technology and rationale behind PPPoE can
be found at
<Ulink
URL="http://www.redback.com/frameset.asp?page=whitepp/wp_pppoe_comparison.html">http://www.redback.com/frameset.asp?page=whitepp/wp_pppoe_comparison.html</Ulink>.
@ -5715,7 +5756,7 @@ Downstream/Upstream
<Title>Compatible Modems</Title>
<Para>
This is an easy one right now &nbsp;;-):
This is an easy one right now ;-):
</Para>