1711 lines
40 KiB
HTML
1711 lines
40 KiB
HTML
<HTML
|
||
><HEAD
|
||
><TITLE
|
||
>Appendix: Miscellaneous</TITLE
|
||
><META
|
||
NAME="GENERATOR"
|
||
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
|
||
"><LINK
|
||
REL="HOME"
|
||
TITLE="DSL HOWTO for Linux"
|
||
HREF="index.html"><LINK
|
||
REL="PREVIOUS"
|
||
TITLE="Appendix: FAQ"
|
||
HREF="faq.html"><LINK
|
||
REL="NEXT"
|
||
TITLE="Appendix: The Alcatel SpeedTouch USB ADSL Modem"
|
||
HREF="speedtouchusb.html"></HEAD
|
||
><BODY
|
||
CLASS="SECT1"
|
||
BGCOLOR="#FFFFFF"
|
||
TEXT="#000000"
|
||
LINK="#0000FF"
|
||
VLINK="#840084"
|
||
ALINK="#0000FF"
|
||
><DIV
|
||
CLASS="NAVHEADER"
|
||
><TABLE
|
||
SUMMARY="Header navigation table"
|
||
WIDTH="100%"
|
||
BORDER="0"
|
||
CELLPADDING="0"
|
||
CELLSPACING="0"
|
||
><TR
|
||
><TH
|
||
COLSPAN="3"
|
||
ALIGN="center"
|
||
>DSL HOWTO for Linux</TH
|
||
></TR
|
||
><TR
|
||
><TD
|
||
WIDTH="10%"
|
||
ALIGN="left"
|
||
VALIGN="bottom"
|
||
><A
|
||
HREF="faq.html"
|
||
ACCESSKEY="P"
|
||
>Prev</A
|
||
></TD
|
||
><TD
|
||
WIDTH="80%"
|
||
ALIGN="center"
|
||
VALIGN="bottom"
|
||
></TD
|
||
><TD
|
||
WIDTH="10%"
|
||
ALIGN="right"
|
||
VALIGN="bottom"
|
||
><A
|
||
HREF="speedtouchusb.html"
|
||
ACCESSKEY="N"
|
||
>Next</A
|
||
></TD
|
||
></TR
|
||
></TABLE
|
||
><HR
|
||
ALIGN="LEFT"
|
||
WIDTH="100%"></DIV
|
||
><DIV
|
||
CLASS="SECT1"
|
||
><H1
|
||
CLASS="SECT1"
|
||
><A
|
||
NAME="APPENDIX">8. Appendix: Miscellaneous</H1
|
||
><DIV
|
||
CLASS="SECT2"
|
||
><H2
|
||
CLASS="SECT2"
|
||
><A
|
||
NAME="LINKS">8.1. Links</H2
|
||
><P
|
||
><P
|
||
></P
|
||
><UL
|
||
><LI
|
||
><P
|
||
> Other related documentation from the Linux Documentation Project:
|
||
</P
|
||
><P
|
||
> <P
|
||
></P
|
||
><UL
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/Firewall-HOWTO.html"
|
||
TARGET="_top"
|
||
>Firewall HOWTO</A
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/Security-HOWTO.html"
|
||
TARGET="_top"
|
||
>Security HOWTO</A
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/IPCHAINS-HOWTO.html"
|
||
TARGET="_top"
|
||
>IPCHAINS HOWTO</A
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/IP-Masquerade-HOWTO.html"
|
||
TARGET="_top"
|
||
>IP Masquerade HOWTO</A
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/mini/Home-Network-mini-HOWTO.html"
|
||
TARGET="_top"
|
||
>Home Network mini HOWTO</A
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/Ethernet-HOWTO.html"
|
||
TARGET="_top"
|
||
>Ethernet HOWTO</A
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/Networking-Overview-HOWTO.html"
|
||
TARGET="_top"
|
||
>Networking Overview HOWTO</A
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/Net-HOWTO/"
|
||
TARGET="_top"
|
||
>Net HOWTO</A
|
||
>,
|
||
previously named the NET3-4-HOWTO, the definitive, in-depth guide to
|
||
various Linux networking topics.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/Adv-Routing-HOWTO.html"
|
||
TARGET="_top"
|
||
>Linux
|
||
2.4 Advanced Routing HOWTO</A
|
||
>. All the great features of Linux's
|
||
sophisticated traffic management capabilities are explained here,
|
||
including performance enhancing ideas relevant to DSL.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/mini/DHCP/"
|
||
TARGET="_top"
|
||
>DHCP HOWTO</A
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/VPN-HOWTO.html"
|
||
TARGET="_top"
|
||
>VPN HOWTO</A
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.tldp.org/HOWTO/VPN-Masquerade-HOWTO.html"
|
||
TARGET="_top"
|
||
>VPN Masquerading HOWTO</A
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
></UL
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> More on the 2.4 kernel packet filtering from The Netfilter Project at <A
|
||
HREF="http://netfilter.samba.org/"
|
||
TARGET="_top"
|
||
>http://netfilter.samba.org/</A
|
||
>.
|
||
Several good HOWTOs for the new features available with 2.4 kernels
|
||
and <SPAN
|
||
CLASS="APPLICATION"
|
||
>iptables</SPAN
|
||
>.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> Check your security and see what ports are open at
|
||
<A
|
||
HREF="http://hackerwhacker.com/"
|
||
TARGET="_top"
|
||
>http://hackerwhacker.com/</A
|
||
>. This
|
||
is one of the better sites for this. Some only test a relatively few
|
||
ports.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> SuSE's Linux PPPoE page is at <A
|
||
HREF="http://www.suse.de/~bk/PPPoE-project.html"
|
||
TARGET="_top"
|
||
>http://www.suse.de/~bk/PPPoE-project.html</A
|
||
>.
|
||
Good information on most of the available Linux PPPoE implementations.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> Bob Carrick's definitive PPPoE site is at <A
|
||
HREF="http://www.carricksolutions.com/"
|
||
TARGET="_top"
|
||
>http://www.carricksolutions.com/</A
|
||
>.
|
||
His Linux PPPoE page is at <A
|
||
HREF="http://www.carricksolutions.com/linuxpppoe.htm"
|
||
TARGET="_top"
|
||
>http://www.carricksolutions.com/linuxpppoe.htm</A
|
||
>.
|
||
It has some other DSL related information as well. All OSes are covered.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> The NTS EnterNet for Linux documentation can be found at <A
|
||
HREF="http://support.efficient.com/KB/NTS/Docs/ENLinux13rel.html"
|
||
TARGET="_top"
|
||
> http://support.efficient.com/KB/NTS/Docs/ENLinux13rel.html</A
|
||
>. This is a
|
||
non-GPL'd PPPoE client that is distributed by some ISPs.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> ATM on Linux: <A
|
||
HREF="http://linux-atm.sourceforge.net/"
|
||
TARGET="_top"
|
||
> http://linux-atm.sourceforge.net/</A
|
||
>. Where to find the latest info on
|
||
PPPoA and raw ATM connections.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> FreeSwan, <A
|
||
HREF="http://www.freeswan.org"
|
||
TARGET="_top"
|
||
>http://www.freeswan.org</A
|
||
>, is an
|
||
IPSec and IKE VPN implementation for Linux.
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> VPN and Masquerading on Linux: <A
|
||
HREF="http://www.tldp.org/HOWTO/VPN-Masquerade-HOWTO.html"
|
||
TARGET="_top"
|
||
>http://www.tldp.org/HOWTO/VPN-Masquerade-HOWTO.html</A
|
||
>
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> PPTP-linux allows you to connect to a PPTP server with Linux. The home page is
|
||
<A
|
||
HREF="http://cag.lcs.mit.edu/~cananian/Projects/PPTP/"
|
||
TARGET="_top"
|
||
>http://cag.lcs.mit.edu/~cananian/Projects/PPTP/</A
|
||
>.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> Justin Beech's
|
||
<A
|
||
HREF="http://dslreports.com"
|
||
TARGET="_top"
|
||
>http://dslreports.com</A
|
||
>, a great
|
||
site for anything and everything related to DSL. If it's not there, then
|
||
there is a link to it. (Site runs on Linux.)
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> John Navas's Cable and DSL site, <A
|
||
HREF="http://cable-dsl.home.att.net"
|
||
TARGET="_top"
|
||
>http://cable-dsl.home.att.net</A
|
||
>,
|
||
has good general info, tweaks, troubleshooting, hardware info, etc. for
|
||
all OSes.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> TCP Performance Tuning tips: <A
|
||
HREF="http://www.psc.edu/networking/perf_tune.html"
|
||
TARGET="_top"
|
||
> http://www.psc.edu/networking/perf_tune.html</A
|
||
>. Tips on Linux, and
|
||
other OSes.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> A great Linux security site is <A
|
||
HREF="http://linuxsecurity.com"
|
||
TARGET="_top"
|
||
>http://linuxsecurity.com</A
|
||
>. Good
|
||
docs, and references for Linux. Another is <A
|
||
HREF="http://linux-firewall-tools.com/linux/"
|
||
TARGET="_top"
|
||
> http://linux-firewall-tools.com/linux/</A
|
||
>. Lots of info from Robert
|
||
L. Ziegler, author of <I
|
||
CLASS="CITETITLE"
|
||
>Linux Firewalls</I
|
||
>. Many links
|
||
to other security related sites as well.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.seifried.org/lasg/"
|
||
TARGET="_top"
|
||
> http://www.seifried.org/lasg/</A
|
||
>, The Linux Administrator's
|
||
Security Guide by Kurt Seifried. Good tutorials on a variety of
|
||
topics -- not just firewalls, but the big picture.
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> The Seattle firewall is a packet filtering firewall that can be used on a
|
||
dedicated masquerading firewall machine (including LRP), a multi-function
|
||
masquerade gateway/server or on a stand-alone Linux system. The
|
||
<SPAN
|
||
CLASS="APPLICATION"
|
||
>ipchains</SPAN
|
||
> project is
|
||
located at <A
|
||
HREF="http://seawall.sourceforge.net/"
|
||
TARGET="_top"
|
||
>http://seawall.sourceforge.net/</A
|
||
>.
|
||
And for <SPAN
|
||
CLASS="APPLICATION"
|
||
>iptables</SPAN
|
||
>:
|
||
<A
|
||
HREF="http://shorewall.sourceforge.net/"
|
||
TARGET="_top"
|
||
>http://shorewall.sourceforge.net/</A
|
||
>.
|
||
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> Here a few pages dedicated to using Linux with specific providers. (I
|
||
could use some submissions for more please.)
|
||
</P
|
||
><P
|
||
> <P
|
||
></P
|
||
><UL
|
||
><LI
|
||
><P
|
||
> Verizon:
|
||
<A
|
||
HREF="http://www.panix.com/~dfoster/prog/linux/pppoe.html"
|
||
TARGET="_top"
|
||
> http://www.panix.com/~dfoster/prog/linux/pppoe.html</A
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> Southwestern Bell:
|
||
<A
|
||
HREF="http://home.swbell.net/sdboyd56/DSL/connect1.html"
|
||
TARGET="_top"
|
||
> http://home.swbell.net/sdboyd56/DSL/connect1.html</A
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> BellSouth:
|
||
<A
|
||
HREF="http://personal.bellsouth.net/sdf/h/b/hburgiss/dsl/survival/linux.htm"
|
||
TARGET="_top"
|
||
> http://personal.bellsouth.net/sdf/h/b/hburgiss/dsl/survival/linux.htm</A
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> HomeChoice (UK):
|
||
<A
|
||
HREF="http://www.maxuk.net/hc/faq.html"
|
||
TARGET="_top"
|
||
>http://www.maxuk.net/hc/faq.html</A
|
||
>. (This gets my vote for the strangest ADSL service anywhere.)
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> BT-Internet (UK):
|
||
<A
|
||
HREF="http://www.tldp.org/HOWTO/mini/BTI-PPP/index.html"
|
||
TARGET="_top"
|
||
>http://www.tldp.org/HOWTO/mini/BTI-PPP/index.html</A
|
||
>
|
||
This covers both dial-up and ADSL connections.
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> German T-DSL:
|
||
<A
|
||
HREF="http://www.datenhighway.com/adsl/"
|
||
TARGET="_top"
|
||
>http://www.datenhighway.com/adsl/</A
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> France T<>l<EFBFBD>com's Netissimo:
|
||
<A
|
||
HREF="http://www.rhapsodyk.net/adsl/HOWTO/"
|
||
TARGET="_top"
|
||
>http://www.rhapsodyk.net/adsl/HOWTO/</A
|
||
>. Good information on setting up PPTP with Linux for Alcatel modems.
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> Austrian Highspeed Internetconnection & Linux HOWTO:
|
||
<A
|
||
HREF="http://www.members.aon.at/heimo.schoen/at-highspeed-howto.html"
|
||
TARGET="_top"
|
||
>http://www.members.aon.at/heimo.schoen/at-highspeed-howto.html</A
|
||
>.
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> Israel (various ISPs covered):
|
||
<A
|
||
HREF="http://vipe.technion.ac.il/~mulix/adsl-howto.txt"
|
||
TARGET="_top"
|
||
>http://vipe.technion.ac.il/~mulix/adsl-howto.txt</A
|
||
>
|
||
</P
|
||
></LI
|
||
></UL
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> Now that you have a full-time connection, want a routable hostname for
|
||
your computer? Dynamic DNS services can do this, even if your IP changes from
|
||
time to time. Just a few of the many available services:
|
||
</P
|
||
><P
|
||
> <P
|
||
></P
|
||
><UL
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://dyndns.org"
|
||
TARGET="_top"
|
||
>http://dyndns.org</A
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://tzo.com"
|
||
TARGET="_top"
|
||
>http://tzo.com</A
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.easydns.com"
|
||
TARGET="_top"
|
||
>http://easydns.com</A
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://no-ip.com"
|
||
TARGET="_top"
|
||
>http://no-ip.com</A
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://www.microtech.co.gg/dns"
|
||
TARGET="_top"
|
||
>http://www.microtech.co.gg/dns</A
|
||
>
|
||
</P
|
||
></LI
|
||
></UL
|
||
>
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://conk.com/world/dsl/"
|
||
TARGET="_top"
|
||
>ADSL
|
||
Deployment 'round the World</A
|
||
> Claims to have a complete list -
|
||
looked accurate for my area - gives providers, prices, speeds, etc.
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="http://homepage.interaccess.com/~jkristof/xdsl-faq.txt"
|
||
TARGET="_top"
|
||
>comp.dcom.xdsl
|
||
FAQ</A
|
||
>. Actively maintained, and a great technical reference for DSL
|
||
technologies.
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> <A
|
||
HREF="news://comp.dcom.xdsl"
|
||
TARGET="_top"
|
||
>comp.dcom.xdsl</A
|
||
>, DSL discussions,
|
||
vents, and flames on Usenet. Good place to get technical questions answered
|
||
that your ISP can't.
|
||
</P
|
||
></LI
|
||
></UL
|
||
></P
|
||
></DIV
|
||
><DIV
|
||
CLASS="SECT2"
|
||
><H2
|
||
CLASS="SECT2"
|
||
><A
|
||
NAME="GLOSSARY">8.2. Glossary</H2
|
||
><P
|
||
> A dictionary of some of the jargon used in this Document, and in the
|
||
telco and DSL industries.</P
|
||
><P
|
||
><P
|
||
></P
|
||
><DIV
|
||
CLASS="VARIABLELIST"
|
||
><DL
|
||
><DT
|
||
>ADSL</DT
|
||
><DD
|
||
><P
|
||
> Asymmetric Digital Subscriber Loop. <SPAN
|
||
CLASS="QUOTE"
|
||
>"Asymmetric"</SPAN
|
||
> in that the
|
||
downstream potential is greater than the upstream. ADSL is capable of
|
||
sharing on a single telco wire pair. Maximum speed is 8 Mbps, though
|
||
typically is limited by the provider to lesser speeds. The most popular
|
||
DSL at this time.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>ANT</DT
|
||
><DD
|
||
><P
|
||
> ADSL Network Termination (a.k.a. the ADSL modem).
|
||
</P
|
||
></DD
|
||
><DT
|
||
>ARP</DT
|
||
><DD
|
||
><P
|
||
> Address Resolution Protocol. Converts MAC addresses to IP addresses.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>ASAM</DT
|
||
><DD
|
||
><P
|
||
> Alcatel's terminology for a DSLAM.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>ATM</DT
|
||
><DD
|
||
><P
|
||
> Asynchronous Transfer Mode - provides high-speed packet switching from 155
|
||
Mbps to (currently) 2Gbps. Used to provide backbone switching for the
|
||
Internet, and by many telcos since it can carry both voice and data. This
|
||
is a common transport protocol for many telco DSL networks.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>ATMF-25Mbps</DT
|
||
><DD
|
||
><P
|
||
> ATM Forum Interface - 25Mbps speed, provided by a PCI NIC card. One of the
|
||
interfaces used between the modem and PC.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>brouter</DT
|
||
><DD
|
||
><P
|
||
> A combination DSL modem that can be configured to act as either a bridge
|
||
or a router.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>CAP</DT
|
||
><DD
|
||
><P
|
||
> Carrierless Amplitude Phase. A proprietary ADSL line encoding technique,
|
||
that is (or was) in competition with <SPAN
|
||
CLASS="QUOTE"
|
||
>"DMT"</SPAN
|
||
>. DMT has won the
|
||
standards battle. CAP and DMT modems are not compatible with each other.
|
||
|
||
</P
|
||
></DD
|
||
><DT
|
||
>Central Office, or CO</DT
|
||
><DD
|
||
><P
|
||
> Usually refers to one of two meanings: 1) The local Telco building that
|
||
houses telephone equipment, and where local loops terminate. 2) The Telco
|
||
voice switch that provides dial tone. Often referred to as just
|
||
<SPAN
|
||
CLASS="QUOTE"
|
||
>"CO"</SPAN
|
||
>. Typically, the CO houses one or more DSLAMs that
|
||
make DSL possible. But, increasingly, DSLAMs are being deployed remotely.
|
||
|
||
</P
|
||
></DD
|
||
><DT
|
||
>CLEC</DT
|
||
><DD
|
||
><P
|
||
> Competitive Local Exchange Carrier. <SPAN
|
||
CLASS="QUOTE"
|
||
>"Competitors"</SPAN
|
||
> to the
|
||
ILECs. They do not own any lines, and must lease their lines from ILEC in
|
||
order to provide any service.
|
||
|
||
</P
|
||
></DD
|
||
><DT
|
||
>CPE</DT
|
||
><DD
|
||
><P
|
||
> Customer Premises Equipment - The Telco term for customer owned equipment
|
||
(i.e. the stuff you are responsible for fixing). Examples are analog
|
||
modems, fax machines, and your telephone.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>DHCP</DT
|
||
><DD
|
||
><P
|
||
> Dynamic Host Configuration Protocol - A protocol used to distribute
|
||
dynamically assigned IP addresses and other important networking
|
||
parameters. The DHCP server <SPAN
|
||
CLASS="QUOTE"
|
||
>"leases"</SPAN
|
||
> an IP from its pool to
|
||
clients on request. The lease is renewed at regular intervals. This is a
|
||
common protocol on bridged DSL networks, and cable modem networks.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>DMT</DT
|
||
><DD
|
||
><P
|
||
> Discrete Multitone Technology. This is a line encoding common among ADSL
|
||
deployments, and now is the standard. Sometimes referred to as
|
||
<SPAN
|
||
CLASS="QUOTE"
|
||
>"Alcatel compatible"</SPAN
|
||
>. Most telcos in the U.S. are now
|
||
standardizing on DMT. The other, less common, ADSL encoding is
|
||
<SPAN
|
||
CLASS="QUOTE"
|
||
>"CAP"</SPAN
|
||
>. CAP and DMT modems are incompatible with each other.
|
||
|
||
</P
|
||
></DD
|
||
><DT
|
||
>DS0</DT
|
||
><DD
|
||
><P
|
||
> The basic digital circuit for Telcos - offered at 56 Kbps or 64 Kbps. Can
|
||
support one analog voice channel.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>DSLAM</DT
|
||
><DD
|
||
><P
|
||
> Digital Subscriber Loop Access Multiplexer - The Telco equipment installed
|
||
at the CO that concentrates and multiplexes the DSL lines. One end of the
|
||
copper loop connects to the DSLAM, the other to your modem. The DSLAM
|
||
is essentially what makes DSL work. Increasingly, smaller devices that
|
||
perform similar functions, are being deployed in remote locations in order
|
||
to extend the reach of DSL.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>DSL</DT
|
||
><DD
|
||
><P
|
||
> Digital Subscriber Loop - A term describing a family of
|
||
DSL services, including ADSL, SDSL, IDSL, RADSL, HDSL, VDSL, SHDSL, etc.
|
||
that enable high speed Internet connections over standard copper
|
||
telephone lines. The main limitation is distance.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>G.DMT</DT
|
||
><DD
|
||
><P
|
||
> Synonymous with <SPAN
|
||
CLASS="QUOTE"
|
||
>"full rate"</SPAN
|
||
> ADSL. Used to distinguish between
|
||
full rate ADSL, CAP based ADSL and G.Lite. See <A
|
||
HREF="overview.html#FAMILY"
|
||
>DSL
|
||
Family</A
|
||
> for more.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>G.Lite</DT
|
||
><DD
|
||
><P
|
||
> A lesser version of ADSL that has lower maximum speeds, and requires no
|
||
splitter or filters. Not DMT compatible. See <A
|
||
HREF="overview.html#FAMILY"
|
||
>DSL
|
||
Family</A
|
||
> in this HOWTO for more. </P
|
||
></DD
|
||
><DT
|
||
>HDSL</DT
|
||
><DD
|
||
><P
|
||
> High bit rate DSL. See <A
|
||
HREF="overview.html#FAMILY"
|
||
>DSL Family</A
|
||
> in
|
||
this HOWTO for more.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>ILEC</DT
|
||
><DD
|
||
><P
|
||
> 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 independents like Covad to
|
||
offer competitive services. This is a good thing for consumers IMHO.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>Interleaving</DT
|
||
><DD
|
||
><P
|
||
> Interleaving is a tunable aspect of DMT/ADSL line encoding. It essential
|
||
controls the 'interleaving' of bits in the transmission, and is used
|
||
as a form of error correction. As interleaving increases, so does
|
||
stability of marginal lines. It also increases latency.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>IP</DT
|
||
><DD
|
||
><P
|
||
> Internet Protocol. Also, often used to simply refer to an IP address.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>ISP</DT
|
||
><DD
|
||
><P
|
||
> Internet Service Provider. Even full-time connections require an ISP to
|
||
provide basic Internet services and connectivity.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>LAN</DT
|
||
><DD
|
||
><P
|
||
> Local Area Network. A network of computers that are segregated from the
|
||
WAN (Wide Area Network, i.e. the Internet). Often using private,
|
||
non-routable IP addressing, e.g. 192.168.1.1 or 10.0.0.1.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>LCP</DT
|
||
><DD
|
||
><P
|
||
> Link Control Protocol, one of the sub-protocols used by PPP, and
|
||
derivative protocols like PPPoE. As the name sounds, it used by
|
||
both the client and server to determine if the connection is
|
||
viable. Either end may terminate the session if LCP indicates
|
||
the connection is not responsive.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>Loop</DT
|
||
><DD
|
||
><P
|
||
> The two wire twisted pair from the telco Central Office that terminates at
|
||
a customer location. For DSL, a <SPAN
|
||
CLASS="QUOTE"
|
||
>"clean"</SPAN
|
||
> copper loop within
|
||
the distance limitations is required.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>MAC Address</DT
|
||
><DD
|
||
><P
|
||
> Media Access Control Address. Sometimes also called
|
||
<SPAN
|
||
CLASS="QUOTE"
|
||
>"hardware"</SPAN
|
||
> address, it is a unique identifier of network
|
||
devices and is an important aspect of some network environments.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>mini-RAM</DT
|
||
><DD
|
||
><P
|
||
> Remote Access Multiplexer, a mini DSLAM. Typically with very few
|
||
connections -- eight is common. Used for remote areas too far from a CO.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>MTU</DT
|
||
><DD
|
||
><P
|
||
> Maximum Transmission Unit, the largest packet size, measured in bytes,
|
||
that a network can transmit. Any packets larger than the MTU are divided
|
||
into smaller packets, or <SPAN
|
||
CLASS="QUOTE"
|
||
>"fragmented"</SPAN
|
||
>, before being transmitted.
|
||
|
||
</P
|
||
></DD
|
||
><DT
|
||
>NAT</DT
|
||
><DD
|
||
><P
|
||
> Network Address Translation is a means of allowing computers on a LAN to
|
||
access the WAN while <SPAN
|
||
CLASS="QUOTE"
|
||
>"masquerading"</SPAN
|
||
> with the IP address of a
|
||
host with a suitable address and configuration. With Linux this is called
|
||
<SPAN
|
||
CLASS="QUOTE"
|
||
>"ip-masquerading"</SPAN
|
||
>. Often used to share one public, routable
|
||
IP address among hosts located on a LAN behind a masquerading proxy where
|
||
the local addresses are private and non-routable.
|
||
|
||
</P
|
||
></DD
|
||
><DT
|
||
>NID</DT
|
||
><DD
|
||
><P
|
||
> Network Interface Device - The telco housing on the side of your house.
|
||
Typically where the telco's responsibility ends, and the owner's begins.
|
||
Also, sometimes called the <SPAN
|
||
CLASS="QUOTE"
|
||
>"SNI"</SPAN
|
||
>, <SPAN
|
||
CLASS="QUOTE"
|
||
>"TNI"</SPAN
|
||
> or
|
||
<SPAN
|
||
CLASS="QUOTE"
|
||
>"ONI"</SPAN
|
||
> or other descriptive acronyms.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>NIC</DT
|
||
><DD
|
||
><P
|
||
> Network Interface Card - An internal PC card that supports the
|
||
required network interface. Often an ethernet 10/100baseT or an
|
||
ATMF-25Mbps card in this context.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>NSP</DT
|
||
><DD
|
||
><P
|
||
> Network Service Provider. An ISP's upstream provider or backbone
|
||
provider.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>OC-3</DT
|
||
><DD
|
||
><P
|
||
> A fiber optic line capable of 155 Mbps.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>POTS</DT
|
||
><DD
|
||
><P
|
||
> Plain Old Telephone Service - The service that provides a single analog
|
||
voice line (i.e. a traditional phone line).
|
||
</P
|
||
></DD
|
||
><DT
|
||
>PPPoA (PPPoATM)</DT
|
||
><DD
|
||
><P
|
||
> Point-to-Point Protocol over ATM (RFC 2364) is one of the PPP
|
||
protocols being used by some DSL providers. This is really a device
|
||
specific driver, and in many respects quite different from PPPoE. A
|
||
hardware device, i.e. a combination modem/router, is one alternative if
|
||
this is the only option available to you.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>PPPoE</DT
|
||
><DD
|
||
><P
|
||
> Point-to-Point Protocol over Ethernet (RFC 2516). Another PPP protocol in
|
||
use by providers. This one is more common, and there are several Linux
|
||
clients available. See the <A
|
||
HREF="appendix.html#LINKS"
|
||
>Links section</A
|
||
> for
|
||
more. Not to be confused with PPPoA (PPPoATM) since there are fundamental
|
||
differences.
|
||
|
||
</P
|
||
></DD
|
||
><DT
|
||
>PPPoX</DT
|
||
><DD
|
||
><P
|
||
> Used to refer to PPPoE and PPPoA collectively.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>RADSL</DT
|
||
><DD
|
||
><P
|
||
> Rate Adaptive DSL. See <A
|
||
HREF="overview.html#FAMILY"
|
||
>DSL Family</A
|
||
> in
|
||
this HOWTO for more.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>RBOC</DT
|
||
><DD
|
||
><P
|
||
> Regional Bell Operating Company. The <SPAN
|
||
CLASS="QUOTE"
|
||
>"Baby Bells"</SPAN
|
||
>. The U.S.
|
||
phone companies that have had a state sponsored monopoly since the break
|
||
up of AT&T.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>RFI</DT
|
||
><DD
|
||
><P
|
||
> Radio Frequency Interference. DSL is susceptible to RFI if in the right
|
||
frequency range, and if close enough to the DSL signal. This can
|
||
disrupt and consequently degrade the DSL signal. Unfortunately, DSL
|
||
seems to operate in the frequency range of quite a few potential
|
||
disrupting influences.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>RWIN</DT
|
||
><DD
|
||
><P
|
||
> Shorthand for 'Receive Window', aka the TCP Receive Window, a tunable
|
||
aspect of TCP network stacks.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>SDSL</DT
|
||
><DD
|
||
><P
|
||
> Single Line DSL. Or, sometimes also <SPAN
|
||
CLASS="QUOTE"
|
||
>"Symmetric DSL"</SPAN
|
||
>.
|
||
See <A
|
||
HREF="overview.html#FAMILY"
|
||
>DSL Family</A
|
||
> for more.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>SNI</DT
|
||
><DD
|
||
><P
|
||
> Subscriber Network Interface - The Telco term for the phone wiring housing
|
||
on the side of your house. It designates the point between the Telco side
|
||
and the Inside Wire. This is also called the Demarcation Point. Sometimes
|
||
called a <SPAN
|
||
CLASS="QUOTE"
|
||
>"NID"</SPAN
|
||
> also.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>Splitter</DT
|
||
><DD
|
||
><P
|
||
> The passive device (low-pass filter) at or near the NID that
|
||
splits the DSL signal into separate voice and data channels. Filtering is
|
||
required for most DSLs that share a regular voice phone line (whether POTS
|
||
or ISDN).
|
||
</P
|
||
></DD
|
||
><DT
|
||
>Splitterless</DT
|
||
><DD
|
||
><P
|
||
> A DSL installation that does not require a splitter. For higher
|
||
speeds, a RJ11 filter (sometimes called microfilters) is placed on every
|
||
extension phone jack where an analog phone or other non-DSL device is
|
||
used, thus filtering the DSL signal at the jack, rather than at the
|
||
NID. For lower speeds, no filter is necessary. Without a filter or
|
||
splitter, the DSL signal tends to cause audible interference on voice
|
||
phones. G.Lite needs no splitter, nor filter, but this is the exception to
|
||
the rule.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>SOHO</DT
|
||
><DD
|
||
><P
|
||
> Small Office HOme
|
||
</P
|
||
></DD
|
||
><DT
|
||
>Sync Rate</DT
|
||
><DD
|
||
><P
|
||
> The speed as negotiated by the DSL modem and the telco's DSLAM. This
|
||
represents the theoretical maximum speed of the connection before any
|
||
networking protocol overhead is taken into account. Real world throughput
|
||
is always something less than the modem's sync rate.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>T-DSL</DT
|
||
><DD
|
||
><P
|
||
> German Telekom's ADSL implementation. See <A
|
||
HREF="overview.html#FAMILY"
|
||
>DSL
|
||
Family</A
|
||
> for more.
|
||
|
||
</P
|
||
></DD
|
||
><DT
|
||
>T1</DT
|
||
><DD
|
||
><P
|
||
> a.k.a DS1 - A digital dedicated line at 1.544 Mbps comprised of 24
|
||
channels, used for both voice (24 DS0s) and data.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>T3</DT
|
||
><DD
|
||
><P
|
||
> a.k.a DS3 - T1's big brother, a digital dedicated line at 44.736 Mbps,
|
||
used for both voice (672 DS0s or 28 DS1s) and data.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>VPI/VCI</DT
|
||
><DD
|
||
><P
|
||
> VPI is <SPAN
|
||
CLASS="QUOTE"
|
||
>"Virtual PATH Identifier"</SPAN
|
||
> and is part of an ATM
|
||
cell header. VCI is <SPAN
|
||
CLASS="QUOTE"
|
||
>"Virtual Circuit Identifier"</SPAN
|
||
>, also part of
|
||
an ATM cell header which contains circuit information. Technically
|
||
speaking, these are really remote VPI and VCI (RVPI, RVCI). They are both
|
||
important configuration aspects for modems and routers attached to ATM
|
||
networks. They must match what the provider is
|
||
using. Frequently used VPI/VCI pairs include 0/32, 0/35 and 8/35.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>VDSL</DT
|
||
><DD
|
||
><P
|
||
> Very high bit rate DSL. See <A
|
||
HREF="overview.html#FAMILY"
|
||
>DSL Family</A
|
||
> for
|
||
more.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>VoD</DT
|
||
><DD
|
||
><P
|
||
> Video on Demand.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>VoDSL</DT
|
||
><DD
|
||
><P
|
||
> Voice over DSL.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>WAN</DT
|
||
><DD
|
||
><P
|
||
> Wide Area Network, a large publicly accessible network. For example, the
|
||
Internet.
|
||
</P
|
||
></DD
|
||
><DT
|
||
>xDSL</DT
|
||
><DD
|
||
><P
|
||
> Used to refer to the entire DSL family of related technologies: ADSL,
|
||
SDSL, IDSL, etc.
|
||
</P
|
||
></DD
|
||
></DL
|
||
></DIV
|
||
></P
|
||
></DIV
|
||
><DIV
|
||
CLASS="SECT2"
|
||
><H2
|
||
CLASS="SECT2"
|
||
><A
|
||
NAME="AEN1750">8.3. Other Consumer Class High Speed Services</H2
|
||
><DIV
|
||
CLASS="SECT3"
|
||
><H3
|
||
CLASS="SECT3"
|
||
><A
|
||
NAME="CABLE">8.3.1. Cable Modem vs DSL</H3
|
||
><P
|
||
> The Telcos see DSL as a competitor to the Cable Company's Cable
|
||
Modem, and as such, are providing competitive pricing and configuration
|
||
offerings. Although Cable Modems are advertised as having 10-30Mbps potential
|
||
bandwidth, they use a shared transmission medium with many other users on the
|
||
same line, and therefore performance may vary, sometimes greatly, with the amount
|
||
of traffic, time of day, and number of other users on the same node. But YMMV. </P
|
||
><P
|
||
> It is often heard that DSL has an advantage in that it is a private pipe to
|
||
the Internet, with dedicated bandwidth. This is mostly a myth. You do have a
|
||
private pipe to the DSLAM, but at that point, you enter the telco's ATM (or
|
||
frame relay) network, and start sharing bandwidth. You are at the mercy of
|
||
how well your DSL provider and ISP manage their networks. The consensus seems
|
||
to be that DSL providers and ISPs are mostly doing a better job of managing
|
||
bandwidth than the Cable companies. It is easier for them to add and adjust
|
||
bandwidth as needed to meet demand. You are less likely to have speed
|
||
fluctuations due to other users being on line at the same time. But, again,
|
||
this gets down to how well the specific network and bandwidth are managed. </P
|
||
><P
|
||
> DSL probably has a small security advantage too. With most Cable modem
|
||
networks, it is like being on a big LAN. You are sharing your connection (and
|
||
bandwidth) right at the point of connection. But if you are not doing
|
||
something to filter incoming connections already, you are asking for trouble
|
||
either way. And, the cable companies are addressing this now, with more
|
||
secure approaches. This should not now be a major deciding factor.</P
|
||
><P
|
||
> There also seems to be a better chance of having ISP alternatives with DSL
|
||
than Cable. At least, in the U.S. this is true. Choice is a good thing, and
|
||
so is competition. It seems most Cable outfits give you just one choice for
|
||
an ISP. If you don't like it, you are out of luck. The number of options with
|
||
DSL probably varies greatly by geographic areas. Populous areas, like
|
||
Northeast U.S., seem to have many options. </P
|
||
><P
|
||
> So which is better? The differences aren't as much with the technology, as they
|
||
are with the implementations. If you look around, you can find plenty of
|
||
horror stories on either. And plenty of happy customers too. The way
|
||
to know what may be the best for you, is to do comparative shopping based on
|
||
experiences of other users in your area. Don't base your choice on one
|
||
person's opinion. This is statistically invalid. Likewise, don't base your
|
||
choice on someone's opinion who has had a particular service for only a short
|
||
time. Again, statistically not worth much. Get as many opinions from those
|
||
that are using the <EM
|
||
>exact same services</EM
|
||
> that you are
|
||
looking at.
|
||
</P
|
||
></DIV
|
||
><DIV
|
||
CLASS="SECT3"
|
||
><H3
|
||
CLASS="SECT3"
|
||
><A
|
||
NAME="AEN1760">8.3.2. Fiber in the Loop (IFITL or FTTC, and FTTH)</H3
|
||
><P
|
||
> In some areas, newer neighborhoods are being built with fiber optic cable
|
||
instead of the traditional telco copper lines. While the fiber is a definite
|
||
problem for DSL services, it has it's own potential advantages. Existing
|
||
fiber is potentially capable of 100 Mbps, and it looks like this could easily
|
||
go up soon.
|
||
</P
|
||
><P
|
||
> So while telco fiber customers are being shut out of the DSL market
|
||
(since DSL is a copper only technology), they may have much to look forward
|
||
to. Technologies are under development, and in some cases just now being
|
||
deployed, to take advantage of fiber telco phone loops. Known as
|
||
<SPAN
|
||
CLASS="QUOTE"
|
||
>"FTTC"</SPAN
|
||
> (Fiber To The Curb), or <SPAN
|
||
CLASS="QUOTE"
|
||
>"IFITL"</SPAN
|
||
> (Integrated
|
||
Fiber In The Loop), this technology is another high speed service that telcos
|
||
can offer. The speeds are sufficient for VoD (Video on Demand) and VoDSL
|
||
(Voice over DSL), and other high bandwidth services. One nice advantage here
|
||
is, that since there is no DSL signal on the wire, the only required CPE is a
|
||
network card. In other words, no modem -- just connect a NIC to the wall jack
|
||
and off you go! This will also allow the telco to provide other digital
|
||
services such digital TV. </P
|
||
><P
|
||
> FTTC is Fiber To The Curb. The last leg into the house is still copper. FTTH
|
||
(Fiber To The Home), on the other hand, is an all fiber loop with even higher
|
||
potential. </P
|
||
></DIV
|
||
><DIV
|
||
CLASS="SECT3"
|
||
><H3
|
||
CLASS="SECT3"
|
||
><A
|
||
NAME="AEN1767">8.3.3. Wireless</H3
|
||
><P
|
||
> There is a lot of buzz about wireless technologies these days. Wireless would
|
||
certainly seem to have a place in the broadband market, especially for areas
|
||
that don't have ready access to cable or telco networks. There are still
|
||
some inherent problems with the current state of this technology that may prevent
|
||
it from becoming a major player in the near term however. Weather can still
|
||
impact the wireless signal -- heavy cloud cover or rain for instance. Also,
|
||
there is some pretty hefty latency if the uplink is via satellite. Surely
|
||
these drawbacks will improve over time. But how soon?
|
||
</P
|
||
></DIV
|
||
></DIV
|
||
><DIV
|
||
CLASS="SECT2"
|
||
><H2
|
||
CLASS="SECT2"
|
||
><A
|
||
NAME="MODEMS">8.4. Compatible Modems</H2
|
||
><P
|
||
> This list is limited to those modems and delivery systems that are readily
|
||
available, and should work with any current Linux distribution without having
|
||
to go to extraordinary lengths. Alpha and Beta projects are not included. All
|
||
modems listed are POTS (analog) modems at this time.
|
||
</P
|
||
><H1
|
||
CLASS="BRIDGEHEAD"
|
||
><A
|
||
NAME="AEN1773">Ethernet Interface</H1
|
||
><P
|
||
> <P
|
||
></P
|
||
><UL
|
||
><LI
|
||
><P
|
||
>
|
||
<EM
|
||
>All</EM
|
||
> external, ethernet based modems, and modem
|
||
combination devices, will work (provided they match the provider's DSL).
|
||
The only requirement is a compatible ethernet network card. This is the
|
||
preferred way to go.
|
||
|
||
</P
|
||
></LI
|
||
></UL
|
||
></P
|
||
><H1
|
||
CLASS="BRIDGEHEAD"
|
||
><A
|
||
NAME="AEN1779">PCI (Internal)</H1
|
||
><P
|
||
> <P
|
||
></P
|
||
><UL
|
||
><LI
|
||
><P
|
||
>
|
||
Xpeed X200 IDSL <A
|
||
HREF="http://www.xpeed.com/Products/x200/x200_c.html"
|
||
TARGET="_top"
|
||
>http://www.xpeed.com/Products/x200/x200_c.html</A
|
||
> (as of kernel 2.2.18)
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
>
|
||
Xpeed X300 SDSL <A
|
||
HREF="http://www.xpeed.com/Products/x300/x300_c.html"
|
||
TARGET="_top"
|
||
>http://www.xpeed.com/Products/x300/x300_c.html</A
|
||
> (as of kernel 2.2.18)
|
||
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> IteX PCI ADSL modem based on the Apollo chipset, also sold under various
|
||
other brand names such as Dlink and ALH110. <A
|
||
HREF="http://www.itexinc.com/"
|
||
TARGET="_top"
|
||
>http://www.itexinc.com/</A
|
||
>.
|
||
</P
|
||
></LI
|
||
></UL
|
||
></P
|
||
><H1
|
||
CLASS="BRIDGEHEAD"
|
||
><A
|
||
NAME="AEN1791">USB</H1
|
||
><P
|
||
> <P
|
||
></P
|
||
><UL
|
||
><LI
|
||
><P
|
||
> Alcatel SpeedTouch USB (ADSL):
|
||
<A
|
||
HREF="http://www.speedtouchdsl.com/support.htm"
|
||
TARGET="_top"
|
||
>http://www.speedtouchdsl.com/support.htm</A
|
||
>.
|
||
The driver is kernel module and requires a 2.4 kernel. See the <A
|
||
HREF="speedtouchusb.html"
|
||
>Appendix</A
|
||
> for driver information.
|
||
</P
|
||
></LI
|
||
><LI
|
||
><P
|
||
> Eci Hi Focus ADSL Modem:
|
||
<A
|
||
HREF="http://eciadsl.sourceforge.net/"
|
||
TARGET="_top"
|
||
>http://eciadsl.sourceforge.net/</A
|
||
>. This project
|
||
seems to support several modems and chipsets, including ez-usb an2131qc,
|
||
gs7070 and gt3180.
|
||
</P
|
||
></LI
|
||
></UL
|
||
></P
|
||
></DIV
|
||
><DIV
|
||
CLASS="SECT2"
|
||
><H2
|
||
CLASS="SECT2"
|
||
><A
|
||
NAME="AEN1801">8.5. Setting up Linux as a Router</H2
|
||
><P
|
||
> Depending on your local setup, you should consider some other issues. These
|
||
include a firewall setup, and any associated configurations. For my setup,
|
||
shown in Figure 5 below, I use an old i486 machine configured as a
|
||
firewall/router between the DSL connection and the rest of my home network.
|
||
I use private IP addresses on my private LAN subnet, and have configured my
|
||
router to provide IP Masquerading and Firewalling between the LAN and
|
||
WAN connections. </P
|
||
><P
|
||
> See the <A
|
||
HREF="http://www.tldp.org/HOWTO/IP-Masquerade-HOWTO.html"
|
||
TARGET="_top"
|
||
>IP
|
||
Masquerade HOWTO</A
|
||
> , and <A
|
||
HREF="http://www.tldp.org/HOWTO/Firewall-HOWTO.html"
|
||
TARGET="_top"
|
||
>Firewall
|
||
HOWTO</A
|
||
> for more information. For 2.4 kernels see the <A
|
||
HREF="http://www.tldp.org/HOWTO/Adv-Routing-HOWTO.html"
|
||
TARGET="_top"
|
||
>Linux 2.4 Advanced Routing HOWTO</A
|
||
>. My experience is that Linux is more
|
||
flexible and provides superior routing/firewalling performance. It is
|
||
much less expensive than a commercial router -- if you find an old 486 machine
|
||
that you may be using as a doorstop somewhere. There any number of
|
||
brands of <SPAN
|
||
CLASS="QUOTE"
|
||
>"DSL/Cable"</SPAN
|
||
> routers on the market as well. These
|
||
might be the way to go for pure ease of use, but lack the sophistication
|
||
of what Linux can do. </P
|
||
><H3
|
||
CLASS="BRIDGEHEAD"
|
||
><A
|
||
NAME="AEN1809"> Figure 5: A typical SOHO Network Setup </H3
|
||
><P
|
||
> <TT
|
||
CLASS="LITERAL"
|
||
> <P
|
||
CLASS="LITERALLAYOUT"
|
||
><br>
|
||
<br>
|
||
<br>
|
||
<--Private Subnet/LAN-> Linux <-----ISP's Public Subnet----><--inet--><br>
|
||
192.168.1.0<br>
|
||
<br>
|
||
<br>
|
||
X--+ -------- <br>
|
||
| | | -------- (eth0:0)---------<br>
|
||
+--=| Hub/ | | Linux | +------=| DSL |=-DSL-> ISP's<br>
|
||
X-----=|Switch|=-----=| System |=----+ | Modem | Gateway<br>
|
||
+--=| | eth1 |(Router)| eth0 ---------<br>
|
||
| -------- | -------- |<br>
|
||
X--+ | IP_Masq |<br>
|
||
| IP_Firewall |<br>
|
||
| | Gateway |<br>
|
||
| | |<br>
|
||
| V V<br>
|
||
V 192.168.1.1 Dynamic or<br>
|
||
192.168.1.x LAN Gateway Static IP<br>
|
||
LAN Addresses IP Address from ISP pool<br>
|
||
<br>
|
||
<br>
|
||
<br>
|
||
</P
|
||
>
|
||
</TT
|
||
></P
|
||
><P
|
||
> What I did is setup a Linux router (Redhat Linux 5.0 on a i486) with two
|
||
ethernet interfaces. One interface routes to the ISP subnet/gateway (eth0 in
|
||
above example), and the other interface (eth1 above) goes to a hub (or switch)
|
||
and then connects the LAN with private network addresses (e.g. 192.168.1.x).
|
||
Using the private network addresses behind your router/firewall allows some
|
||
additional security because it is not directly addressable from outside. You
|
||
have to explicitly masquerade your private addresses in order to connect to
|
||
the Internet from the LAN. The LAN hosts will access the Internet via the
|
||
second NIC (eth1) in the Linux router. Just set their gateway to the IP
|
||
address of the second NIC, and assign them addresses on the same network. </P
|
||
><P
|
||
> <EM
|
||
>Caution</EM
|
||
> Make sure your kernel is complied
|
||
with IP forwarding and the IP forwarding is turned on. You can check this
|
||
with '<B
|
||
CLASS="COMMAND"
|
||
>cat /proc/sys/net/ipv4/ip_forward</B
|
||
>'. The value is
|
||
<SPAN
|
||
CLASS="QUOTE"
|
||
>"1"</SPAN
|
||
> for on, and <SPAN
|
||
CLASS="QUOTE"
|
||
>"0"</SPAN
|
||
> for off. You can change this
|
||
value by echoing the desired value into this file: </P
|
||
><P
|
||
> <TABLE
|
||
BORDER="1"
|
||
BGCOLOR="#E0E0E0"
|
||
WIDTH="100%"
|
||
><TR
|
||
><TD
|
||
><FONT
|
||
COLOR="#000000"
|
||
><PRE
|
||
CLASS="SCREEN"
|
||
> # echo 1 > /proc/sys/net/ipv4/ip_forward
|
||
|
||
</PRE
|
||
></FONT
|
||
></TD
|
||
></TR
|
||
></TABLE
|
||
></P
|
||
><P
|
||
> You will also need to set up <SPAN
|
||
CLASS="QUOTE"
|
||
>"IP Masquerading"</SPAN
|
||
> on the Linux
|
||
router. Depending on your kernel version, this is done with
|
||
<B
|
||
CLASS="COMMAND"
|
||
>ipfwadm</B
|
||
> (2.0), <B
|
||
CLASS="COMMAND"
|
||
>ipchains</B
|
||
> (2.2), or
|
||
<B
|
||
CLASS="COMMAND"
|
||
>iptables</B
|
||
> (2.4). See the documentation for specifics on
|
||
each. AND -- do not forget to have that firewall set up too!
|
||
</P
|
||
><P
|
||
> There are also several projects that are devoted specifically to using Linux
|
||
as a router, just for this type of situation. These are all-in-one solutions,
|
||
that include security and various other features. Installation and
|
||
configuration, is reportedly very easy. And these will run on very minimal
|
||
hardware -- like a floppy drive only. The best known is <A
|
||
HREF="http://www.linuxrouter.org"
|
||
TARGET="_top"
|
||
>http://www.linuxrouter.org</A
|
||
>. You
|
||
might also want to look at <A
|
||
HREF="http://www.freesco.org"
|
||
TARGET="_top"
|
||
>http://www.freesco.org</A
|
||
> and <A
|
||
HREF="http://www.coyotelinux.com"
|
||
TARGET="_top"
|
||
>http://www.coyotelinux.com</A
|
||
>. There is
|
||
also <A
|
||
HREF="http://www.clarkconnect.org/index.html"
|
||
TARGET="_top"
|
||
>http://www.clarkconnect.org/index.html</A
|
||
>,
|
||
which is a similar concept but more full-featured and is designed to be
|
||
monitored and configured with a set of Windows based utilities. </P
|
||
></DIV
|
||
></DIV
|
||
><DIV
|
||
CLASS="NAVFOOTER"
|
||
><HR
|
||
ALIGN="LEFT"
|
||
WIDTH="100%"><TABLE
|
||
SUMMARY="Footer navigation table"
|
||
WIDTH="100%"
|
||
BORDER="0"
|
||
CELLPADDING="0"
|
||
CELLSPACING="0"
|
||
><TR
|
||
><TD
|
||
WIDTH="33%"
|
||
ALIGN="left"
|
||
VALIGN="top"
|
||
><A
|
||
HREF="faq.html"
|
||
ACCESSKEY="P"
|
||
>Prev</A
|
||
></TD
|
||
><TD
|
||
WIDTH="34%"
|
||
ALIGN="center"
|
||
VALIGN="top"
|
||
><A
|
||
HREF="index.html"
|
||
ACCESSKEY="H"
|
||
>Home</A
|
||
></TD
|
||
><TD
|
||
WIDTH="33%"
|
||
ALIGN="right"
|
||
VALIGN="top"
|
||
><A
|
||
HREF="speedtouchusb.html"
|
||
ACCESSKEY="N"
|
||
>Next</A
|
||
></TD
|
||
></TR
|
||
><TR
|
||
><TD
|
||
WIDTH="33%"
|
||
ALIGN="left"
|
||
VALIGN="top"
|
||
>Appendix: FAQ</TD
|
||
><TD
|
||
WIDTH="34%"
|
||
ALIGN="center"
|
||
VALIGN="top"
|
||
> </TD
|
||
><TD
|
||
WIDTH="33%"
|
||
ALIGN="right"
|
||
VALIGN="top"
|
||
>Appendix: The Alcatel SpeedTouch USB ADSL Modem</TD
|
||
></TR
|
||
></TABLE
|
||
></DIV
|
||
></BODY
|
||
></HTML
|
||
> |