Announcements
Sangoma Hardware
HW Installation Manuals
Wanpipe Drivers Download Linux | Windows
Wanpipe for Asterisk
Install
Configure
Operation
Debugging
Tutorials
Appendix
Trixbox
Faxing
FAQ
Tapping(*New)
BRI: B700 / A500
Wanpipe for FreeSwitch
Install
Configure
Operation
FAQ
Appendix
Netborder VoIP Gateway
Linux
Windows
Release Notes
FAQ
Config Options
Routing Rules *NEW*
SMG-SS7
Install/Upgrade
Asterisk-SS7 Install
FreeSwitch-SS7 Install
Configure
Operation
Debugging
FAQ
Wanpipe TDM API
LibSangoma
Install/Config
FreeTDM
Wanpipe MTP2 API
Wanpipe for Wan/API
Install
Configure
RPMs
Operation
ADSL - S518
ADSL2+ - S519
Multi-Link PPP
Appendix
FAQ
Wanpipe for Yate
Wanpipe for Callweaver
Install
Configure
Wanpipe Case Studies
Troubleshooting
Tech Support
Glossary
| Wanpipe for Windows |
Wanpipe ADSL2+ (S519)
The S519 cards consists of a Realtek 8139 PCI network interface and an ADSL/ADSL2+ modem. This design makes the installation of this card very simple, the Realtek 8139 drivers are very common and are included in almost every Operating System available. The modem is configured either through your web browser or a telnet connection.
Most kernels should auto detect the card and automatically load the drivers for the Realtek 8139cp interface. If this is your case then simply configure the new network interface to use IP address 192.168.1.2 and a netmask=255.255.255.0, restart the computer and you will be able to configure the ADSL modem through your web browser by pointing it to 192.168.1.1.
If the drivers do not load automatically in Linux then the drivers need to be compiled through the kernel configuration utility.
- Go to the kernel build directory (you will need the kernel source files for this).
cd /lib/modules/$(uname -r)/build- Open the kernel configuration utility, find the Realtek 8139cp drivers, select them, save and exit:
make menuconfig- Re-compile the kernel modules. This will create the modules in the /lib/modules/$(uname -r)/build/drivers/net/:
make modules- Find the module named 8139cp.ko and copy it to /lib/modules/$(uname -r)/kernel/drivers/net/.
- Once you have copied the new driver run "depmod" so that the kernel recognizes the new driver.
depmod -A- Create a new network interface configuration file and set the interface to use IP address 192.168.1.2, netmask=255.255.255.0, and to load at start.
- Reboot the computer to activate the changes and the ADSL modem.
- Once the system is back up you should be able to ping both 192.168.1.2 (network interface) and 192.168.1.1 (modem).
If you have any problems please contact Sangoma Tech support at techdesk@sangoma.com
Most versions of Windows should auto detect the card and automatically load the drivers for the Realtek 8139cp interface. If this is your case then simply configure the new network interface to use IP address 192.168.1.2 and a netmask=255.255.255.0, restart the computer and you will be able to configure the ADSL modem through your web browser by pointing it to 192.168.1.1.
If the drivers do not load automatically in Windows then:
- Download the latest driver from Realtek.
- Run the auto-installation program included in the drivers
- Once the drivers have been installed configure the IP address through the Network Connections window.
- Right click the new interface and select "Properties"
- Next select the "Internet Protocol (TCP/IP)" item and click on "Properties".
- In the new window that appears select "Use the following IP Address" and enter 192.168.1.2 for the IP address and 255.255.255.0 for the Subnet Mask.
- Click "Ok" until you are back at the "Network Connections" window.
- You should now be able to ping both 192.168.1.2 (network interface) and 192.168.1.1 (modem).
If you have any problems please contact Sangoma Tech support at techdesk@sangoma.com
Configuration for Both Linux and Windows
***Note: the following instructions are for configuration through the telnet connection to the ADSL modem.
1.)Configuring for PPPoE Connection
If you have any problems please contact Sangoma Tech support at techdesk@sangoma.com
- Setup a new transport in the ADSL modem using:
pppoe add transport pppoe1 dialout pvc 1 a1 <vpi> <vic>- Setup the PPPoE connection username:
pppoe set transport pppoe1 username <username>- Setup the PPPoE connection password:
pppoe set transport pppoe1 password <password>- Test the connection:
- Turn on manual connection so that you restart the connection manually:
pppoe set transport pppoe1 manualconnect enabled- Force a connection attempt:
pppoe set transport pppoe1 connectnow enabled- Check the status of the connection:
pppoe show transport pppoe1- Add NAT reserved mapping so that all WAN traffic is passed to the internal IP address:
nat add resvmap rm1 interfacename ipwan 192.168.1.2 all
2.)Configuring for PPPoA Connection
If you have any problems please contact Sangoma Tech support at techdesk@sangoma.com
- Setup a new transport in the ADSL modem using:
pppoa add transport pppoa1 dialout pvc 1 a1 <vpi> <vci>- Setup the PPPoA connection username:
pppoA set transport pppoa1 username <username>- Setup the PPPoA connection password:
pppoa set transport pppoa1 password <password>- Test the connection:
- Turn on manual connection so that you restart the connection manually:
pppoa set transport pppoa1 manualconnect enabled- Force a connection attempt:
pppoa set transport pppoa1 connectnow enabled- Check the status of the connection:
pppoa show transport pppoa1- Add NAT reserved mapping:
nat add resvmap rm1 interfacename ipwan 192.168.1.2 all
3.)Configuring for RFC 1483 (Bridged Ethernet)
Type the following CLI commands to configure the modem for bridging
ip delete interface ipwan
bridge add interface br0
bridge attach br0 ethernet
rfc1483 add transport tr1 a1 8 35 llc bridged
{note the VPI, VCI values vary from country to country. 8, 35 as shown is for Australia. For other countries see attachment}
bridge add interface br1
bridge attach br1 tr1
system config save
If you have any problems please contact Sangoma Tech support at techdesk@sangoma.com
Power LED
Solid Green = Power on
Off = Power off
Red = POST (Power On Self Test) failure (not bootable) or Device malfunctionEthernet LED
Solid Green = Powered device connected to the associated port
Flashing Green = LAN activity present (traffic in either direction)DSL LED
Solid Green = DSL good sync
Off = Modem power off
Flashing Green = DSL attempting sync
Flashing at 2 Hz with a 50% duty cycle when trying to detect carrier signal
Flashing at 4 Hz with a 50% duty cycle when the carrier has been detected and the modem is trying to trainInternet LED
Solid Green = IP connected (the device has a WAN IP address from IPCP or DHCP and DSL is up or a static IP address is configured, PPP negotiation has successfully complete - if used - and DSL is up ) and no traffic detected. If the IP or PPPoE session is dropped due to an idle timeout, the light will remain green if an ADSL connection is still present. If the session is dropped for any other reason, the light is turned off. The light will turn red when it attempts to reconnect and DHCP or PPPoE fails.
Off = Modem power off, modem in bridged mode or ADSL connection not present
Flickering Green = IP connected and IP Traffic is passing thru the device (either direction)
Red = Device attempted to become IP connected and failed (no DHCP response, no PPPoE response, PPPoE authentication failed, no IP address from IPCP, etc.)For bridged mode, the indicator light MUST be off.
- How do I access the telnet connection to the ADSL Modem?
-for Linux and Windows; open a new command prompt and run "telnet 192.168.1.1"- What is the default user name and password for the telnet connection or the Web GUI?
-user name = admin
-password = admin- How do I change the default address for the S-519 so that I can run multiple cards
- Connect to the telnet interface
-telnet 192.168.1.1- Change the IP address of the iplan interface:
-ip set interface iplan ipaddress <X.X.X.X>- The telnet connection will be stalled now since it is pointing to the wrong address, the network interface needs to be updated now:
-for Linux:
-for Windows:
- Create a new network interface configuration file and set the interface to use IP address <X.X.X.X>, netmask=255.255.255.0, and to load at start.
- Reboot the computer to activate the changes and the ADSL modem.
- Once the system is back up you should be able to ping both the network interface (X.X.X.X+1) and the modem interface (X.X.X.X).
- Once the drivers have been installed configure the IP address through the Network Connections window.
- Right click the new interface and select "Properties"
- Next select the "Internet Protocol (TCP/IP)" item and click on "Properties".
- In the new window that appears select "Use the following IP Address" and enter <X.X.X.X> for the IP address and 255.255.255.0 for the Subnet.
- Click "Ok" until you are back at the "Network Connections" window.
- You should now be able to ping both the network interface (X.X.X.X+1) and the modem interface (X.X.X.X).
- My Linux network interface for the S519 fails to start and when I run "ifconfig -a" I see an interface with the name "__tmp<random number>"
-The Realtek driver is mis-naming the interface when it loads...renaming the interface fixes the issue
- Run "ifconfig -a" to find out the name currently assigned by the Realtek driver to the interface
[root@konrad132 ~]# ifconfig -a
__temp1186241952 Link encpa:Ethernet HWaddr 00:0A:FA:30:00:A8
BROADCAST MULITCAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:82 Base address:0xc000- Run "ip link set dev __tmp1186241952 name eth0" to change the name to "eth0"
Attached Files
| PVCs.pdf | yannick | Jun 15, 2009 | 5 KB |
| PVCs | |||