wan-router.txt 23 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622
  1. ------------------------------------------------------------------------------
  2. Linux WAN Router Utilities Package
  3. ------------------------------------------------------------------------------
  4. Version 2.2.1
  5. Mar 28, 2001
  6. Author: Nenad Corbic <ncorbic@sangoma.com>
  7. Copyright (c) 1995-2001 Sangoma Technologies Inc.
  8. ------------------------------------------------------------------------------
  9. INTRODUCTION
  10. Wide Area Networks (WANs) are used to interconnect Local Area Networks (LANs)
  11. and/or stand-alone hosts over vast distances with data transfer rates
  12. significantly higher than those achievable with commonly used dial-up
  13. connections.
  14. Usually an external device called `WAN router' sitting on your local network
  15. or connected to your machine's serial port provides physical connection to
  16. WAN. Although router's job may be as simple as taking your local network
  17. traffic, converting it to WAN format and piping it through the WAN link, these
  18. devices are notoriously expensive, with prices as much as 2 - 5 times higher
  19. then the price of a typical PC box.
  20. Alternatively, considering robustness and multitasking capabilities of Linux,
  21. an internal router can be built (most routers use some sort of stripped down
  22. Unix-like operating system anyway). With a number of relatively inexpensive WAN
  23. interface cards available on the market, a perfectly usable router can be
  24. built for less than half a price of an external router. Yet a Linux box
  25. acting as a router can still be used for other purposes, such as fire-walling,
  26. running FTP, WWW or DNS server, etc.
  27. This kernel module introduces the notion of a WAN Link Driver (WLD) to Linux
  28. operating system and provides generic hardware-independent services for such
  29. drivers. Why can existing Linux network device interface not be used for
  30. this purpose? Well, it can. However, there are a few key differences between
  31. a typical network interface (e.g. Ethernet) and a WAN link.
  32. Many WAN protocols, such as X.25 and frame relay, allow for multiple logical
  33. connections (known as `virtual circuits' in X.25 terminology) over a single
  34. physical link. Each such virtual circuit may (and almost always does) lead
  35. to a different geographical location and, therefore, different network. As a
  36. result, it is the virtual circuit, not the physical link, that represents a
  37. route and, therefore, a network interface in Linux terms.
  38. To further complicate things, virtual circuits are usually volatile in nature
  39. (excluding so called `permanent' virtual circuits or PVCs). With almost no
  40. time required to set up and tear down a virtual circuit, it is highly desirable
  41. to implement on-demand connections in order to minimize network charges. So
  42. unlike a typical network driver, the WAN driver must be able to handle multiple
  43. network interfaces and cope as multiple virtual circuits come into existence
  44. and go away dynamically.
  45. Last, but not least, WAN configuration is much more complex than that of say
  46. Ethernet and may well amount to several dozens of parameters. Some of them
  47. are "link-wide" while others are virtual circuit-specific. The same holds
  48. true for WAN statistics which is by far more extensive and extremely useful
  49. when troubleshooting WAN connections. Extending the ifconfig utility to suit
  50. these needs may be possible, but does not seem quite reasonable. Therefore, a
  51. WAN configuration utility and corresponding application programmer's interface
  52. is needed for this purpose.
  53. Most of these problems are taken care of by this module. Its goal is to
  54. provide a user with more-or-less standard look and feel for all WAN devices and
  55. assist a WAN device driver writer by providing common services, such as:
  56. o User-level interface via /proc file system
  57. o Centralized configuration
  58. o Device management (setup, shutdown, etc.)
  59. o Network interface management (dynamic creation/destruction)
  60. o Protocol encapsulation/decapsulation
  61. To ba able to use the Linux WAN Router you will also need a WAN Tools package
  62. available from
  63. ftp.sangoma.com/pub/linux/current_wanpipe/wanpipe-X.Y.Z.tgz
  64. where vX.Y.Z represent the wanpipe version number.
  65. For technical questions and/or comments please e-mail to ncorbic@sangoma.com.
  66. For general inquiries please contact Sangoma Technologies Inc. by
  67. Hotline: 1-800-388-2475 (USA and Canada, toll free)
  68. Phone: (905) 474-1990 ext: 106
  69. Fax: (905) 474-9223
  70. E-mail: dm@sangoma.com (David Mandelstam)
  71. WWW: http://www.sangoma.com
  72. INSTALLATION
  73. Please read the WanpipeForLinux.pdf manual on how to
  74. install the WANPIPE tools and drivers properly.
  75. After installing wanpipe package: /usr/local/wanrouter/doc.
  76. On the ftp.sangoma.com : /linux/current_wanpipe/doc
  77. COPYRIGHT AND LICENSING INFORMATION
  78. This program is free software; you can redistribute it and/or modify it under
  79. the terms of the GNU General Public License as published by the Free Software
  80. Foundation; either version 2, or (at your option) any later version.
  81. This program is distributed in the hope that it will be useful, but WITHOUT
  82. ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
  83. FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
  84. You should have received a copy of the GNU General Public License along with
  85. this program; if not, write to the Free Software Foundation, Inc., 675 Mass
  86. Ave, Cambridge, MA 02139, USA.
  87. ACKNOWLEDGEMENTS
  88. This product is based on the WANPIPE(tm) Multiprotocol WAN Router developed
  89. by Sangoma Technologies Inc. for Linux 2.0.x and 2.2.x. Success of the WANPIPE
  90. together with the next major release of Linux kernel in summer 1996 commanded
  91. adequate changes to the WANPIPE code to take full advantage of new Linux
  92. features.
  93. Instead of continuing developing proprietary interface tied to Sangoma WAN
  94. cards, we decided to separate all hardware-independent code into a separate
  95. module and defined two levels of interfaces - one for user-level applications
  96. and another for kernel-level WAN drivers. WANPIPE is now implemented as a
  97. WAN driver compliant with the WAN Link Driver interface. Also a general
  98. purpose WAN configuration utility and a set of shell scripts was developed to
  99. support WAN router at the user level.
  100. Many useful ideas concerning hardware-independent interface implementation
  101. were given by Mike McLagan <mike.mclagan@linux.org> and his implementation
  102. of the Frame Relay router and drivers for Sangoma cards (dlci/sdla).
  103. With the new implementation of the APIs being incorporated into the WANPIPE,
  104. a special thank goes to Alan Cox in providing insight into BSD sockets.
  105. Special thanks to all the WANPIPE users who performed field-testing, reported
  106. bugs and made valuable comments and suggestions that help us to improve this
  107. product.
  108. NEW IN THIS RELEASE
  109. o Updated the WANCFG utility
  110. Calls the pppconfig to configure the PPPD
  111. for async connections.
  112. o Added the PPPCONFIG utility
  113. Used to configure the PPPD daemon for the
  114. WANPIPE Async PPP and standard serial port.
  115. The wancfg calls the pppconfig to configure
  116. the pppd.
  117. o Fixed the PCI autodetect feature.
  118. The SLOT 0 was used as an autodetect option
  119. however, some high end PC's slot numbers start
  120. from 0.
  121. o This release has been tested with the new backupd
  122. daemon release.
  123. PRODUCT COMPONENTS AND RELATED FILES
  124. /etc: (or user defined)
  125. wanpipe1.conf default router configuration file
  126. /lib/modules/X.Y.Z/misc:
  127. wanrouter.o router kernel loadable module
  128. af_wanpipe.o wanpipe api socket module
  129. /lib/modules/X.Y.Z/net:
  130. sdladrv.o Sangoma SDLA support module
  131. wanpipe.o Sangoma WANPIPE(tm) driver module
  132. /proc/net/wanrouter
  133. Config reads current router configuration
  134. Status reads current router status
  135. {name} reads WAN driver statistics
  136. /usr/sbin:
  137. wanrouter wanrouter start-up script
  138. wanconfig wanrouter configuration utility
  139. sdladump WANPIPE adapter memory dump utility
  140. fpipemon Monitor for Frame Relay
  141. cpipemon Monitor for Cisco HDLC
  142. ppipemon Monitor for PPP
  143. xpipemon Monitor for X25
  144. wpkbdmon WANPIPE keyboard led monitor/debugger
  145. /usr/local/wanrouter:
  146. README this file
  147. COPYING GNU General Public License
  148. Setup installation script
  149. Filelist distribution definition file
  150. wanrouter.rc meta-configuration file
  151. (used by the Setup and wanrouter script)
  152. /usr/local/wanrouter/doc:
  153. wanpipeForLinux.pdf WAN Router User's Manual
  154. /usr/local/wanrouter/patches:
  155. wanrouter-v2213.gz patch for Linux kernels 2.2.11 up to 2.2.13.
  156. wanrouter-v2214.gz patch for Linux kernel 2.2.14.
  157. wanrouter-v2215.gz patch for Linux kernels 2.2.15 to 2.2.17.
  158. wanrouter-v2218.gz patch for Linux kernels 2.2.18 and up.
  159. wanrouter-v240.gz patch for Linux kernel 2.4.0.
  160. wanrouter-v242.gz patch for Linux kernel 2.4.2 and up.
  161. wanrouter-v2034.gz patch for Linux kernel 2.0.34
  162. wanrouter-v2036.gz patch for Linux kernel 2.0.36 and up.
  163. /usr/local/wanrouter/patches/kdrivers:
  164. Sources of the latest WANPIPE device drivers.
  165. These are used to UPGRADE the linux kernel to the newest
  166. version if the kernel source has already been patched with
  167. WANPIPE drivers.
  168. /usr/local/wanrouter/samples:
  169. interface sample interface configuration file
  170. wanpipe1.cpri CHDLC primary port
  171. wanpipe2.csec CHDLC secondary port
  172. wanpipe1.fr Frame Relay protocol
  173. wanpipe1.ppp PPP protocol )
  174. wanpipe1.asy CHDLC ASYNC protocol
  175. wanpipe1.x25 X25 protocol
  176. wanpipe1.stty Sync TTY driver (Used by Kernel PPPD daemon)
  177. wanpipe1.atty Async TTY driver (Used by Kernel PPPD daemon)
  178. wanrouter.rc sample meta-configuration file
  179. /usr/local/wanrouter/util:
  180. * wan-tools utilities source code
  181. /usr/local/wanrouter/api/x25:
  182. * x25 api sample programs.
  183. /usr/local/wanrouter/api/chdlc:
  184. * chdlc api sample programs.
  185. /usr/local/wanrouter/api/fr:
  186. * fr api sample programs.
  187. /usr/local/wanrouter/config/wancfg:
  188. wancfg WANPIPE GUI configuration program.
  189. Creates wanpipe#.conf files.
  190. /usr/local/wanrouter/config/cfgft1:
  191. cfgft1 GUI CSU/DSU configuration program.
  192. /usr/include/linux:
  193. wanrouter.h router API definitions
  194. wanpipe.h WANPIPE API definitions
  195. sdladrv.h SDLA support module API definitions
  196. sdlasfm.h SDLA firmware module definitions
  197. if_wanpipe.h WANPIPE Socket definitions
  198. if_wanpipe_common.h WANPIPE Socket/Driver common definitions.
  199. sdlapci.h WANPIPE PCI definitions
  200. /usr/src/linux/net/wanrouter:
  201. * wanrouter source code
  202. /var/log:
  203. wanrouter wanrouter start-up log (created by the Setup script)
  204. /var/lock: (or /var/lock/subsys for RedHat)
  205. wanrouter wanrouter lock file (created by the Setup script)
  206. /usr/local/wanrouter/firmware:
  207. fr514.sfm Frame relay firmware for Sangoma S508/S514 card
  208. cdual514.sfm Dual Port Cisco HDLC firmware for Sangoma S508/S514 card
  209. ppp514.sfm PPP Firmware for Sangoma S508 and S514 cards
  210. x25_508.sfm X25 Firmware for Sangoma S508 card.
  211. REVISION HISTORY
  212. 1.0.0 December 31, 1996 Initial version
  213. 1.0.1 January 30, 1997 Status and statistics can be read via /proc
  214. filesystem entries.
  215. 1.0.2 April 30, 1997 Added UDP management via monitors.
  216. 1.0.3 June 3, 1997 UDP management for multiple boards using Frame
  217. Relay and PPP
  218. Enabled continuous transmission of Configure
  219. Request Packet for PPP (for 508 only)
  220. Connection Timeout for PPP changed from 900 to 0
  221. Flow Control Problem fixed for Frame Relay
  222. 1.0.4 July 10, 1997 S508/FT1 monitoring capability in fpipemon and
  223. ppipemon utilities.
  224. Configurable TTL for UDP packets.
  225. Multicast and Broadcast IP source addresses are
  226. silently discarded.
  227. 1.0.5 July 28, 1997 Configurable T391,T392,N391,N392,N393 for Frame
  228. Relay in router.conf.
  229. Configurable Memory Address through router.conf
  230. for Frame Relay, PPP and X.25. (commenting this
  231. out enables auto-detection).
  232. Fixed freeing up received buffers using kfree()
  233. for Frame Relay and X.25.
  234. Protect sdla_peek() by calling save_flags(),
  235. cli() and restore_flags().
  236. Changed number of Trace elements from 32 to 20
  237. Added DLCI specific data monitoring in FPIPEMON.
  238. 2.0.0 Nov 07, 1997 Implemented protection of RACE conditions by
  239. critical flags for FRAME RELAY and PPP.
  240. DLCI List interrupt mode implemented.
  241. IPX support in FRAME RELAY and PPP.
  242. IPX Server Support (MARS)
  243. More driver specific stats included in FPIPEMON
  244. and PIPEMON.
  245. 2.0.1 Nov 28, 1997 Bug Fixes for version 2.0.0.
  246. Protection of "enable_irq()" while
  247. "disable_irq()" has been enabled from any other
  248. routine (for Frame Relay, PPP and X25).
  249. Added additional Stats for Fpipemon and Ppipemon
  250. Improved Load Sharing for multiple boards
  251. 2.0.2 Dec 09, 1997 Support for PAP and CHAP for ppp has been
  252. implemented.
  253. 2.0.3 Aug 15, 1998 New release supporting Cisco HDLC, CIR for Frame
  254. relay, Dynamic IP assignment for PPP and Inverse
  255. Arp support for Frame-relay. Man Pages are
  256. included for better support and a new utility
  257. for configuring FT1 cards.
  258. 2.0.4 Dec 09, 1998 Dual Port support for Cisco HDLC.
  259. Support for HDLC (LAPB) API.
  260. Supports BiSync Streaming code for S502E
  261. and S503 cards.
  262. Support for Streaming HDLC API.
  263. Provides a BSD socket interface for
  264. creating applications using BiSync
  265. streaming.
  266. 2.0.5 Aug 04, 1999 CHDLC initializatin bug fix.
  267. PPP interrupt driven driver:
  268. Fix to the PPP line hangup problem.
  269. New PPP firmware
  270. Added comments to the startup SYSTEM ERROR messages
  271. Xpipemon debugging application for the X25 protocol
  272. New USER_MANUAL.txt
  273. Fixed the odd boundary 4byte writes to the board.
  274. BiSync Streaming code has been taken out.
  275. Available as a patch.
  276. Streaming HDLC API has been taken out.
  277. Available as a patch.
  278. 2.0.6 Aug 17, 1999 Increased debugging in statup scripts
  279. Fixed installation bugs from 2.0.5
  280. Kernel patch works for both 2.2.10 and 2.2.11 kernels.
  281. There is no functional difference between the two packages
  282. 2.0.7 Aug 26, 1999 o Merged X25API code into WANPIPE.
  283. o Fixed a memory leak for X25API
  284. o Updated the X25API code for 2.2.X kernels.
  285. o Improved NEM handling.
  286. 2.1.0 Oct 25, 1999 o New code for S514 PCI Card
  287. o New CHDLC and Frame Relay drivers
  288. o PPP and X25 are not supported in this release
  289. 2.1.1 Nov 30, 1999 o PPP support for S514 PCI Cards
  290. 2.1.3 Apr 06, 2000 o Socket based x25api
  291. o Socket based chdlc api
  292. o Socket based fr api
  293. o Dual Port Receive only CHDLC support.
  294. o Asynchronous CHDLC support (Secondary Port)
  295. o cfgft1 GUI csu/dsu configurator
  296. o wancfg GUI configuration file
  297. configurator.
  298. o Architectual directory changes.
  299. beta-2.1.4 Jul 2000 o Dynamic interface configuration:
  300. Network interfaces reflect the state
  301. of protocol layer. If the protocol becomes
  302. disconnected, driver will bring down
  303. the interface. Once the protocol reconnects
  304. the interface will be brought up.
  305. Note: This option is turned off by default.
  306. o Dynamic wanrouter setup using 'wanconfig':
  307. wanconfig utility can be used to
  308. shutdown,restart,start or reconfigure
  309. a virtual circuit dynamically.
  310. Frame Relay: Each DLCI can be:
  311. created,stopped,restarted and reconfigured
  312. dynamically using wanconfig.
  313. ex: wanconfig card wanpipe1 dev wp1_fr16 up
  314. o Wanrouter startup via command line arguments:
  315. wanconfig also supports wanrouter startup via command line
  316. arguments. Thus, there is no need to create a wanpipe#.conf
  317. configuration file.
  318. o Socket based x25api update/bug fixes.
  319. Added support for LCN numbers greater than 255.
  320. Option to pass up modem messages.
  321. Provided a PCI IRQ check, so a single S514
  322. card is guaranteed to have a non-sharing interrupt.
  323. o Fixes to the wancfg utility.
  324. o New FT1 debugging support via *pipemon utilities.
  325. o Frame Relay ARP support Enabled.
  326. beta3-2.1.4 Jul 2000 o X25 M_BIT Problem fix.
  327. o Added the Multi-Port PPP
  328. Updated utilities for the Multi-Port PPP.
  329. 2.1.4 Aut 2000
  330. o In X25API:
  331. Maximum packet an application can send
  332. to the driver has been extended to 4096 bytes.
  333. Fixed the x25 startup bug. Enable
  334. communications only after all interfaces
  335. come up. HIGH SVC/PVC is used to calculate
  336. the number of channels.
  337. Enable protocol only after all interfaces
  338. are enabled.
  339. o Added an extra state to the FT1 config, kernel module.
  340. o Updated the pipemon debuggers.
  341. o Blocked the Multi-Port PPP from running on kernels
  342. 2.2.16 or greater, due to syncppp kernel module
  343. change.
  344. beta1-2.1.5 Nov 15 2000
  345. o Fixed the MultiPort PPP Support for kernels 2.2.16 and above.
  346. 2.2.X kernels only
  347. o Secured the driver UDP debugging calls
  348. - All illegal network debugging calls are reported to
  349. the log.
  350. - Defined a set of allowed commands, all other denied.
  351. o Cpipemon
  352. - Added set FT1 commands to the cpipemon. Thus CSU/DSU
  353. configuration can be performed using cpipemon.
  354. All systems that cannot run cfgft1 GUI utility should
  355. use cpipemon to configure the on board CSU/DSU.
  356. o Keyboard Led Monitor/Debugger
  357. - A new utility /usr/sbin/wpkbdmon uses keyboard leds
  358. to convey operational statistic information of the
  359. Sangoma WANPIPE cards.
  360. NUM_LOCK = Line State (On=connected, Off=disconnected)
  361. CAPS_LOCK = Tx data (On=transmitting, Off=no tx data)
  362. SCROLL_LOCK = Rx data (On=receiving, Off=no rx data
  363. o Hardware probe on module load and dynamic device allocation
  364. - During WANPIPE module load, all Sangoma cards are probed
  365. and found information is printed in the /var/log/messages.
  366. - If no cards are found, the module load fails.
  367. - Appropriate number of devices are dynamically loaded
  368. based on the number of Sangoma cards found.
  369. Note: The kernel configuration option
  370. CONFIG_WANPIPE_CARDS has been taken out.
  371. o Fixed the Frame Relay and Chdlc network interfaces so they are
  372. compatible with libpcap libraries. Meaning, tcpdump, snort,
  373. ethereal, and all other packet sniffers and debuggers work on
  374. all WANPIPE network interfaces.
  375. - Set the network interface encoding type to ARPHRD_PPP.
  376. This tell the sniffers that data obtained from the
  377. network interface is in pure IP format.
  378. Fix for 2.2.X kernels only.
  379. o True interface encoding option for Frame Relay and CHDLC
  380. - The above fix sets the network interface encoding
  381. type to ARPHRD_PPP, however some customers use
  382. the encoding interface type to determine the
  383. protocol running. Therefore, the TURE ENCODING
  384. option will set the interface type back to the
  385. original value.
  386. NOTE: If this option is used with Frame Relay and CHDLC
  387. libpcap library support will be broken.
  388. i.e. tcpdump will not work.
  389. Fix for 2.2.x Kernels only.
  390. o Ethernet Bridgind over Frame Relay
  391. - The Frame Relay bridging has been developed by
  392. Kristian Hoffmann and Mark Wells.
  393. - The Linux kernel bridge is used to send ethernet
  394. data over the frame relay links.
  395. For 2.2.X Kernels only.
  396. o Added extensive 2.0.X support. Most new features of
  397. 2.1.5 for protocols Frame Relay, PPP and CHDLC are
  398. supported under 2.0.X kernels.
  399. beta1-2.2.0 Dec 30 2000
  400. o Updated drivers for 2.4.X kernels.
  401. o Updated drivers for SMP support.
  402. o X25API is now able to share PCI interrupts.
  403. o Took out a general polling routine that was used
  404. only by X25API.
  405. o Added appropriate locks to the dynamic reconfiguration
  406. code.
  407. o Fixed a bug in the keyboard debug monitor.
  408. beta2-2.2.0 Jan 8 2001
  409. o Patches for 2.4.0 kernel
  410. o Patches for 2.2.18 kernel
  411. o Minor updates to PPP and CHLDC drivers.
  412. Note: No functional difference.
  413. beta3-2.2.9 Jan 10 2001
  414. o I missed the 2.2.18 kernel patches in beta2-2.2.0
  415. release. They are included in this release.
  416. Stable Release
  417. 2.2.0 Feb 01 2001
  418. o Bug fix in wancfg GUI configurator.
  419. The edit function didn't work properly.
  420. bata1-2.2.1 Feb 09 2001
  421. o WANPIPE TTY Driver emulation.
  422. Two modes of operation Sync and Async.
  423. Sync: Using the PPPD daemon, kernel SyncPPP layer
  424. and the Wanpipe sync TTY driver: a PPP protocol
  425. connection can be established via Sangoma adapter, over
  426. a T1 leased line.
  427. The 2.4.0 kernel PPP layer supports MULTILINK
  428. protocol, that can be used to bundle any number of Sangoma
  429. adapters (T1 lines) into one, under a single IP address.
  430. Thus, efficiently obtaining multiple T1 throughput.
  431. NOTE: The remote side must also implement MULTILINK PPP
  432. protocol.
  433. Async:Using the PPPD daemon, kernel AsyncPPP layer
  434. and the WANPIPE async TTY driver: a PPP protocol
  435. connection can be established via Sangoma adapter and
  436. a modem, over a telephone line.
  437. Thus, the WANPIPE async TTY driver simulates a serial
  438. TTY driver that would normally be used to interface the
  439. MODEM to the linux kernel.
  440. o WANPIPE PPP Backup Utility
  441. This utility will monitor the state of the PPP T1 line.
  442. In case of failure, a dial up connection will be established
  443. via pppd daemon, ether via a serial tty driver (serial port),
  444. or a WANPIPE async TTY driver (in case serial port is unavailable).
  445. Furthermore, while in dial up mode, the primary PPP T1 link
  446. will be monitored for signs of life.
  447. If the PPP T1 link comes back to life, the dial up connection
  448. will be shutdown and T1 line re-established.
  449. o New Setup installation script.
  450. Option to UPGRADE device drivers if the kernel source has
  451. already been patched with WANPIPE.
  452. Option to COMPILE WANPIPE modules against the currently
  453. running kernel, thus no need for manual kernel and module
  454. re-compilation.
  455. o Updates and Bug Fixes to wancfg utility.
  456. bata2-2.2.1 Feb 20 2001
  457. o Bug fixes to the CHDLC device drivers.
  458. The driver had compilation problems under kernels
  459. 2.2.14 or lower.
  460. o Bug fixes to the Setup installation script.
  461. The device drivers compilation options didn't work
  462. properly.
  463. o Update to the wpbackupd daemon.
  464. Optimized the cross-over times, between the primary
  465. link and the backup dialup.
  466. beta3-2.2.1 Mar 02 2001
  467. o Patches for 2.4.2 kernel.
  468. o Bug fixes to util/ make files.
  469. o Bug fixes to the Setup installation script.
  470. o Took out the backupd support and made it into
  471. as separate package.
  472. beta4-2.2.1 Mar 12 2001
  473. o Fix to the Frame Relay Device driver.
  474. IPSAC sends a packet of zero length
  475. header to the frame relay driver. The
  476. driver tries to push its own 2 byte header
  477. into the packet, which causes the driver to
  478. crash.
  479. o Fix the WANPIPE re-configuration code.
  480. Bug was found by trying to run the cfgft1 while the
  481. interface was already running.
  482. o Updates to cfgft1.
  483. Writes a wanpipe#.cfgft1 configuration file
  484. once the CSU/DSU is configured. This file can
  485. holds the current CSU/DSU configuration.
  486. >>>>>> END OF README <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<