HLF_David
asked on
Creating a Tunnel with Sonic Wall TZ and Somic Wall SOHO3
I have created a tunnel between two location of our company using a Sonic Wall TZ at our corporate location and a SOnic Wall SOHO3 at our Satelittle location. The tunnel seems to work fine at the satelitte location when I plug the Sonic Wall LAN port directly into a single PC. When I do this everything passes fine and works. I can get an IP address, get out to the internet, remotoe desktop into other machines.
However, when I plug the SOnic Wall into a switch nothing will work. Checking the logs in the Sonic Wall I get this IP Spoofing error.
"IP spoof detected on packet to Central Gateway, packet dropped"
I've tried all kinds of solutions like using a cross-over cable from the Sonic Wall to the switch, created numerous rules but I must being doing something wrong at some point. Has anyone come accross this issue? Thanks.
However, when I plug the SOnic Wall into a switch nothing will work. Checking the logs in the Sonic Wall I get this IP Spoofing error.
"IP spoof detected on packet to Central Gateway, packet dropped"
I've tried all kinds of solutions like using a cross-over cable from the Sonic Wall to the switch, created numerous rules but I must being doing something wrong at some point. Has anyone come accross this issue? Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
After defining your LAN interface and LAN zone ; you should be able to define firewall access rules from LAN to VPN .
what do you see under Network>Zone ?
what do you see under Network>Zone ?
No worries , I think you are doing great .
In your SOHO 3 ; do you have a NETWORK section in web GUI ? do you see interface and zones options ?
In your SOHO 3 ; do you have a NETWORK section in web GUI ? do you see interface and zones options ?
where do you see the IP spoofing error ? on SOHO or on TZ ?
I have a similar setup..
I have a SOHO2 .. looking into it now ; let's see the similarities...
Under General > Network : Make sure "NAT enabled " is selected.
Under Sonicwall LAN IP address : make sure you have an IP in the range that you considered for your satellite network .
from ACCESS > service ; make sure default is selected at least.
Under ACCESS > Rules : Make sure you allow services from source (LAN) to destination(*).
this is on SOHO side ; If you get the IP spoofing error on TZ , let me know .
I have a SOHO2 .. looking into it now ; let's see the similarities...
Under General > Network : Make sure "NAT enabled " is selected.
Under Sonicwall LAN IP address : make sure you have an IP in the range that you considered for your satellite network .
from ACCESS > service ; make sure default is selected at least.
Under ACCESS > Rules : Make sure you allow services from source (LAN) to destination(*).
this is on SOHO side ; If you get the IP spoofing error on TZ , let me know .
Dear could you please answer "where do you see the IP spoofing error ? on SOHO or on TZ ? "
apart from above could you please let us know how many network switches you have, are you using VLANs in your office?
what is the lan subnet of your site and what is the lan subnet of other site?
""IP spoof detected on packet to Central Gateway, packet dropped" this error has nothing to do with NAT or Routing
apart from above could you please let us know how many network switches you have, are you using VLANs in your office?
what is the lan subnet of your site and what is the lan subnet of other site?
""IP spoof detected on packet to Central Gateway, packet dropped" this error has nothing to do with NAT or Routing
ASKER
Ok. I stopped and did a little thinking and figured out what was causing the IP Spoofing issues.
What happened is this. Before I finished the tunnel I had move over 3 server from corporate to set up at the satelittle location. They had already been assigned a DHCP lease at corporate so when I plugged them up here and to the switch and then plugged the Sonic Wall into the switch they conflicted.
To remedy this I unplugged everything from the switch and unplugged it. Then I plugged the LAN from the Sonic Wall to the switch. After that I used a HotSpot connection to VPN to corporate and release the DHCP leases assigned to the servers. Once I did that I hooked up an individual PC and then the servers and everything is working as it should be.
Thanks for the help your posts got me to thinking along a different tangent.
What happened is this. Before I finished the tunnel I had move over 3 server from corporate to set up at the satelittle location. They had already been assigned a DHCP lease at corporate so when I plugged them up here and to the switch and then plugged the Sonic Wall into the switch they conflicted.
To remedy this I unplugged everything from the switch and unplugged it. Then I plugged the LAN from the Sonic Wall to the switch. After that I used a HotSpot connection to VPN to corporate and release the DHCP leases assigned to the servers. Once I did that I hooked up an individual PC and then the servers and everything is working as it should be.
Thanks for the help your posts got me to thinking along a different tangent.
ASKER
The post got me to thinking about how I hooked everything up to the switch and in what order. It helped lead to a final solution.
ASKER
Forgive me for my ignorance am I filling in for the on-site Network guy and I am a programmer. So alot of this is foreign to me.