Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Nov 1996 00:22:24 -0500 (EST)
From:      root@tolstoy.mpd.ca
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   docs/2047: isdn.sgml changes
Message-ID:  <199611180522.AAA13450@tolstoy.mpd.ca>
Resent-Message-ID: <199611180530.VAA11720@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         2047
>Category:       docs
>Synopsis:       isdn.sgml changes
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 17 21:30:06 PST 1996
>Last-Modified:
>Originator:     wlloyd@mpd.ca
>Organization:
>Release:        FreeBSD 2.1.5-STABLE i386
>Environment:
FreeBSD 2.2
	

>Description:
isdn.sgml changes
Spelling error corrected.
Changes and update on isdn code now removed from source tree.


	

>How-To-Repeat:

	

>Fix:
	
	


*** isdn.sgml.orig	Sun Oct 20 13:02:04 1996
--- isdn.sgml	Sun Nov 17 23:55:52 1996
***************
*** 3,12 ****
  
  <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>A good resource for information on ISDN technology and hardware is
  <url url="http://alumni.caltech.edu/~dank/isdn/" name="Dan Kegel's
--- 3,9 ----
  
  <sect><heading>ISDN<label id="isdn"></heading>
  
! <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,47 ****
  
  <sect1><heading>ISDN Cards</heading>
  
! <p><em>Originally 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>PC ISDN cards support the full bandwidth of ISDN, 128Kbs.  These
  cards are often the least expensive type of ISDN equipment.  
  
  <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.
--- 30,48 ----
  
  <sect1><heading>ISDN Cards</heading>
  
! <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,66 ****
  <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.
  <itemize>
! <item>No PPP support, only raw hdlc.  This means you cannot connect to a
! some standalone routers, such as a Cisco unit.
  <item>Bridging Control Protocol not supported.
  <item>Multiple cards are not supported.
  <item>No bandwidth on demand.
--- 56,66 ----
  <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.
! 
  <itemize>
! <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,174 ****
  <em>Branch office or Home network</em>
  
  Network is 10 Base T ethernet.  Connect router to network cable with
! AUI/10bT transciever if necessary.
  
  <verb>
  ---Sun workstation     
--- 168,174 ----
  <em>Branch office or Home network</em>
  
  Network is 10 Base T ethernet.  Connect router to network cable with
! AUI/10BT transciever, if necessary.
  
  <verb>
  ---Sun workstation     
***************
*** 205,219 ****
  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 is a 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.
  
- 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.
--- 205,218 ----
  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, MPP etc.
  
! 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 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.
! 
! <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>
  
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611180522.AAA13450>