• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1471
  • Last Modified:

Vlans and switch route to Internet

I'm not sure if this is a problem or a misconfiguration but I could do with some help please.

We have a HP A5120 SI 3 layer switch setup with 2 Vlans,  Vlan 1 and Vlan 2 the switch trunks to a Sonicwall TZ210 for internet access.  

The Sonicwall has two subinterfaces and for both subnets, I can ping the switch interfaces and Sonicwall subinterfaces from the Vlans.  

The problem I'm having is with the default route for internet access. What should this be??

If I add the following 2 routes only one route shows as active and that specific Vlan has Internet access, if I remove one off the static routes then the remaining route becomes active.

What I need is both routes to be active so both Vlans can access the internet at the same time.

Static routes

I tried adding the Sonicwalls primary interface as the default static route but the switch couldn't see the network, I assume the Sonicwall dropped the packets as per design.  

Any help/advise would be grateful as to how i can get both Vlans to share an internet connection.
2 Solutions
try the following

remove ip config on the router

on the switch create a new interface with ip
on the router create an interface with ip

on clients put the L3 switch as the default gateway
on the L3 switch put the as the default gateway

If I recall the TZ series don't support VLAN tagging, so you'll either have to do what fcontrepois said or put the uplinks on different switch ports and plug them into two interfaces on the sonicwall (i.e. LAN 1 goes from port 1 on switch to X0 on TZ210, LAN 2 goes from port 2 to X2 on TZ210).

HatchITAuthor Commented:
The latest SonicOS 5.8 now supports Vlan tagging on the TZ210 so both Sonicwall subinterfaces are tagged accordingly X0:20 and X0:50

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

You do not need static routes on the switch for this if the VLANs extend to the Sonicwall. What you need is to set the default gateway on your computers for the Sonicwall's IP's.

You might as well disable IP Routing on the switch, i really don't see the need to add another VLAN to it (192...).

HatchITAuthor Commented:
We looked at that option but we wanted the switch to do the routing between vlans so if anything happend to the Sonicwall the clients could still communicate across the vlans. We want the the Sonicwall to do just internet and vpn access going forward.
Even if you have IP Routing enabled on the switch, it doesn't matter because of your default gateway. If you set the default gateway on your computers to 172.18.x.1, the packet will go go the Sonicwall because the VLAN is extended all the way there.

If you want to route locally, you have to remove the 172.18.x.x networks from the Sonicwall like fcontrepois said on the first post and create the 192.168.1.x network on the switch.

Important concept to remember is that a packet will only hit a Router Interface if it does not have the destination IP on the same VLAN, so by extending the Layer 2 all the way to the Sonicwall, your pretty much eliminating the need for Layer 3 on the switch.


HatchITAuthor Commented:
RK, I think you hit the nail on the head, it all makes sense, Thanks.
Thanks Hatchit !

I think you might want to consider giving credit to fcontrepois as well. He didn't go into detail, but I think he meant the same thing on his first post.

HatchITAuthor Commented:
RK, I think you hit the nail on the head, it all makes sense, Thanks
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now