The network
This example illustrates a
Allied Telesis | vlan1: |
router | 192.168.1.1 |
eth0: | workstation: |
192.168.254.1/30 | 192.168.1.100 by |
| automatic address |
| assignment |
192.168.254.2/30 |
|
NAT device |
|
100.100.100.1/30 |
|
100.100.100.2/30 | VPN |
| tunnel |
Internet |
|
200.200.200.2/30 |
|
WAN: |
|
200.200.200.1/30 |
|
SonicWALL | VLAN: |
router | 192.168.2.1 |
| workstation: |
| 192.168.2.100 by |
| automatic address |
| assignment |
|
Note: You can still use this example if you have no NAT device between the Allied Telesis router and the Internet, or if you have a NAT device between the SonicWALL router and the Internet, with slight alterations. See "Appendix: Using this example if you don’t have a NAT device in the same position" on page 31 for details.
Initiating the In this example, you can only initiate the tunnel from the Allied Telesis end, not the tunnel from SonicWALL end. If you want to let the SonicWALL initiate the VPN too, you have to
either end configure your NAT device to allow it. To do this, set up pinholes (allow rules) on the NAT device to allow through UDP traffic on ports 500 and 4500.
Page 3 AlliedWare™ OS How To Note: VPNs with SonicWALL routers