VLAN unable to get on internet

[snagrat]

So I have setup a basic VLAN on my switches and Ruckus wireless. The idea that anyone who connects to a certain SSID gets an IP from a different DHCP server. I have a DHCP server on each VLAN (default 1 + 100).

 

I know its not the best way to do it but it seems to work OK currently. Devices get the IPs from the correct DHCP server depending on which WLAN they join.

 

However I am unable to ping the router from the new VLAN 100. Now each DHCP server is setup to distribute from the same range but do not cross (i.e DHCP 1 = 10.0.0.1 - 10.0.0.100 and DHCP2 = 10.0.0.101 - 10.0.0.200).

 

I thought it might be as easy as making the port the router plugs into the switch as a TRUNK like I have done for the Ruckus AP and ZD? But that doesn't seem to work.

 

Any suggestions?

[chilbs]

Have you given the new vlan an ip address as the clients will need this as their gateway to talk to the rest of the network.

[Steve21]

Why not just tag the ports of the server with 2 VLANs?

 

If you made a new VLAN have you made the route for it to get out to the gateway etc as that's going to be on another VLAN anyway

 

Steve

[Davit2005]

Can you give quick diagram of setup??

 

As I remember from what I before did tag the ports from the Switch to our SonicWall and then used sub interfaces on the SonicWall. The Sonicwall was setup as DHCP server for the additional SSIDS but not the school device WiFi.

 

These days we have our Core switch doing the IntervLan routing and our DHCP provides the IP addresses.

[snagrat]

Why not just tag the ports of the server with 2 VLANs?

 

If you made a new VLAN have you made the route for it to get out to the gateway etc as that's going to be on another VLAN anyway

 

Steve

 

That's the future plan but the servers are virtualised going through different switches which I haven't got my head around yet

[Steve21]

That's the future plan but the servers are virtualised going through different switches which I haven't got my head around yet

 

Either way, you need to have a route from your VLAN to the Gateway. You're going to cause yourself more problems using 2 servers with the same range/VLAN etc.

 

Whatever is doing your routing needs to know about the VLANs and where to route them.

 

Normally it would be each VLAN points to a unique IP address on the "router" as it's gateway e.g. 10.1.0.1 for VLAN 1, and 10.100.0.1 for VLAN 100. And then the router works out how to route from 10.100.0.1 to the real gateway of 10.0.0.1

 

Steve

[snagrat]

Either way, you need to have a route from your VLAN to the Gateway. You're going to cause yourself more problems using 2 servers with the same range/VLAN etc.

 

Whatever is doing your routing needs to know about the VLANs and where to route them.

 

Normally it would be each VLAN points to a unique IP address on the "router" as it's gateway e.g. 10.1.0.1 for VLAN 1, and 10.100.0.1 for VLAN 100. And then the router works out how to route from 10.100.0.1 to the real gateway of 10.0.0.1

 

Steve

 

I thought routing was only required if inter-VLAN routing was happening. Am I wrong then?

 

I do have a second interface on the router so I may configure that on a different IP address range and see if that works.

 

Thanks

[Steve21]

I thought routing was only required if inter-VLAN routing was happening. Am I wrong then?

 

I do have a second interface on the router so I may configure that on a different IP address range and see if that works.

 

Thanks

 

Effectively your are routing though, as your VLAN has no route to the Gateway on a different IP range.

 

If you have a spare port on the router you can configure it, but you'll still need to configure the routing between the VLANs etc or the tags on the external as it's all one port in etc

 

Steve

[ReBoot]

"Now each DHCP server is setup to distribute from the same range but do not cross (i.e DHCP 1 = 10.0.0.1 - 10.0.0.100 and DHCP2 = 10.0.0.101 - 10.0.0.200)."

 

Each VLAN needs to be on a different subnet. As I understand your description you are allocating part of the same subnet from each DHCP server.

 

This isn't how VLAN design works. You can't route to each VLAN if they are on the same subnet. Without going into detail there is also no benefit from using VLANs in this way as you haven't segmented your broadcast domain.

 

I suggest you start by splitting your address range into 2 subnets such as 10.0.0.0/25 and 10.0.0.128/25 (255.255.255.128) as a starting point.

 

10.0.0.1 Gateway 10.0.0.2 - 126 DHCP Range

10.0.0.129 Gateway 10.0.0.130 - 254 DHCP Range

 

You will need routes on your router for each VLAN subnet 10.0.0.0/25 and 10.0.0.128/25.

[ReBoot]

Footnote on the routing question. You will always require routing with VLANs unless there will be no traffic between them and no internet access.

 

For Internet access your router will need a route for each VLAN subnet associated with a physical port or tagged subinterface.

 

Inter VLAN routing is a form of policy based routing or access control where the router is configured to block or pass traffic between specific VLANs.