Spelling error corrected.

Changes and update on isdn code now removed from source tree.

submitted by: wlloyd@mpd.ca 	close PR #2047
This commit is contained in:
Wolfram Schneider 1996-12-08 22:24:10 +00:00
parent 4de7c430f6
commit 77a62bfa44

View File

@ -1,12 +1,9 @@
<!-- $Id: isdn.sgml,v 1.5 1996/10/04 22:54:06 wosch Exp $-->
<!-- $Id: isdn.sgml,v 1.6 1996/10/16 12:28:37 max Exp $-->
<!-- The FreeBSD Documentation Project -->
<sect><heading>ISDN<label id="isdn"></heading>
<p><em>Last modicified by &a.wlloyd;</em>.
<p>ISDN for FreeBSD is still largely under developement. Specifically,
there are a lack of drivers for PC ISDN cards.
<p><em>Last modified by &a.wlloyd;</em>.
<p>A good resource for information on ISDN technology and hardware is
<url url="http://alumni.caltech.edu/~dank/isdn/" name="Dan Kegel's
@ -33,15 +30,24 @@ expensive.
<sect1><heading>ISDN Cards</heading>
<p><em>Originally Contribution by &a.hm;.</em>
<p><em>Original Contribution by &a.hm;.</em>
<p>This section is really only relevant to European ISDN users. The
cards supported are not yet(?) availible for North American ISDN
standards.
<p>You should be aware that this code is largely under development.
Specifically, drivers have only been written for two manufacturers
cards.
<p>PC ISDN cards support the full bandwidth of ISDN, 128Kbs. These
cards are often the least expensive type of ISDN equipment.
<p>Under FreeBSD 2.1.0 and 2.1.5, there is early unfinished ISDN code
under /usr/src/gnu/isdn. This code is out of date and should not be
used. If you want to go this route, get the bisdn stuff. This code
has been removed from the main source tree starting with FreeBSD 2.2.
<p>There is the bisdn ISDN package available from
<url url="ftp://ftp.muc.ditec.de/isdn" name="ftp.muc.ditec.de">
supporting FreeBSD 2.1R, FreeBSD-current and NetBSD.
@ -55,12 +61,12 @@ for the EuroISDN (DSS1) and 1TR6 protocols.
<item>Dr. Neuhaus - Niccy 1016
</itemize>
There are several limitations with the bisdn stuff.
Specifically the following features usually associated with ISDN are not
supported.
There are several limitations with the bisdn stuff. Specifically the
following features usually associated with ISDN are not supported.
<itemize>
<item>No PPP support, only raw hdlc. This means you cannot connect to a
some standalone routers, such as a Cisco unit.
<item>No PPP support, only raw hdlc. This means you cannot connect to most
standalone routers.
<item>Bridging Control Protocol not supported.
<item>Multiple cards are not supported.
<item>No bandwidth on demand.
@ -168,7 +174,7 @@ head office network the following setup could be used.
<em>Branch office or Home network</em>
Network is 10 Base T ethernet. Connect router to network cable with
AUI/10bT transciever if necessary.
AUI/10BT transciever, if necessary.
<verb>
---Sun workstation
@ -205,15 +211,16 @@ One large advantage of most routers/bridges is that they allow you to
have 2 SEPERATE INDEPENDANT PPP connections to 2 separate sites at the
SAME time. This is not supported on most TA's, except for
specific(expensive) models that have two serial ports. Do not confuse
this with channel bonding.
this with channel bonding, MPP etc.
This is a very usefull feature for example if you have an dedicated
This can be very usefull feature, for example if you have an dedicated
internet ISDN connection at your office and would like to tap into it,
but don't want to get another ISDN line at work. A router at the office
location can manage a dedicated B channel connection (64Kbs) to the
internet as well as a use the other B channel for anything else,
including dialin or dialout to another location or dynamically bonding
it with the internet connection for more bandwidth.
internet, as well as a use the other B channel for a seperate data connection.
The second B channel can be used for dialin, dialout or dynamically
bond(MPP etc.) with the first B channel for more bandwidth.
An alternate use of this is to connect to 2 different branch offices at
the same time from the same ISDN line at your central office.
<p>An ethernet bridge will also allow you to transmit more than just
IP traffic, you can also send IPX/SPX or whatever other protocols you
use.</p>