Sonicwall in a third party data centre

ashrobbo

ashrobbo

ashrobbo

Associate
Joined
3 May 2009
Posts
805
Hi all

working with a tz210 which we have placed in cloud 9s data centre.

The x0 interface is 192.168.x.1
The x1 interface is 80.x.x.xwhich which assigned to us by cloud 9 ages ago

We require another static ip which they have assigned to us but it's on a different range on 90.x.x.x For arguments sake.

From the sounds of it they are natting 90.x.x.x directly to a server on the LAN (192.168.x.101)

Now to Me that sounds odd. They couldn't redirect the 90.x.x.x traffic to the 80.x.x.x as the Cisco asa won't Let them.

Will it work if they Nat to the x0 sonic wall ip?

Cheers

Ash
 
Do you just have the two interfaces in use?

I'd probably expect Cloud 9 to send both IPs "down" to X1 and then you can create new address objects to NAT the 90.x IP through to X0 (just like you do with the 80.x range).

We've got customers with BT DSL connections. They tend up give a dynamic IP out first (which the SonicWall picks up via PPPoE) and then provide a /29 subnet in a totally different range for static IPs. Works fine.
 
They have now provided an additional ip that is 80.x.x.122 but they are still natting to the LAN ip of the sonic wall. It's still not working, is there an easy way to determine if traffic is getting as far as the sonic wall??
 
Depending on the SonicOS version, you can look in the logs, connection monitor or run a packet capture.

I don't see how the provider can NAT it to a private IP and expect it to get through your SonicWall. I'd expect your SonicWall to do that address translation...
 
Exactly what I was thinking, the X0 goes into our on site switch, and the X1 goes into their cisco layer 3 switch, they dont have access to our lan interface on the cisco so it was never going to work.

Will hassle them some more today.
 
You must log in or register to reply here.
Back
Top Bottom