10-05-2012 2:01 PM
I have a Sonicwall firewall sitting behind my AT&T RG (3800) in DMZ Plus mode. the RG has a public IP address of 99.x.x.x.x and 192.168.0.x as provate. The public IP was passed via DHCP to the SonicWall's WAN port. The LAN and WLAN are on subnets 192.168.1.x and 192.168.2.x
I ordered a static IP block in order to configure my SonicWall's SSLVPN. AT&T gave me a x.x.x.192/8 that makes a block of x.x.x.192 through x.x.x.200. Based on this I configured x.x.x.199 under supplemental networks. (IP Address and subnet)
I set the new public IP given by AT&T (x.x.x.199) as the address for the WAN interface, and tried setting x.x.x.1 as gateway, and 188.8.131.52 as DNS. This does not allow me to browse the internet at all. I can't access my SSLVPN either.
I then configured the WAN port as x.x.x.198 and gateway 99.x.x.1 and although it is not "technically" correct.. I can reach the internet.
However, this configuration also does not allow me to reach my SSLVPN.
I wonder.. how exactly should I configure it with the new static IP block, so I can acess internet and my SSLVPN?
I will appreciate any help you can provide.
Solved! Go to Solution.
10-06-2012 5:18 PM
10-07-2012 9:44 AM - edited 10-07-2012 10:20 AM
Thanks… that certainly fixed my problem.
01-26-2013 11:39 AM
Is there any reason to use anything but 100-full on the Sonicwall WAN interface?
01-26-2013 12:06 PM
© 2016 AT&T Intellectual Property.This link will open a new window All rights reserved. AT&T, Globe logo, Mobilizing Your World and DIRECTV are registered trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks are the property of their respective owners.
Congratulations! You earned the Liz badge!