mirror of https://github.com/tLDP/LDP
Version 1.6, minor updates.
This commit is contained in:
parent
ac9dbd8176
commit
168a1861f4
|
@ -7,7 +7,7 @@
|
|||
|
||||
<Title>DSL HOWTO for Linux</Title>
|
||||
|
||||
<PubDate>v1.5, 2002-01-07</PubDate>
|
||||
<PubDate>v1.6, 2002-05-23</PubDate>
|
||||
|
||||
<AuthorGroup>
|
||||
<AUTHOR>
|
||||
|
@ -24,9 +24,6 @@
|
|||
<FirstName>Original Author: David</FirstName>
|
||||
<SurName>Fannin</SurName>
|
||||
<Affiliation>
|
||||
<Address>
|
||||
<Email>dfannin@sushisoft.com</Email>
|
||||
</Address>
|
||||
</Affiliation>
|
||||
</AUTHOR>
|
||||
|
||||
|
@ -71,6 +68,14 @@ section.
|
|||
|
||||
<RevHistory>
|
||||
|
||||
<Revision>
|
||||
<RevNumber>v1.6</RevNumber>
|
||||
<Date>2002-05-23</Date>
|
||||
<Authorinitials>hb</Authorinitials>
|
||||
<RevRemark>
|
||||
Various small updates.
|
||||
</RevRemark>
|
||||
</Revision>
|
||||
<Revision>
|
||||
<RevNumber>v1.5</RevNumber>
|
||||
<Date>2002-01-07</Date>
|
||||
|
@ -135,6 +140,7 @@ section.
|
|||
</Revision>
|
||||
</RevHistory>
|
||||
|
||||
|
||||
<KeywordSet>
|
||||
<Keyword>DSL</Keyword>
|
||||
<Keyword>xDSL</Keyword>
|
||||
|
@ -163,7 +169,7 @@ section.
|
|||
aspell -H -c DSL-HOWTO.sgml
|
||||
submit@linuxdoc.org
|
||||
|
||||
export CVSROOT=:pserver:hal@cvs.linuxdoc.org:/cvsroot
|
||||
export CVSROOT=:pserver:hal@cvs.tldp.org:/cvsroot
|
||||
cvs -d $CVSROOT login
|
||||
pword: XXXXXXXXXXXXXX
|
||||
|
||||
|
@ -178,11 +184,89 @@ check here: http://cvs.pld.org.pl/LDP/howto/docbook/DSL-HOWTO.sgml
|
|||
alex alex@bennee.com, user land A STUSB.
|
||||
|
||||
====================================================================
|
||||
|
||||
Begin 1.6 01/07/02
|
||||
Todo:
|
||||
Add something on usepeerdns per Timo Karjalainen timo.karjalainen@myorigo.com
|
||||
|
||||
|
||||
Release 1.5 to LDP 01/07/02
|
||||
Begin 1.6 01/07/02 submitted 05/23/02
|
||||
Changes:
|
||||
new faq re: distance CO vs DSLAM
|
||||
minor touch ups to DSL family.
|
||||
Trouble: setup both chap and pap
|
||||
Removed sympatico from ISPs.
|
||||
Xpeed not in 2.4.
|
||||
Made table of out of distance chart
|
||||
Alarm re-write.
|
||||
|
||||
|
||||
|
||||
|
||||
From: "Jordi Domenech M." jordi@domenech.com.mx
|
||||
Date: Thu, 4 Apr 2002 04:09:16 -0600
|
||||
|
||||
Hi,
|
||||
I would like to add to the Friendly ADSL ISP's List in the DSL-Howto my service
|
||||
provider:
|
||||
ISP Name: Prodigy/Telmex
|
||||
Product Name: Infinitum (ADSL)
|
||||
URL: http://www.miembrosprodigy.com.mx/int/prod_prodigy_infinitum.html
|
||||
Comments: Static or Dynamic IP (depending on DSL modem provided), PPPoE, they
|
||||
provide the DSL Modem (Alcatel SpeedTouch Home, Pro and USB).
|
||||
Available at: Mexico City, Guadalajara, Monterrey (more coming soon)
|
||||
Greetings, and congrats for the howto. If you need more info, please contact
|
||||
me!
|
||||
|
||||
|
||||
=================
|
||||
Erik Sigra sigra@home.se:
|
||||
|
||||
Bostream:
|
||||
http://www.bostream.se
|
||||
Mentions Linux among the operating systems. Static IP-addres. Servers
|
||||
allowed if not high traffic and not commercial.
|
||||
|
||||
Telia:
|
||||
http://www.telia.se/bvo/info/gen_info_bred.jsp.html?OID=Telia_ADSL_Bredband
|
||||
Linux possible but not supported. Dynamic IP-addres.
|
||||
|
||||
Telenorida:
|
||||
https://selfcare.telenordia.se/adsltn/
|
||||
Mentions Linux among the operating systems, free support but not for
|
||||
the UNIX operating systems. Dynamic IP-addres.
|
||||
|
||||
On Mon, Feb 25, 2002 at 03:34:55PM -0600, Eckdahl, Larry wrote:
|
||||
> Webperception in Novato, California.
|
||||
> Uses local Verizon provider, who also provides DSL modem.
|
||||
> www.webperception.com
|
||||
> Service in Novato, Los Gatos and Morgan Hill.
|
||||
|
||||
|
||||
From: Øyvind Rangøy rangoy@online.no
|
||||
Date: Fri, 1 Feb 2002 20:43:54 +0200
|
||||
Subject: Linux Friendly DSL-provider in Estonia
|
||||
|
||||
Sending this tip as requested in the Linux DSL-HOWTO:
|
||||
The Estonian provider Atlas (Eesti Telefon) (http://www.atlas.et.ee) is linux
|
||||
friendly, and provides linux software by default
|
||||
with their different ADSL services.
|
||||
|
||||
|
||||
|
||||
From: Akavia araka@netvision.net.il
|
||||
Date: Fri, 01 Feb 2002 19:19:43 +0200
|
||||
Subject: DSL for israel
|
||||
|
||||
Dear sir,
|
||||
There is a howto on how to setup DSL for Israeli ISPs. It is at the
|
||||
address
|
||||
http://vipe.technion.ac.il/~mulix/adsl-howto.txt.
|
||||
|
||||
It is very important, since they use PPTP in israel, with quirks.
|
||||
I hope you can link to this site.
|
||||
|
||||
|
||||
|
||||
Released 1.5 to LDP 01/07/02
|
||||
Begin 1.5 12/10/01
|
||||
|
||||
Changes:
|
||||
|
@ -198,7 +282,7 @@ Changes:
|
|||
fixed _screen_ tags 12/31/01
|
||||
removed linux.com.sg/news/atm/
|
||||
rewrite new tuning section on iproute 01/02/02
|
||||
reworked SpeedTouch section again.
|
||||
reworked SpeedTouch section again. (major)
|
||||
|
||||
|
||||
ToDo:
|
||||
|
@ -538,6 +622,12 @@ This is not a real glossary, it's just an example.
|
|||
|
||||
<Sect2>
|
||||
<Title>What's New</Title>
|
||||
<para>
|
||||
1.6: Several new Linux Friendly ISPs. Clarification on
|
||||
problems with alarm systems. Minor touch ups to other sections, and fix some
|
||||
broken links (never ending job :).
|
||||
|
||||
</para>
|
||||
<para>
|
||||
1.5: New Tuning sub-section using <application>iproute</application>. Hot
|
||||
stuff! Other additions to the Tuning section. A few new ISPs. Alcatel
|
||||
|
@ -574,7 +664,7 @@ This is not a real glossary, it's just an example.
|
|||
Version 1.1 included quite a few minor corrections, updates,
|
||||
and additions. Not much that is substantially new. There are finally two
|
||||
Linux compatible DSL PCI modems from Xpeed. The drivers are now in the kernel
|
||||
2.2.18 source.
|
||||
2.2.18 source (not ported to 2.4 as of this writing 05/23/02).
|
||||
|
||||
</Para>
|
||||
|
||||
|
@ -726,10 +816,9 @@ This is not a real glossary, it's just an example.
|
|||
</para>
|
||||
|
||||
<para>
|
||||
All copyrights are held by their by their respective owners, unless
|
||||
specifically noted otherwise. Use of a term in this document
|
||||
should not be regarded as affecting the validity of any trademark
|
||||
or service mark.
|
||||
All copyrights are held by their respective owners, unless specifically noted
|
||||
otherwise. Use of a term in this document should not be regarded as affecting
|
||||
the validity of any trademark or service mark.
|
||||
|
||||
</para>
|
||||
|
||||
|
@ -1054,7 +1143,8 @@ This is not a real glossary, it's just an example.
|
|||
|
||||
<ListItem>
|
||||
<Para>
|
||||
Linux friendly, Linux hostile, or Linux agnostic?
|
||||
Linux friendly, Linux hostile, or Linux agnostic? This is not as much of
|
||||
a problem as it used to be in most areas.
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
@ -1546,10 +1636,13 @@ This is not a real glossary, it's just an example.
|
|||
</Para>
|
||||
|
||||
<Para>
|
||||
<Emphasis>Warning!</Emphasis> If you have an alarm system, it is recommended
|
||||
not to use microfilters. Alarm systems can present various problems,
|
||||
depending on the type of alarm and how it is installed. The recommended
|
||||
installation in this case is with a splitter.
|
||||
<Emphasis>Warning!</Emphasis>
|
||||
Alarm systems can present various problems, depending on the type of alarm
|
||||
and how it is installed. This may require telco help for proper installation
|
||||
so the one does not interfere with the other. Microfilters tend not to work
|
||||
because most alarm boxes use a different size jack. Filters are now available
|
||||
just for alarm boxes, though traditionally this has been handled with a
|
||||
splitter type installation.
|
||||
</Para>
|
||||
|
||||
</Sect2>
|
||||
|
@ -2187,7 +2280,7 @@ eth0 Link encap:Ethernet HWaddr 00:50:04:C2:09:AC
|
|||
2.4.x kernels include native PPPoE support. The PPPoE for 2.4 page is
|
||||
<Ulink
|
||||
URL="http://www.shoshin.uwaterloo.ca/~mostrows/">http://www.shoshin.uwaterloo.ca/~mostrows</Ulink>
|
||||
and is by Michal Ostrowski, the maintainer for kernel PPPoE. This
|
||||
[link is dead, sorry, can't find new page] and is by Michal Ostrowski, the maintainer for kernel PPPoE. This
|
||||
includes detailed instructions for installing and configuring kernel
|
||||
mode PPPoE.
|
||||
|
||||
|
@ -2325,8 +2418,8 @@ ppp0 Link encap:Point-to-Point Protocol
|
|||
like there is for PPPoE. 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,
|
||||
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://linux-atm.sourceforge.net/">
|
||||
http://linux-atm.sourceforge.net/</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
|
||||
|
@ -3048,7 +3141,7 @@ defaultroute
|
|||
Linux networking is pretty robust, even a default installation with no
|
||||
<Quote>tuning</Quote>. You may well not need to do anything else. But if your
|
||||
connection is not performing up to what you think it should be, then possibly
|
||||
there is a problem somewhere. This is may be a more worthwhile approach than
|
||||
there is a problem somewhere. This may be a more worthwhile approach than
|
||||
the pursuit of any magical <Quote>tweak</Quote>.
|
||||
</Para>
|
||||
|
||||
|
@ -3057,13 +3150,55 @@ defaultroute
|
|||
expect as a maximum sync rate, based on distance from DSLAM/CO:
|
||||
|
||||
</Para>
|
||||
|
||||
<!--
|
||||
<LiteralLayout>
|
||||
0-12 K ft (0-3.6 km) - 2000 Kbps or more (8100 max for ADSL)
|
||||
12-16 K ft (3.6-4.6 km) - 1500 Kbps -> 1000 Kbps
|
||||
16-18 K ft (4.6-5.4 km) - 1200 Kbps -> 512 Kbps
|
||||
18-?? K ft (5.4-?? km) - 512 Kbps -> 128 Kbps or less :(
|
||||
</LiteralLayout>
|
||||
-->
|
||||
<informaltable label="Distances" pgwide="1">
|
||||
<tgroup cols=2 align="left" colsep=1 rowsep=1>
|
||||
<colspec colname=c1 align="center" colwidth="40">
|
||||
<colspec colname=c2 align="center" colwidth="40">
|
||||
<tbody>
|
||||
<row>
|
||||
<entry align="right" colname="c1">
|
||||
0-12 K ft (0-3.6 km)
|
||||
</entry>
|
||||
<entry align="left" colname="c2">
|
||||
2000 Kbps or more (8100 max for ADSL)
|
||||
</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry align="right" colname="c1">
|
||||
12-16 K ft (3.6-4.6 km)
|
||||
</entry>
|
||||
<entry align="left" colname="c2">
|
||||
1500 Kbps to 1000 Kbps
|
||||
</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry align="right" colname="c1">
|
||||
16-18 K ft (4.6-5.4 km)
|
||||
</entry>
|
||||
<entry align="left" colname="c2">
|
||||
1200 Kbps to 512 Kbps
|
||||
</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry align="right" colname="c1">
|
||||
18-?? K ft (5.4-?? km)
|
||||
</entry>
|
||||
<entry align="left" colname="c2">
|
||||
512 Kbps to 128 Kbps or less :(
|
||||
</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable>
|
||||
|
||||
|
||||
<Para>
|
||||
There are many conceivable factors that could effect this one way or the
|
||||
|
@ -3646,6 +3781,13 @@ the Receive Window:
|
|||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
CHAP, PAP, or other? I would set up both CHAP and PAP (see man pppd)
|
||||
just to be safe.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
Try pinging the default gateway's address. Get this with '<Command>route
|
||||
|
@ -3658,7 +3800,7 @@ the Receive Window:
|
|||
|
||||
<ListItem>
|
||||
<Para>
|
||||
For PPPoE, let the PPPoE client bring up the ethernet interface. Do not
|
||||
For <application>rp-pppoe</application>, let the PPPoE client bring up the ethernet interface. Do not
|
||||
have it come up on boot. Make sure there is no existing default route
|
||||
before starting PPPoE. For rp-pppoe, David Skoll recommends that
|
||||
<Filename>/etc/ppp/options</FileName> be left empty.
|
||||
|
@ -3667,12 +3809,21 @@ the Receive Window:
|
|||
|
||||
<ListItem>
|
||||
<Para>
|
||||
If running a firewall (e.g. with ipchains), try temporarily taking it
|
||||
down. Possibly this is misconfigured, and not allowing packets through.
|
||||
If running a firewall (e.g. with <application>ipchains</application>), try
|
||||
temporarily taking it down. Possibly this is misconfigured, and not
|
||||
allowing packets through.
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Roaring Penguin has a very nice debug output with all kinds of
|
||||
system info, and even tips for correcting problems. See the docs
|
||||
for turning this well-done feature on.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
If the modem was purchased from a source other than your ISP, it may the
|
||||
|
@ -3691,7 +3842,6 @@ the Receive Window:
|
|||
</Para>
|
||||
|
||||
</ListItem>
|
||||
|
||||
|
||||
</ItemizedList>
|
||||
</Para>
|
||||
|
@ -4399,22 +4549,22 @@ the Receive Window:
|
|||
<Para>
|
||||
Asymmetric Digital Subscriber Loop currently supports downstream rates up
|
||||
to 8 Mbps, and upstream of 1024 Kbps, hence the <Quote>asymmetric</Quote>.
|
||||
The most widely deployed form of DSL at this time, and was specifically
|
||||
developed for the home and SOHO markets. The higher downstream rates lends
|
||||
itself to those not running serious servers -- at least anything more than
|
||||
a small, personal web site. ADSL is capable of sharing data with a POTS
|
||||
voice line, so an additional line is not required. A big selling point.
|
||||
ADSL, like other DSLs, is limited by distance. 18,000 ft (5.5 km) is a
|
||||
typical cut-off point for telcos. ADSL does typically require either a
|
||||
splitter or filters to isolate the DSL signal from POTS. Sometimes referred
|
||||
to as <Quote>full rate</Quote> ADSL in order to differentiate it from
|
||||
G.Lite DSL. There are two common line encodings for ADSL: DMT and CAP. DMT
|
||||
(a.k.a. Alcatel compatible) has won the standards battle and is now the
|
||||
standard and the more common of the two. Also, note that modems must be
|
||||
compatible with the encoding. In other words, a CAP modem will not work
|
||||
with a DMT service, and vice versa.
|
||||
ADSL is far and away the most widely deployed consumer DSL, and was
|
||||
specifically developed for the home and SOHO markets. The higher downstream
|
||||
rates lends itself to those not running serious servers -- at least
|
||||
anything more than a small, personal web site. ADSL is capable of sharing
|
||||
data with a POTS voice line, so an additional line is not required. A big
|
||||
selling point. ADSL, like other DSLs, is limited by distance. 18,000 ft
|
||||
(5.5 km) is a typical cut-off point for telcos. ADSL does typically require
|
||||
either a splitter or filters to isolate the DSL signal from POTS. Sometimes
|
||||
referred to as <Quote>full rate</Quote> ADSL in order to differentiate it
|
||||
from G.Lite DSL. There are two line encodings for ADSL: DMT and CAP.
|
||||
DMT (a.k.a. Alcatel compatible) has won the standards battle and is now
|
||||
the standard and the most common. Also, note that modems must be compatible
|
||||
with the encoding. In other words, a CAP modem will not work with a DMT
|
||||
service, and vice versa.
|
||||
|
||||
</Para>
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<ListItem>
|
||||
|
@ -4443,11 +4593,12 @@ the Receive Window:
|
|||
dedicated line, and thus true SDSL is not as readily adaptable to the
|
||||
consumer market as ADSL. SDSL also uses a 2B1Q encoding (same as ISDN and
|
||||
some T1) which is considered more robust than the DMT or CAP encoding of
|
||||
ADSL. True SDSL is generally considered more of a server quality DSL. It is
|
||||
worth noting that some providers may be marketing a <Quote>SDSL</Quote>
|
||||
service that is really ADSL pinched so that upstream/downstream are the
|
||||
same. Or vice versa, SDSL with asymmetrically allocated bandwidth.
|
||||
Wasn't all this confusing enough already?
|
||||
ADSL. True SDSL is generally considered more of a server quality DSL, and
|
||||
is typically marketed as a business class service. It is worth noting that
|
||||
some providers may be promoting a <Quote>SDSL</Quote> service that is
|
||||
really ADSL pinched so that upstream/downstream are the same. Or vice
|
||||
versa, SDSL with asymmetrically allocated bandwidth. Wasn't all this
|
||||
confusing enough already?
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
@ -4464,6 +4615,7 @@ the Receive Window:
|
|||
DSLs, and provides an additional 16 Kbps over traditional ISDN. It is being
|
||||
marketed by some DSL providers as a low end bit rate option, where line
|
||||
quality is not sufficient for higher speeds such as that of ADSL.
|
||||
Ironically, IDSL is generally priced significantly higher than ADSL.
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
@ -4523,7 +4675,7 @@ the Receive Window:
|
|||
<BridgeHead renderas=sect3>G.SHDSL</BridgeHead>
|
||||
|
||||
<Para>
|
||||
The standards for G.SHDSL have just recently been finalized. SHSDSL
|
||||
The standards for G.SHDSL have just recently been finalized. SHDSL
|
||||
includes many enhancements, including better reach, better rate adaptation,
|
||||
and better upstream bandwidth. G.SHDSL is symmetric with speeds up to 2.3
|
||||
Mbps, and will more than likely be marketed as an SDSL alternative.
|
||||
|
@ -4725,14 +4877,15 @@ the Receive Window:
|
|||
<Para>
|
||||
As always, there are exceptions. <Ulink URL="http://www.xpeed.com">Xpeed</Ulink>
|
||||
now has drivers for two PCI modems included with the kernel drivers (as of
|
||||
2.2.18). These are the first open source Linux DSL modem drivers, and is
|
||||
welcomed news. <Ulink URL="http://www.alcateldsl.com">Alcatel's</Ulink> ADSL
|
||||
SpeedTouch USB modem now has Linux drivers. Diamond makes an internal PCI
|
||||
modem which has binary-only drivers, but it is not in widespread use, and
|
||||
seems to be discontinued at this point. It is also possible to make a direct
|
||||
ATM connection using a modem plus an ATM network card, though this delivery
|
||||
system is not used in the U.S. as far as I know, and should not be considered
|
||||
as a viable option. This would also require a 2.4 kernel.
|
||||
2.2.18, not in 2.4 yet though). These are the first open source Linux DSL modem
|
||||
drivers, and is welcomed news. <Ulink
|
||||
URL="http://www.alcateldsl.com">Alcatel's</Ulink> ADSL SpeedTouch USB modem
|
||||
now has Linux drivers. Diamond makes an internal PCI modem which has
|
||||
binary-only drivers, but it is not in widespread use, and seems to be
|
||||
discontinued at this point. It is also possible to make a direct ATM
|
||||
connection using a modem plus an ATM network card, though this delivery
|
||||
system is not used in the U.S. as far as I know, and should not be
|
||||
considered as a viable option. This would also require a 2.4 kernel.
|
||||
|
||||
</Para>
|
||||
|
||||
|
@ -5324,6 +5477,22 @@ Downstream/Upstream
|
|||
</Para>
|
||||
|
||||
</ListItem>
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
Q. I am told I am 20,000 ft from the CO. Isn't that too far? Will my
|
||||
speeds be really bad?
|
||||
|
||||
</Para>
|
||||
|
||||
<Para>
|
||||
Not necessarily. This distance limitation is not where the CO is, but
|
||||
where the DSLAM is. These are often installed in CO's, but more and more
|
||||
are being installed in remote locations in order to expand the reach
|
||||
of DSL service.
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
|
@ -5564,9 +5733,9 @@ Downstream/Upstream
|
|||
At the most basic level, a 386 will work fine. In most situations, you are
|
||||
connected to what is essentially an ethernet based network. So
|
||||
theoretically anything that can handle a very slow ethernet connection
|
||||
would work. No comment on well Netscape will run on a 386 though ;-) But as
|
||||
far as just managing a raw connection, a 386 is indeed workable. What else
|
||||
you can do with it, is another matter.
|
||||
would work. No comment on how well Netscape will run on a 386 though ;-)
|
||||
But as far as just managing a raw connection, a 386 is indeed workable.
|
||||
What else you can do with it, is another matter.
|
||||
|
||||
</Para>
|
||||
|
||||
|
@ -5722,7 +5891,7 @@ Downstream/Upstream
|
|||
card. But this is rarely done in practice since many Operating Systems
|
||||
can't speak ATM natively, and the cost of ATM cards is more than ethernet.
|
||||
See <Ulink
|
||||
URL="http://lrcwww.epfl.ch/linux-atm/">http://lrcwww.epfl.ch/linux-atm/</Ulink>
|
||||
URL="http://linux-atm.sourceforge.net/">http://linux-atm.sourceforge.net/</Ulink>
|
||||
for more details.
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
@ -6126,7 +6295,8 @@ Downstream/Upstream
|
|||
<Para>
|
||||
More on the 2.4 kernel packet filtering from The Netfilter Project at <Ulink
|
||||
URL="http://netfilter.samba.org/">http://netfilter.samba.org/</Ulink>.
|
||||
Several good HOWTOs for the new features available with 2.4 kernels.
|
||||
Several good HOWTOs for the new features available with 2.4 kernels
|
||||
and <application>iptables</application>.
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
@ -6213,7 +6383,7 @@ Funky URL 06/21/01
|
|||
|
||||
<ListItem>
|
||||
<Para>
|
||||
VPN and Masquerading on Linux: <Ulink URL="http://www.wolfenet.com/~jhardin/ip_masq_vpn.html">http://www.wolfenet.com/~jhardin/ip_masq_vpn.html</Ulink>
|
||||
VPN and Masquerading on Linux: <Ulink URL="http://www.tldp.org/HOWTO/VPN-Masquerade-HOWTO.html">http://www.tldp.org/HOWTO/VPN-Masquerade-HOWTO.html</Ulink>
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
@ -6295,18 +6465,6 @@ Funky URL 06/21/01
|
|||
</ListItem>
|
||||
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
My ipchains script is at <Ulink
|
||||
URL="http://personal.bellsouth.net/~hburgiss/linux/ipchains.html">
|
||||
http://personal.bellsouth.net/~hburgiss/linux/ipchains.html</Ulink>.
|
||||
This has IP Masquerading already set up, is reasonably well commented, and
|
||||
may make a quick starting point for your own script with only
|
||||
minor adjustments to suit your situation.
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
Here a few pages dedicated to using Linux with specific providers. (I
|
||||
|
@ -6391,6 +6549,13 @@ no findo 06/21/01
|
|||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Israel (various ISPs covered):
|
||||
<ulink url="http://vipe.technion.ac.il/~mulix/adsl-howto.txt">http://vipe.technion.ac.il/~mulix/adsl-howto.txt</ulink>
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</ItemizedList>
|
||||
</Para>
|
||||
|
||||
|
@ -6497,15 +6662,6 @@ kaput????
|
|||
<Sect2 id="glossary">
|
||||
<Title>Glossary</Title>
|
||||
|
||||
|
||||
<comment>There are a bunch of tags designed for marking up
|
||||
glossaries. Take a look at
|
||||
http://www.docbook.org/tdg/html/glossary.html and some of the
|
||||
pages following it.
|
||||
|
||||
HB-Looks a little time consuming. FIXMELATER
|
||||
</comment>
|
||||
|
||||
<Para>
|
||||
A dictionary of some of the jargon used in this Document, and in the
|
||||
telco and DSL industries.
|
||||
|
@ -6773,21 +6929,6 @@ kaput????
|
|||
</ListItem>
|
||||
</VarListEntry>
|
||||
|
||||
<VarListEntry>
|
||||
<Term>ILEC</Term>
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
Incumbent Local Exchange Carrier. The Regional phone company that
|
||||
physically owns the lines. Examples: Bell Atlantic and Pacific Bell. FCC
|
||||
regulations are forcing the ILECs to open up their networks to independent
|
||||
providers. This is allowing an independent like Covad to
|
||||
offer competitive services. This is a good thing for consumers IMHO.
|
||||
</Para>
|
||||
|
||||
</ListItem>
|
||||
</VarListEntry>
|
||||
|
||||
<VarListEntry>
|
||||
<Term>Interleaving</Term>
|
||||
|
||||
|
@ -7522,7 +7663,7 @@ compatible</Quote>.
|
|||
<Para>
|
||||
To add a name to this list, mail <ULink
|
||||
URL="mailto:hal@foobox.net?Subject=LinuxFriendlyISP">Linux
|
||||
Friendly</ULink>. Please included ISP's official name, URL (if not obvious),
|
||||
Friendly</ULink>. Please include ISP's official name, URL (if not obvious),
|
||||
location and coverage area, modem type, server policy, and any other
|
||||
pertinent details.
|
||||
|
||||
|
@ -7546,12 +7687,19 @@ compatible</Quote>.
|
|||
<ListItem>
|
||||
<Para>
|
||||
<Ulink Url="http://www.directtvdsl.com">DirectTV DSL (formerly
|
||||
Telocity)</Ulink>: Static IP, no PPPoX, liberal server policy. Reports of
|
||||
poor tech support. National. They have their own proprietary modem, but
|
||||
Telocity)</Ulink>: Static IP, no PPPoX, liberal server policy.
|
||||
National. They have their own proprietary modem, but
|
||||
it is ethernet based.
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
<Ulink Url="http://www.dsli.com">DSLi</Ulink>: Static IP, no PPPoX,
|
||||
personal servers allowed, static IP available.
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
|
@ -7703,7 +7851,7 @@ compatible</Quote>.
|
|||
greater Los Angeles area. Static IP, personal servers allowed.
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<!--
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
|
@ -7712,7 +7860,7 @@ compatible</Quote>.
|
|||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
-->
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="http://istop.com/">istop.com, The Internet Stop</ulink>,
|
||||
|
@ -7724,24 +7872,29 @@ compatible</Quote>.
|
|||
</para>
|
||||
</listitem>
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
<Ulink URL="http://www.bell.ca/en/ps/pers/internet/sympatico/default.asp">
|
||||
Bell Canada's Sympatico High Speed Edition</Ulink>. PPPoE.
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<ListItem>
|
||||
<Para>
|
||||
<Ulink URL="http://www.vic.com/">http://www.vic.com/</Ulink>,
|
||||
Virtual Interactive Center, Knoxville, TN and surrounding areas.
|
||||
Bridged connection (no PPP), static IP available (additional cost),
|
||||
personal servers are allowed, and runs on Linux.
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="http://www.webperception.com">WebPerception</ulink>,
|
||||
Novato, Los Gatos, and Morgan Hill areas of California.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="http://www.miembrosprodigy.com.mx/int/prod_prodigy_infinitum.html">Prodigy/Telmex</ulink>,
|
||||
covering Mexico City, Guadalajara, and Monterrey Mexico. Static IP available.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</ItemizedList>
|
||||
</Para>
|
||||
|
||||
|
@ -7791,10 +7944,38 @@ compatible</Quote>.
|
|||
<Para>
|
||||
<Ulink URL="http://www.tiscali.it/">Tiscali ADSL</Ulink>,
|
||||
Italy.
|
||||
|
||||
</Para>
|
||||
</ListItem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="http://www.atlas.et.ee">Eesti Telefon</ulink>, Estonia, they even
|
||||
include Linux software!
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="http://www.bostream.se">Bostream</ulink>, Sweden, static IP
|
||||
available, non-commercial servers allowed.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="http://www.telia.se/bvo/info/gen_info_bred.jsp.html?OID=Telia_ADSL_Bredband">Telia</ulink>, Sweden,
|
||||
dynamic IP.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="https://selfcare.telenordia.se/adsltn/">Telenorida</ulink>,
|
||||
Sweden, dynamic IP.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
</ItemizedList>
|
||||
</Para>
|
||||
|
||||
|
@ -7948,7 +8129,8 @@ LAN Addresses IP Address from ISP pool
|
|||
might also want to look at <Ulink
|
||||
URL="http://www.freesco.org">http://www.freesco.org</Ulink> and <Ulink
|
||||
URL="http://www.coyotelinux.com">http://www.coyotelinux.com</Ulink>. There is
|
||||
also <Ulink URL="http://www.clarkconnect.org/index.html">http://www.clarkconnect.org/index.html</Ulink>, which is a similar concept but designed to be
|
||||
also <Ulink URL="http://www.clarkconnect.org/index.html">http://www.clarkconnect.org/index.html</Ulink>,
|
||||
which is a similar concept but more full-featured and is designed to be
|
||||
monitored and configured with a set of Windows based utilities.
|
||||
|
||||
</Para>
|
||||
|
@ -8077,9 +8259,13 @@ http://www.linuxdude.co.uk/docs/Alcatel-Speedtouch-USB-mini-HOWTO.sgml
|
|||
I think most would agree that the installation of this driver is the more
|
||||
complex of the two, and more than likely will require some patching (unless
|
||||
your distro has already done this). But, it may have some slight performance
|
||||
benefits since it runs mostly in kernel space. There is also the
|
||||
benefits since it runs mostly in kernel space.
|
||||
<!--
|
||||
404
|
||||
There is also the
|
||||
Alcatel-Speedtouch-USB-mini-HOWTO from Chris Jones, <Ulink
|
||||
URL="http://www.linuxdude.co.uk/docs/Alcatel-Speedtouch-USB-mini-HOWTO/">http://www.linuxdude.co.uk/docs/Alcatel-Speedtouch-USB-mini-HOWTO/</Ulink>.
|
||||
-->
|
||||
This driver can potentially support both PPPoE and PPPoA connections.
|
||||
|
||||
</para>
|
||||
|
|
Loading…
Reference in New Issue