...
ADSL Installation and Support
-> Download Wanpipe Driver for ADSL protocol Support
-> ADSL protocol is Supported with Sangoma S518 Hardware (S519 is End-of-Life, click HERE for S519 installation information)
...
| Info |
|---|
NOTE: The S518 ADSL drivers do not work on 64bit kernels |
Installation:
ADSL drivers are part of Wanpipe's DEFAULT installation.
eg: ./Setup install -> Default Compilation Mode
Configuration:
ADSL configuration is performed using /usr/sbin/wancfg GUI configurator. Sample files are also located at the bottom of this file.
...
Interface Section
Specify interface name.
(Leave it default)Operation Mode: PPPoE
PPPoE: This interface will be used by the PPPoE
daemon, thus no ip information is needed.Leave the rest of the option DEFAULT
End of configuration, exit and save
Download Roaring Penguin PPPoE Stack :
Start Wanpipe:
wanrouter start
Install and configure Roaring Penguin PPPoE Stack.
Note: The ethernet interface name must be the wanpipe
pppoe interface name in section 5.1 above.
...
Check /var/log/messages.
...
w1g1: TTY Driver Init: Major 240, Minor Range 0-32
w1g1: TTY Sync Dev Minor 0 : /dev/ttyWP0
...
or you might see the following depending on kernel used:
---
w1g1: TTY Driver Init: Major 240, Minor Range 0-32
w1g1: TTY Sync Dev Minor 0 : /dev/ttyWP/0
---
Now the driver is ready for pppd connection.
Start PPPD based on configuration below:
pppd call isp_wanpipe1 <enter>
pppd call isp_wanpipe2 <enter>
...
For all wanpipe devices configured.
...
- /dev/ttyWPX :X is TTY_MINOR number.
- /etc/ppp/options
- /etc/ppp/peers/isp_wanpipeX :X is a wanpipe device number (1-16)
Device /dev/ttyWP(0,1,2..)
To interface a PPPD daemon to the WANPIPE TTY driver a
/dev/ttyWPX X={0,1,3...) device must be created.
eg:
mknod -m 666 /dev/ttyWP0 c 240 0
mknod -m 666 /dev/ttyWP1 c 240 1
mknod -m 666 /dev/ttyWP2 c 240 2
...
Note: 240 is the Major Number and 0,1,2... are the Minor Numbers
File /etc/ppp/options
-------CUT HERE ----------------------
persist #If connection goes down try to connect again
defaultroute #This interface will set default route
asyncmap 0
sync #Use Synchronous PPP
lcp-echo-interval 5
lcp-echo-failure 12#Following options disable compression.
#Lot of Telco equipment doesnt support it
nobsdcomp
nodeflate
nopcomp
novj
novjccomp
noaccomp -am#silent #On some CISCO routers we must be in silent mode
nodetach #DEBUG Should be commented out in production
debug #Should be commented out in production
kdebug 2 #Should be commented out in production
-------CUT HERE ----------------------
File /etc/ppp/peers/isp_wanpipeX (X=1 to 16)
-------CUT HERE----------------------
ttyWP0 #Bind to WANPIPE device wanpipe1#If IP address is commented out PPPD will attempt to
#get the IP address dynamically.
#Some PPP servers only negotiate single IP p-to-p address
#in such cases one must specify a their own Local:PtoP IP addresses.
#1.1.1.1:1.1.1.2#Set user name and password if running with PAP/CHAP
#Uncomment next two parameters if needed
#user <username>
#password <password>-------CUT HERE----------------------
For more information on PPPD configuration view
...
Multilink-PPP (PPPoA) over ADSL using PPPD Daemon
...
- /dev/ttyWPX :X is TTY_MINOR number.
- /etc/ppp/options
- /etc/ppp/peers/isp_wanpipeX :X is a wanpipe device number (1-16)
Device /dev/ttyWP(0,1,2..)
To interface a PPPD daemon to the WANPIPE TTY driver a
/dev/ttyWPX X={0,1,3...) device must be created.
eg:
mknod -m 666 /dev/ttyWP0 c 240 0
mknod -m 666 /dev/ttyWP1 c 240 1
mknod -m 666 /dev/ttyWP2 c 240 2
...
Note: 240 is the Major Number and 0,1,2... are the Minor Numbers
File /etc/ppp/options
-------CUT HERE ----------------------
persist #If connection goes down try to connect again
defaultroute #This interface will set default route
asyncmap 0
sync #Use Synchronous PPPlcp-echo-interval 1
lcp-echo-failure 3
#Following options disable compression.
#Lot of Telco equipment doesnt support it
nobsdcomp
nodeflate
nopcomp
novj
novjccomp
noaccomp -ammultilink #Enable Multilink
#silent #On some CISCO routers we must be in silent mode
#nodetach #DEBUG Should be commented out in production
#debug #Should be commented out in production
#kdebug 2 #Should be commented out in production
-------CUT HERE ----------------------
File /etc/ppp/peers/isp_wanpipeX (X=1 to 16)
-------CUT HERE----------------------
ttyWP0 #Bind to WANPIPE device wanpipe1
#If IP address is commented out PPPD will attempt to
#get the IP address dynamically.
#Some PPP servers only negotiate single IP p-to-p address
#in such cases one must specify a their own Local:PtoP IP addresses.
#1.1.1.1:1.1.1.2#MULTILINK NOTE:
#Each peer interface must have same IP configuration#Set user name and password if running with PAP/CHAP
#Uncomment next two parameters if needed
#user <username>
#password <password>-------CUT HERE----------------------
For more information on PPPD configuration view
Start PPPD based on configuration above:
pppd call isp_wanpipe1 <enter>
pppd call isp_wanpipe2 <enter>
...
For all wanpipe devices configured.
Where isp_wanpipe1 is the master device that contains IP information, and the rest of wanpipe devices have "noip" config options in peers/isp_wanpipeX filex.
...
Note: Dynamic IP Broken in kernels 2.6.17 and above.
New kernels do not allow changing of the ip address internally from the kernel. Due to this reason the Wanpipe PPP stack cannot support dynamic ip mode. We strongly suggest that your use the PPPDthe PPPD/TTY implementation of PPPoA as described above.
PPPoA Configuration:
Run: /usr/sbin/wancfg
...
[w1ad]
---- CUT HERE -----
...
Protocols supported on Windows
...