{"id":28414994,"url":"https://github.com/interlinked1/wanpipe","last_synced_at":"2025-09-12T20:40:58.047Z","repository":{"id":280364144,"uuid":"941740411","full_name":"InterLinked1/wanpipe","owner":"InterLinked1","description":"Git history of wanpipe releases. No patches accepted here, please visit https://github.com/InterLinked1/phreakscript instead","archived":false,"fork":false,"pushed_at":"2025-03-03T01:08:19.000Z","size":43997,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-06-03T21:28:26.962Z","etag":null,"topics":["sangoma"],"latest_commit_sha":null,"homepage":"https://ftp.sangoma.com/linux/current_wanpipe/","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/InterLinked1.png","metadata":{"files":{"readme":"README","changelog":"ChangeLog","contributing":null,"funding":null,"license":"COPYING","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2025-03-03T00:58:21.000Z","updated_at":"2025-03-03T01:12:42.000Z","dependencies_parsed_at":"2025-03-03T02:32:01.670Z","dependency_job_id":null,"html_url":"https://github.com/InterLinked1/wanpipe","commit_stats":null,"previous_names":["interlinked1/wanpipe"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/InterLinked1/wanpipe","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/InterLinked1%2Fwanpipe","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/InterLinked1%2Fwanpipe/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/InterLinked1%2Fwanpipe/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/InterLinked1%2Fwanpipe/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/InterLinked1","download_url":"https://codeload.github.com/InterLinked1/wanpipe/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/InterLinked1%2Fwanpipe/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":274873613,"owners_count":25365824,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-09-12T02:00:09.324Z","response_time":60,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["sangoma"],"created_at":"2025-06-03T12:30:26.612Z","updated_at":"2025-09-12T20:40:58.039Z","avatar_url":"https://github.com/InterLinked1.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"------------------------------------------------------------------------------\nLinux WAN Router Utilities Package\n------------------------------------------------------------------------------\nVersion beta1-2.3.1\nJan 27 2003\nAuthor: Nenad Corbic \u003cncorbic@sangoma.com\u003e\nCopyright (c) 1995-2003 Sangoma Technologies Inc.\n------------------------------------------------------------------------------\n\nINTRODUCTION\n\nWide Area Networks (WANs) are used to interconnect Local Area Networks (LANs)\nand/or stand-alone hosts over vast distances with data transfer rates\nsignificantly higher than those achievable with commonly used dial-up\nconnections.\n\nUsually an external device called `WAN router' sitting on your local network\nor connected to your machine's serial port provides physical connection to\nWAN.  Although router's job may be as simple as taking your local network\ntraffic, converting it to WAN format and piping it through the WAN link, these\ndevices are notoriously expensive, with prices as much as 2 - 5 times higher\nthen the price of a typical PC box.\n\nAlternatively, considering robustness and multitasking capabilities of Linux,\nan internal router can be built (most routers use some sort of stripped down\nUnix-like operating system anyway). With a number of relatively inexpensive WAN\ninterface cards available on the market, a perfectly usable router can be\nbuilt for less than half a price of an external router.  Yet a Linux box\nacting as a router can still be used for other purposes, such as fire-walling,\nrunning FTP, WWW or DNS server, etc.\n\nThis kernel module introduces the notion of a WAN Link Driver (WLD) to Linux\noperating system and provides generic hardware-independent services for such\ndrivers.  Why can existing Linux network device interface not be used for\nthis purpose?  Well, it can.  However, there are a few key differences between\na typical network interface (e.g. Ethernet) and a WAN link.\n\nMany WAN protocols, such as X.25 and frame relay, allow for multiple logical\nconnections (known as `virtual circuits' in X.25 terminology) over a single\nphysical link.  Each such virtual circuit may (and almost always does) lead\nto a different geographical location and, therefore, different network.  As a\nresult, it is the virtual circuit, not the physical link, that represents a\nroute and, therefore, a network interface in Linux terms.\n\nTo further complicate things, virtual circuits are usually volatile in nature\n(excluding so called `permanent' virtual circuits or PVCs).  With almost no\ntime required to set up and tear down a virtual circuit, it is highly desirable\nto implement on-demand connections in order to minimize network charges.  So\nunlike a typical network driver, the WAN driver must be able to handle multiple\nnetwork interfaces and cope as multiple virtual circuits come into existence\nand go away dynamically.\n \nLast, but not least, WAN configuration is much more complex than that of say\nEthernet and may well amount to several dozens of parameters.  Some of them\nare \"link-wide\"  while others are virtual circuit-specific.  The same holds\ntrue for WAN statistics which is by far more extensive and extremely useful\nwhen troubleshooting WAN connections.  Extending the ifconfig utility to suit\nthese needs may be possible, but does not seem quite reasonable.  Therefore, a\nWAN configuration utility and corresponding application programmer's interface\nis needed for this purpose.\n\nMost of these problems are taken care of by this module.  Its goal is to\nprovide a user with more-or-less standard look and feel for all WAN devices and\nassist a WAN device driver writer by providing common services, such as:\n\n o User-level interface via /proc file system\n o Centralized configuration\n o Device management (setup, shutdown, etc.)\n o Network interface management (dynamic creation/destruction)\n o Protocol encapsulation/decapsulation\n\nTo ba able to use the Linux WAN Router you will also need a WAN Tools package\navailable from\n\n\tftp.sangoma.com/pub/linux/current_wanpipe/wanpipe-X.Y.Z.tgz\n\nwhere vX.Y.Z represent the wanpipe version number.\n\nFor technical questions and/or comments please e-mail to ncorbic@sangoma.com.\nFor general inquiries please contact Sangoma Technologies Inc. by\n\n\tHotline:\t1-800-388-2475\t(USA and Canada, toll free)\n\tPhone:\t\t(905) 474-1990  ext: 106\n\tFax:\t\t(905) 474-9223\n\tE-mail:\t\tdm@sangoma.com\t(David Mandelstam)\n\t\t\tncorbic@sangoma.com (Nenad Corbic)\n\tWWW:\t\thttp://www.sangoma.com\n\n\nINSTALLATION\n\nPlease read the README.install on how to \ninstall the WANPIPE tools and drivers properly. \n\n\nAfter installation read README.config on how\nto configure and start wanpipe device.\n\nFor further information refer to the\ndoc/ directory.\n\nftp.sangoma.com/linux/current_wanpipe/doc\n\n\nCOPYRIGHT AND LICENSING INFORMATION\n\nThis program is free software; you can redistribute it and/or modify it under\nthe terms of the GNU General Public License as published by the Free Software\nFoundation; either version 2, or (at your option) any later version.\n\nThis program is distributed in the hope that it will be useful, but WITHOUT\nANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS\nFOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.\n\nYou should have received a copy of the GNU General Public License along with\nthis program; if not, write to the Free Software Foundation, Inc., 675 Mass\nAve, Cambridge, MA 02139, USA.\n\n\n\nACKNOWLEDGEMENTS\n\nThis product is based on the WANPIPE(tm) Multiprotocol WAN Router developed\nby Sangoma Technologies Inc. for Linux 2.0.x and 2.2.x.  Success of the WANPIPE\ntogether with the next major release of Linux kernel in summer 1996 commanded\nadequate changes to the WANPIPE code to take full advantage of new Linux\nfeatures.\n\nInstead of continuing developing proprietary interface tied to Sangoma WAN\ncards, we decided to separate all hardware-independent code into a separate\nmodule and defined two levels of interfaces - one for user-level applications\nand another for kernel-level WAN drivers.  WANPIPE is now implemented as a\nWAN driver compliant with the WAN Link Driver interface.  Also a general\npurpose WAN configuration utility and a set of shell scripts was developed to \nsupport WAN router at the user level.\n\nMany useful ideas concerning hardware-independent interface implementation\nwere given by Mike McLagan \u003cmike.mclagan@linux.org\u003e and his implementation\nof the Frame Relay router and drivers for Sangoma cards (dlci/sdla).\n\nWith the new implementation of the APIs being incorporated into the WANPIPE,\na special thank goes to Alan Cox in providing insight into BSD sockets.\n\nSpecial thanks to all the WANPIPE users who performed field-testing, reported\nbugs and made valuable comments and suggestions that help us to improve this\nproduct.\n\n\to From 2.3.1 contains major structural driver changes.\n\t  The new Hardware Abstraction layer cleanly separates, the\n\t  physical layer from the driver/protocol layers.\n\n\t  Support for 2.6.X kernel.\n\n\to From 2.3.0 contains major structural driver changes \n\t  most notably the ADSL OS abstraction layer. ADLS drivers\n\t  can now be compiled against any custom kernel.\n\n\to From 2.2.6 release forward the new S514-7 Dual T/E1, \n \t  S514-8 Single TE1 and S518 ADSL cards are supproted.\n\n\to From 2.2.4 release forward the new S514-4 T/E1 and S514-5 56K\n          cards are supported.\n   \n\to From 2.2.3 release forward ALL wanpipe modules\n          including API modules, can be recompiled from\n           ./Setup installation script! \n           NO KERNEL RECOMPILATION is necessary.\n           \n\to From 2.2.3 release forward, wanpipe directory\n           architecture has been changed.  New home directory\n           for wanpipe is /etc/wanpipe. \n   \n\to All old releases are in ../old_releases/wanpipe directory. \n\n\to Custom RPMs can be build based on current kernel image\n\t  by using the ./Setup buildrpm command.\n\t  Read the README.rpmbuild.\n\n\n\n\nNEW IN beta1-2.3.1 RELEASE\n===========================\nJan 27 2004\t\n\t\n\to Support for 2.6.X kernels\n\t\n\to New Hardware Abstracion Layer\n\t  Cleanly separates the hardware\n\t  layer from the data/protocol layers.\n\n\to New AFT Hardware Support\n          Sangomas new high-speed T1/E1\n\t  adapters.\n\n\to Bitstrm Update\n\t  New bitstrm SWITCHING on\n\t  serial cards.\n\t\n\t\t\n\t\n2.3.0-8\nJan 15 2004\n\n\to ADSL Update\n          Fixed the lights problem\n\t  where lights turn off after\n\t  training timeout.\n\n\to All Drivers UDP PKT TYPE\n\t  The check for UPD packets function\n\t  has been secured by checking for the\n\t  packet length before proceeding to test\n\t  for udp packet.\n\n\to Wanpipe DEBIAN packager\n          The ./Setup installation script\n\t  can now build DEBIAN packages.\n\n\t  ./Setup builddeb\n\n\to Wanpipe PCAP Tracing\n          wanpipemon trace utility can now\n\t  trace to a PCAP type file, that\n\t  can be read by \"Etheral\" for\n\t  graphical protocol decoding.\n\n\t  wanpipemon -i \u003cifname\u003e -pcap -c tr\n\n\t  for further info run:\n\t  \twanpipemon -traceinfo \u003ccr\u003e\n\n2.3.0-7\nDec 01 2003\n\n\to MAJOR BUG FIX: T1/E1\n\t \n\t  The 2.3.0-6 release had a major T1/E1\n\t  bug!  \n\t  \n\t  NOTE: This bug was only on 2.3.0-6 \n\t        release.\n\n\to Bitstrm Update\n\t  New bitsreaming firmware.\n\n\to X25 Update\n\t\n\t  Added an algorithm to check for\n\t  loss of tx clock.  In such case\n\t  the firmware would not be able to\n\t  transmit.  The API would receive an\n\t  OOB message with packet type 0x0C\n\t  same as the modem down condition.\n\t\n\t  Update x25 firmware\n\n\n2.3.0-6\nNov 24 2003\n\to Bitstrm Update\n\t \n\t  Fixed E1 API.\n\t  New Bitstrm Firmware that fixes and \n\t  monitors the channel slip condition.\n\n\to X25 Update\n          Added front end state. If modem\n\t  goes down, the link state will\n\t  follow.\n\n\t  Fixed the incoming call user data lenght filed.\n\t  The user data length on incoming call would\n\t  always be set, even if there was no user\n\t  data.\n\n\t  Added detailed milisecond timesamps\n\t  to trace packets.\n\n\t  Updated the trace lost counter.\n\t \n\to MPAPI \n\t  Added PVC support to MPAPI X25 stack\n\t  Added the MOD128 X25 support\n\n\to ADSL\n\t  Update the SMP locks\n\t  Fixed a shared interrupt bug.\n\n\to HDLC Firmware Update\n\t  Added FAST_ISR option to the\n\t  CHDLC firmware, for better performance\n\t  when all four ports are running at\n\t  the same time.\n\n2.3.0-5\nOct 7 2003\n\to WPBWM Utility\n\t  Added a bandwidth monitor utility\n\t  to the wanpipe package.  \n\t  Used for real time throughput statistics\n\t  on all running network interfaces.\n\t  \n\to ATM Update\n\t  ATM drivers didn't work over E1 cards.\n\t  Configuration issue.\n\n\to ADSL Update\n\t  ADSL drivers failed to train\n\t  on lines in South Africa. \n\t  Update firmware and minor driver\n\t  bug fixes.\n\n\to BitStreaming Bug Fix\n\t  Problem with bitstreaming over\n\t  S514 (1/2) Serial cards.\n\n\to X25API Update\n\t  Added interrupt based tracing\n\t  this way the trace will not \n\t  drop any packets, even during\n\t  high traffic conditions.\n\n\to Update X25API\n\t  The MTU of 128 was not supported :(\n\n\to PPP over Frame Relay\n\t  Added the PPP protocol support over\n\t  Frame Relay.\n\n\to Setup Update\n\t  Buildrpm option has been fixed for\n\t  RedHat 9.0\n\n\n2.3.0-4\nAug 11 2003\n\to EduKit Driver Update\n\t  Updated ioctl calls\n\n\to Added ss7 headers to the\n\t  release, to resolve the\n\t  ss7pipemon compilation issue.\n\n2.3.0-3\nAug 5 2003\n\to Update to X25API driver\n\t  Fixed the accept() \n          Fixed the reset()\n\t  Fixed the clear_call() \n\t  \n\to Wanpipemon\n\t  New SS7 monitor\n\n\to Setup Update\n\t  \n\t  Fixed the kernel source update.\n\t  Now the wanpipe drivers can be\n\t  compiled inside the kernel tree.\n\n2.3.0-2\nJul 21 2003\n\to Wanpipe Bug Fix\n\t  The test code used in debugging\n\t  was left inside the driver, which\n\t  caused problems when shutting down\n\t  wanpipe.\n\n\n2.3.0-1\nJul 18 2003\n\to New API sockets \n\n\t  The MPAPI sockets have replaced the\n\t  original WANPIPE API sockets.  The\n\t  API interface is 100% backward compatible.\n\n2.3.0-0\nJun 14 2003\n\n\to Wanrouter External Scripts Support\n   \n          The /usr/sbin/wanrouter startup script\n\t  is now able to start external scripts for\n\t  each action performed on WANPIPE devices.\n\n\n\t  Script Location: \n\t\tConfigurable in /etc/wanpipe/wanrouter.rc\n\t\t\n\t\teg:\tWAN_SCRITPS_DIR=/etc/wanpipe/scripts/\n\n\n\t  Interface Start/Stop Scripts:\n\n\t    \u003cdevice name\u003e-\u003cinterface name\u003e-\u003ccmd\u003e\n\n\t    eg: wanpipe1-wan0-start\n\t\twanpipe1-wan0-stop\n\n\n\t    Interfaces scripts will get invoked by the following commands:\n\t    \t\n\t\twanrouter [start|stop|restart]\n\t\twanrouter [start|stop|restart] \u003cdevice\u003e\n\t\twanrouter [start|stop|restart] \u003cdevice\u003e \u003cinterface\u003e\n\t\t\n\t    or  Dynamically by wanpipe syncppp driver after \n\t        successfull IPCP negotiation.\n\n\t\tThis option is extremely useful for PPPoA ADSL\n\t\tor PPP customers, that need to update their \n\t\trouters based on new negotiated IP addresses.\n\n\t  Device Start/Stop Scripts:\n\n\t    \u003cdevice name\u003e-\u003ccmd\u003e\n\n\t    eg: wanpipe1-start\n\t\twanpipe1-stop\n\n\t    Device scripts will get invoked by the following commands:\n\t\twanrouter [start|stop|restart]\n\t\twanrouter [start|stop|restart] \u003cdevice\u003e\n\n\t  Global Start/Stop Scripts:\n\n\t    \u003ccmd\u003e\n\n\t    eg: start\n\t\tstop\n\n\t    Global Wanpipe scripts will get invoked by the following commands:\n\t\twanrouter [start|stop|restart]\n\n\t  Wancfg Configurator Update\n\t    \n\t    The /usr/sbin/wancfg configuration utility has\n\t    been updated to create/edit all external\n\t    global,device,interface scripts.\n\n\n\t  Each script is executed as Bash2 shell script.\n\n\n\to Wancfg Configurator Update\n\t\n\t  The /usr/sbin/wancfg configuration utility has \n\t  been updated to create/edit all external\n\t  global,device,interface scripts.\n\n\n\to New API sockets \n\n\t  The MPAPI sockets have replaced the\n\t  original WANPIPE API sockets.  The\n\t  API interface is 100% backward compatible.\n\n\n\to Wanrouter External Scripts Support\n   \n          The /usr/sbin/wanrouter startup script\n\t  is now able to start external scripts for\n\t  each action performed on WANPIPE devices.\n\n\n\t  Script Location: \n\t\tConfigurable in /etc/wanpipe/wanrouter.rc\n\t\t\n\t\teg:\tWAN_SCRITPS_DIR=/etc/wanpipe/scripts/\n\n\n\t  Interface Start/Stop Scripts:\n\n\t    \u003cdevice name\u003e-\u003cinterface name\u003e-\u003ccmd\u003e\n\n\t    eg: wanpipe1-wan0-start\n\t\twanpipe1-wan0-stop\n\n\n\t    Interfaces scripts will get invoked by the following commands:\n\t    \t\n\t\twanrouter [start|stop|restart]\n\t\twanrouter [start|stop|restart] \u003cdevice\u003e\n\t\twanrouter [start|stop|restart] \u003cdevice\u003e \u003cinterface\u003e\n\t\t\n\t    or  Dynamically by wanpipe syncppp driver after \n\t        successfull IPCP negotiation.\n\n\t\tThis option is extremely useful for PPPoA ADSL\n\t\tor PPP customers, that need to update their \n\t\trouters based on new negotiated IP addresses.\n\n\t  Device Start/Stop Scripts:\n\n\t    \u003cdevice name\u003e-\u003ccmd\u003e\n\n\t    eg: wanpipe1-start\n\t\twanpipe1-stop\n\n\t    Device scripts will get invoked by the following commands:\n\t\twanrouter [start|stop|restart]\n\t\twanrouter [start|stop|restart] \u003cdevice\u003e\n\n\t  Global Start/Stop Scripts:\n\n\t    \u003ccmd\u003e\n\n\t    eg: start\n\t\tstop\n\n\t    Global Wanpipe scripts will get invoked by the following commands:\n\t\twanrouter [start|stop|restart]\n\n\t  Wancfg Configurator Update\n\t    \n\t    The /usr/sbin/wancfg configuration utility has\n\t    been updated to create/edit all external\n\t    global,device,interface scripts.\n\n\n\t  Each script is executed as Bash2 shell script.\n\n\n\to Wancfg Configurator Update\n\t\n\t  The /usr/sbin/wancfg configuration utility has \n\t  been updated to create/edit all external\n\t  global,device,interface scripts.\n\n\n\nbeta7-2.3.0\nMay 22 2003\n\n\to ADCCP Lapb API Protocol\n\t  \n\t  New ADCCP Lapb API protocol for\n\t  S514 and S508 cards.\n\n\t  Read the REAME.adccp for more info.\n\n\to ADSL Update\n  \n          Bug fixes and feature upates to the\n\t  ADSL code.  Including, line watchdog\n\t  and cell delienation fix.\n\n\t  Added a line watchdog feature. New config\n\t  option ADSL_WATCHDOG in wanpipe1.conf.\n\n\t  New PPPoA ppp driver.  No need to use\n\t  the pppd daemon any more.  The whole PPPoA \n\t  configuration is now inside /usr/sbin/wancfg.\n\n          New Interface Config Options:\n\n\t\tDYN_INTR_CFG: Option enables dynamic ppp ip addressing\n\t\tPAP:          Enables pap authentication\n\t\tCHAP:\t      Enables chap authentication\n\t\tUSERID:       User id\n\t\tPASSWD:       User password\n\n\t  Refer to README.adsl for further info.\n\n\to MPAPI X25 Updates and fixes\n\n\to Updated WANPIPE for \n\t  RedHat AS 2.1 distribution.  \n\n\n\nbeta6-2.3.0\nApr 22 2003\n\n\to ATM firmware update\n\t  Beta5 had the ATM wrong firmware version,\n\t  which doesn't work with some ATM switches.\n\n\to Frame Relay bug fix. \n\t  If running beta4-2.3.0 update to the latest\n\t  or enable MULTICASTING in network interface\n\t  protocol setup.\n\n\to ADSL protocol update\n\t  ADSL driver was too sensitive to noisy lines which\n\t  caused it to re-train too often. \n\n\t  ADSL PPPoA has been re-designed.  The PPPD Daemon\n\t  is not used any more.  The Wanpipe PPP kernel stack\n\t  has PAP/CHAP support now.  \n\n\t  Thus whole PPPoA configuration, including PAP/CHAP\n\t  is now handled by the /usr/sbin/wancfg configurator.\n\n \to New SNMP MIBS\n\t  New SNMP MIBS for T1/E1/56 front ends\n\t  Updated original protocol mibs: FR/PPP/CHDLC/X25 ...\n\n\nbeta5-2.3.0\nApr 9 2003\n\n\to New ATM driver for S514(T1/E1) cards\n\n\t  Flexible PHY-layer, supporting all formats of Idle, \n\t  Unassigned and Physical Layer cells.\n\n\t  DS1 direct ATM cell mapping as per ITU G.804 \n\t  Section 2.1.\n\t\n\t  Support for AAL Type 5.\n\n    \t  ATM operations and management (OAM) support.\n\n    \t  Extensive statistics at both the PHY and ATM levels.\n\n    \t  Real-time data scope with advanced cell-filtering \n\t  capabilities.\n\n    \t  Unlimited number of VPI/VCI combinations.\n\n    \t  Encapsulation and protocols supported\n          (IP over ATM, PPP over ATM, and Ethernet over ATM)\n\n\to ADSL driver update\n         \n\t  Major bug fixes in ADSL driver.\n\t  Better retraining algorithm, improved debugging.\n\t  Better performance on noisy lines.\n\n\to Multi-Protocol Driver Support\n\n\t  The Multi Protocol drivers implements HDLC/PPP/CHDLC\n\t  protocols in kernel that run over sangoma dumb\n\t  card support (S514/S508).\n\n          All Multi Protocol drivers can run on each Sangoma\n\t  S514/S508 Primary and Secondary Ports.\n\n\to Multi-Protocol API Support\n\n\t  The Multi Protocol API support runs on top of the\n\t  Multi Protocol drivers.  The MPAPI supports X25/LAPB\n\t  and DSP protocols as kernel modules. \n\n          All Multi Protocol APIs can run on each Sangoma\n\t  S514/S508 Primary and Secondary Ports.\n\n\t  Sample code /etc/wanpipe/api/mpapi/\n\t\n\t  The MPAPI support is not released with standard wanpipe\n\t  release.  It must be downloaded separately.  For\n\t  further info contact Sangoma Technologies.\n\n\to Updated Wanpipe Documentation\n\t  \n\t  New PDF Files: WanpipeInstallation.pdf\n\t                 WanpipeConfiguration.pdf\n\t\t\t WanpipeOperation.pdf\n\t\t\t WanpipeDebugging.pdf\n\t\t\t x25_programming_manual.pdf\n\t\n\t  New README Files:\n\t                 There is a README file for\n\t\t\t each new protocol.\n\n\t\t\t eg: README.atm, README.adsl...\n\n\t\t\t New README.faq\n\n          All README files are in doc/ directory or\n\t  once WANPIPE is installed in /usr/share/doc/wanpipe\n\t  directory.\n\n\to Updated Wanpipe utilites\n\n\n\nbeta4-2.3.0\nFeb 20 2003\n\n\to ATM Protocol support for all S514 (T1/E1/V35) cards.\n\t  \n\t  ATM Protocol includes a full PHY/SAR ATM layer.\n\t  As well as the following ATM Encapsulation Protocols:\n\t  \tEthernet (LLC/VC) over ATM\n\t\tClassical IP (LLC/VC) over ATM\n\n\t  ATM Protocol is part of Default WANPIPE protocols,\n\t  thus it will be compiled by default during\n\t  \t./Setup install\n\n\t  IMPORTANT: \n\t        ATM Protocol is still in beta state and \n\t        there are known bug issues with the ATM\n\t\tfirmware that will be resolved in the\n\t\tnext release.\n\n\to POS (Point of Sale) S509/S515 card support\n\t  The POS adapters support proprietary protocols\n\t  such as: IBM 4680, NCR 2126, NCR 1255\n\n\t  To enable POS card, on installation run:\n\t  \t./Setup install \n\t\t\tEnable POS in Custom compile mode \n\n\t\tor\n\t\t\n\t\t./Setup install --protocol=POS\n\t\t\n\n\to ADSL driver update\n\n\t  Major bug fix in rx data path.\n\t  \tRacing condition between the\n\t\tinterrupt and the rx task.\n\t\t\n\n\to Wanpipe drivers update\n\n\t  Wanpipe Event based line debugging \n\t  \n\t  For Frame Relay, PPP and CHDLC protocols, \n\t  extensive debugging is outputted to the \n\t  logs, in case of  a protocol, line or \n\t  hardware error events.\n\n\to Setup installation script update\n\n\t   When compiling wanpipe drivers two compilation\n\t   options are offered:\n\n\t   Compilaton Options:  Default or Custom\n\n\t   Default compilation: \n\t   \tCompile the standard WANPIPE protocols \n\t\tinto the kernel device driver: Frame Relay, PPP, CHDLC \n\t\tMulti-Port Frame Relay, Multi-Port PPP, and X25(API). \" \n\t\t\n\t   Custom compilation:\n\t        Offer a menu of all available WAN and \n\t\tAPI protocols. The user will be able to enable \n\t\tprotocols individually or all at once, \n\t\tas desired. \n\n\to Bit Streaming Update\n\t\n\t  Fixed bitstreaming for E1 cards.\n\t  New bitstreaming api sample codes in\n\t  /etc/wanpipe/api/bitstrm directory.\n\t\n\nbeta3-2.3.0\nJan 7 2003\n\n\to ADSL Update\n\t  \n\t  Added ATM OAM protocol support\n\t  OAM Cell loopback is used to test the \n\t  functionality of the ATM network before\n\t  the upper layers are enabled.\n\t  i.e. ATM Ping\n\n\t  Added further buffer locking mechanism that\n\t  will further protect buffers on SMP systems.\n\n\to Wanpipemon Update\n\n\t  Added ADSL ATM Cell trace option \n\t  (tl2) to ADSL debugger.\n\t  \n\t  eg: wanpipemon -i \u003cifname\u003e -c tl2\n\n\to Frame Relay memory leak bug fix under\n\t  BRIDGE MODE. If a non ethernet packet was\n\t  received from the remote network, it was\n\t  not properly deallocated. \n\n\t  This condition is very rare but it may occur.\n\n\to Updated ATMARP's for Classical IP over\n\t  ATM protocol.  On startup the Client\n\t  will send out ATMARPS every 10 seconds.\n\t  Refer to RFC2225\n\t\n\to Updated Classical IP over ATM protocol.\n\t  Maximum MTU=9180 bytes.  Specified in RFC2225\n\nbeta2 2.3.0\n\to Bug fix in wanrouter.h header\n           The kernel source compilation failed due to\n           a missing header include file in wanrouter.h \n \n           This has been fixed now.  No other changes\n           except in wanrouter.h.\n\n\to wanpipemon debugger update\n       \n\nbeta1-2.3.0\n\n\to ADSL abstraction layer has been added\n\t  to the main wanpipe source.  Thus, from now\n\t  on ADSL code can be compiled against any\n\t  custom kernel.  \n\n\t  Added new ATM encapsulation modes:\n\n\t  Bridged Ethernet LLC over ATM (PPPoE: requires rp-pppoe)\n\t  Bridged Ethernet VC over ATM\n\t  Routed IP LLC over ATM (Classical IP)\n\t  Routed IP VC over ATM\n\t  PPP LLC over ATM (PPPoA: requires pppd)\n\t  PPP VC over ATM (PPPoA: requires pppd)\n\n\to Wanpipemon GUI update\n\t  Better menu system\n\n\to Major driver updates due to new common\n\t  headers between all protocols and other\n\t  operating systems (FreeBSD, NetBSD). \n\t  \n\nbeta4-2.2.6\n\t\n\to Compilation problems on RedHat 8.0 kernel\n          have been fixed\n\n\nbeta3-2.2.6\n\n\to Turns out that RedHat 8 moved the 2.4.20 feature\n\t  into its 2.4.18 kernel, thus causing the same\n\t  problem.  Thus I had to re-do the fix.\n\n\to Fixed the bug that caused the wanpipe comilation\n\t  errors when drivers were being compiled into\n\t  the kernel. (i.e. not modules)\n\n        The current 2.2.6 RPMS are not affected by this bug, since\n        they were compiled for older kernels (not 2.4.20).\n\n\nbeta2-2.2.6\n\n\to Due to the change in 2.4.20 kernel all wanpipe\n\t  network interfaces failed on startup.\n\t  \t  \n\t  A fix was a one liner, however it had to be\n\t  applied to all protocols.\n\n\nbeta1-2.2.6\n\n\to Support for new hardware:\n\t\tS5147 - Dual T1/E1 card\n\t\tS5148 - T1/E1 card\n\t\tS518  - ADSL card\n\n\to New ADSL drivers\n\t\tEthernet of ATM\t(IPoE and PPPoE) \n\t\tClassical IP of ATM\n\n\to Updated drivers for all protocols\n \t  \n\to A unified debugging tool 'wanpipemon'\n\t  that replaces protocol specific debugging\n\t  tools (fpipemon, cpipemon, xpipemon ...)\n\n\t  GUI support for wanpipemon \n\n\to Update 'wancfg' configuration tool \n\t\n\to Updated documentation\n\n\to Frame Relay Feature\n\t\tAuto DLCI configuration for a single DLCI.\n\t\tThe /usr/sbin/wancfg will offer the auto\n\t\toption if FR is configured for CPE and\n\t\ta Single DLCI.\n\n\to New MultiPort Frame Relay Driver\n\n\t  This new Frame Relay driver can operate on both\n\t  S514/S508 PRIMARY and SECONDARY ports.\n\n\t  Thus, on a single S5141 card one can run CHDLC,\n\t  and FR on each port.\n\n\t  On a S5142 card on can run CHDLC, MPPP and MFR\n\t  protocols on each 4 ports.  \n\n\to SDLC support for Linux\n\t  API for SDLC protocol\n\n\to Update to /usr/sbin/wanrouter\n\n\t \twanrouter debug \n\t\t\tCheck current wanpipe environment.\n                        After a startup error run this command to\n                        get a possible solution\n                        i.e. wanrouter start; wanrouter debug;\n\n        \twanrouter debug if_name\n\t\t\tDisplay common debugging statistics\n                        In case of line problems save to file,\n                        wait 2-5mi and send to Sangoma Tech Support\n                        i.e. wanrouter debug wp1fr16 \u003e debug_file;\n\n        \twanrouter messages\n\t\t\tDisplay wanpipe kernel event messages\n                        i.e. /var/log/messages\n\n        \twanrouter conflog\n\t\t\tDisplay wanpipe configuration parsing messages\n                        i.e. /var/log/wanrouter\n\n\n\n\nPRODUCT COMPONENTS AND RELATED FILES\n\n/etc/wanpipe/: (or user defined)\n\twanpipe1.conf\tdefault router configuration file\n\netc/wanpipe/samples:\n\tinterface\tsample interface configuration file\n\twanpipe1.cpri \tCHDLC primary port\n     \twanpipe2.csec \tCHDLC secondary port\n     \twanpipe1.fr   \tFrame Relay protocol\n     \twanpipe1.ppp  \tPPP protocol ) \n\twanpipe1.asy\tCHDLC ASYNC protocol\n\twanpipe1.x25\tX25 protocol\n\twanpipe1.stty\tSync TTY driver (Used by Kernel PPPD daemon)\n\twanpipe1.atty\tAsync TTY driver (Used by Kernel PPPD daemon)\n\twanrouter.rc\tsample meta-configuration file\n\n/etc/wanpipe/firmware:\n\tfr514.sfm\tFrame relay firmware for Sangoma S508/S514 card\n\tcdual514.sfm\tDual Port Cisco HDLC firmware for Sangoma S508/S514 card\n\tppp514.sfm      PPP Firmware for Sangoma S508 and S514 cards\n\tx25_508.sfm\tX25 Firmware for Sangoma S508 card.\n \tbscmp514.sfm    Multi point bisync\n\tedu_kit.sfm     Education driver  \n\tbitstrm.sfm\tBit streaming firmware \n\tbscstrm514.sfm\tBisync streaming firware\n\n\n/lib/modules/X.Y.Z/misc:\n\twanrouter.o\trouter kernel loadable module\n\taf_wanpipe.o\twanpipe api socket module\n\n/lib/modules/X.Y.Z/net:\n\tsdladrv.o\tSangoma SDLA support module\n\twanpipe.o\tSangoma WANPIPE(tm) driver module\n\tsyncppp.o\tKernel Sync PPP module\n\n/proc/net/wanrouter\n\tConfig\t\treads current router configuration\n\tStatus\t\treads current router status\n\t{name}\t\treads WAN driver statistics\n\n/usr/sbin:\n\twanrouter\twanrouter start-up script\n\twanconfig\twanrouter configuration utility\n\tsdladump\tWANPIPE adapter memory dump utility\n        wanpipemon      Debugging Monitor for all WANPIPE protocols\n\twpkbdmon        WANPIPE keyboard led monitor/debugger\n\twancfg\t\tWANPIPE GUI configuration program.\n                        Creates wanpipe#.conf files. \n\tcfgft1\t\tGUI CSU/DSU configuration program.\n\n\nwanpipe/ (temporary untar directory):\n\tREADME\t\tthis file\n\tCOPYING\t\tGNU General Public License\n\tSetup\t\tinstallation script\n\tFilelist\tdistribution definition file\n\twanrouter.rc\tmeta-configuration file \n\t\t\t(used by the Setup and wanrouter script)\n\n/usr/share/doc/wanpipe:\n\tWanpipeInstallation.pdf \tWAN Router User's Manual\n\tWanpipeInstallation.txt\n\tWanpipeConfiguration.pdf\n\tWanpipeConfiguration.txt\n\tWanpipeOperation.pdf\n\tWanpipeOperation.txt\n\t\nwanpipe/patches:\n\twanrouter-v2213.gz  \tpatch for Linux kernels 2.2.11 up to 2.2.13.\n\twanrouter-v2214.gz\tpatch for Linux kernel 2.2.14. \n\twanrouter-v2215.gz\tpatch for Linux kernels 2.2.15 to 2.2.17.\n\twanrouter-v2218.gz\tpatch for Linux kernels 2.2.18 and up.\n\twanrouter-v240.gz\tpatch for Linux kernel 2.4.0.  \n\twanrouter-v242.gz\tpatch for Linux kernel 2.4.2.\n\twanrouter-v243.gz\tpatch for Linux kernel 2.4.3\n\twanrouter-v244.gz\tpatch for Linux kernel 2.4.4\n\twanrouter-v245.gz\tpatch for Linux kernel 2.4.5\n\twanrouter-v246.gz \tpatch for Linux kernel 2.4.6 and up\n\twanrouter-v249.gz\tpatch for Linux kernel 2.4.9 and up\n\twanrouter-v2416.gz\tpatch for Linux kenrel 2.4.16 and up\n\twanrouter-v2034.gz\tpatch for Linux kernel 2.0.34\n\twanrouter-v2036.gz \tpatch for Linux kernel 2.0.36 and up. \n\nwanpipe/patches/kdrivers:\n\tSources of the latest WANPIPE device drivers.\n\tThese are used to UPGRADE the linux kernel to the newest\n\tversion if the kernel source has already been pathced with\n\tWANPIPE drivers.\n\n/etc/wanpipe/api/x25:\n\t*\t\tx25 api sample programs.\n/etc/wanpipe/api/chdlc:\n\t*\t\tchdlc api sample programs.\n/etc/wanpipe/api/fr:\n\t*\t\tfr api sample programs.\n\n/usr/src/linux/include/linux:\n\twanrouter.h\trouter API definitions\n\twanpipe.h\tWANPIPE API definitions\n\tsdladrv.h\tSDLA support module API definitions\n\tsdlasfm.h\tSDLA firmware module definitions\n\tif_wanpipe.h\tWANPIPE Socket definitions\n\tif_wanpipe_common.h\tWANPIPE Socket/Driver common definitions.\n\tsdlapci.h\tWANPIPE PCI definitions\n\t\n\n/usr/src/linux/net/wanrouter:\n\t*\t\twanrouter source code\n/usr/src/linux/drivers/net/wan:\n\tsdla* and\n\twanpipe* \twanpipe source code\n\n/var/log:\n\twanrouter\twanrouter start-up log (created by the Setup script)\n\n/var/lock:  (or /var/lock/subsys for RedHat)\n\twanrouter\twanrouter lock file (created by the Setup script)\n\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Finterlinked1%2Fwanpipe","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Finterlinked1%2Fwanpipe","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Finterlinked1%2Fwanpipe/lists"}