How to access remote LAN of a SonicWall from an other LAN SonicWall without VPN Site to Site?
Hello, below my problem:
Site A
- LAN IP X0 : 192.168.0.254
- WAN IP X1 : 10.10.10.1
Site B
- LAN IP X0 : 172.16.0.254
- WAN IP X1 : 10.10.11.1
The LAN 192.168.0.0 /24 of the SonicWall of the Site A can ping the WAN Interface 10.10.11.1 of the SonicWall of the Site B.
The LAN 172.16.0.0 /24 of the SonicWall of the Site B can ping the WAN Interface 10.10.10.1 of the SonicWall of the Site A.
From the LAN 192.168.0.0 /24 of the Site A, how can I ping the LAN 172.16.0.0 /24 of the Site B?
…and inversely
What routing should be configured on both SonicWalls? Are NAT rules needed, which ones?
Many thanks for your help.
Best Answers
-
TKWITS Community Legend ✭✭✭✭✭
If the connection your 10.10.x.x interfaces are on is private, you can setup static routes to have the LANs talk to each other through the 10.10.x.x interfaces without NAT. You'll need access rules to allow the traffic as any traffic from WAN zones to LAN zones is dropped by default.
See the following articles:
0 -
JeroLefe Newbie ✭
Thank you verry much TKWITS, I have allow "Use Routed Mode - Add NAT Policy to prevent outbound\inbound translation checkbox to enable Routed Mode for the interface X0" on each SonicWall.
Next, I have add the static route below:Site A
- Source: 192.168.0.0 /24
- Destination: 172.16.0.0 /24
- Service: Any
- Gateway: X1 Default Gateway - 10.10.11.1
Site B
- Source: 172.16.0.0 /24
- Destination: 192.168.0.0 /24
- Service: Any
- Gateway: X1 Default Gateway - 10.10.10.1
Finally, I have allow traffic from LAN to WAN on each SonicWall.
Now, I can dialog from 192.168.0.0 LAN Network to the 172.16.0.0 LAN Network and inversely.
At the begining, I was missing the "Use Routed Mode - Add NAT Policy to prevent outbound\inbound translation checkbox to enable Routed Mode for the interface X0" on each SonicWall and allow traffic from WAN to LAN…Thanks again for your specific help.
0
Answers
A Site to Site VPN is the solution