Link to home
Create AccountLog in
Avatar of JamesonJendreas
JamesonJendreas

asked on

Sonicwall Interface Routing

Should be easy - trying to setup two internal networks to use two different WAN links.  I am using a SonicWall NSA 4500, utilizing 4 of the interfaces as follows:

X0 - Primary LAN - 192.168.10.1 /25
X1 - Primary WAB - b.b.b.b. Gateway: b.b.b.a
X2 - Secondary WAN - c.c.c.c gateway c.c.c.b
X3 - Secondary LAN - 10.10.254.1/24

So, I have it setup that the b.b.b.a is my default gateway.   I have a laptop with a static IP 10.10.254.10/24 plugged into X3.  I can ping this from any device on the X0 subnet or anywhere else.

So I have created a rule where:
Source: X4 Subnet
Destination: Any
Service: Any
Gateway: c.c.c.b

Pings timeout.  If I remove the rule, I get out just fine, but am using the wrong outbound interface.

Suggestions?
Avatar of Shane McKeown
Shane McKeown
Flag of Ireland image

2 things I can see possibly...

1) Gateway - should be the WAN ip - c.c.c.c, not c.c.c.b
2) I don't see your INTERFACE setting - normally you have an Interface section where you specify WAN1 or WAN2 - is there not an option to select that?
Avatar of JamesonJendreas
JamesonJendreas

ASKER

So #1 - That makes some, sense but alas did not resolve the issue. I kind of need to think about that though - since this is a single L3 device, I'm still thinking we'd set the far end of the gateway, as the sonicwall has an interface that is on the same subnet as the c.c.c.b (otherwise, I'm routing to it's own interface)

2) No interface setting for what WAN link to take.  I'm thinking this might be because I have both links setup in the same Zone (WAN), and within an Load Balance group.
ASKER CERTIFIED SOLUTION
Avatar of Shane McKeown
Shane McKeown
Flag of Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Alright, that was it.  I for some reason didn't understand what you meant by interface settings, I was thinking the actual physical interface settings (for x3), not the interface settings on the route statement.  

Changing the route to the proper interface resolved the issue. \

Cheers!
Great...glad it worked...