New VLANS - different subnets and or private ip range?

[CapnPugwash]

You can always break it up geographically later on.

 

Yeah, I think so. I think if we get everything all set up fairly solidly to start with & I understand the config of the switches, then I can tweak later.

 

Although right now I'm still wading through the basics!

 

If , for wireless devices, If I have a planned scope of 10.51.8.0 / 10.51.11.255 with subnet mask 255.255.252.0

And I set up the scope in DHCP with start / end IPs 10.51.8.1 / 10.51.11.254 , is the gateway still the default gateway address of my network (which is on a different scope) & if so, is this traffic routing handled within the switches themselves?

[CSE]

Your core switch (or whatever is doing the routing) will have multiple IP addresses, one on each of your subnets (VLAN's). Everything on each VLAN will have a default gateway address of the core switch as that is the device you want to route your traffic.

 

The only time I've seen it work any differently to this is in some wireless deployments where you may wish to keep guests separate from the rest of your network and you can give these devices a default gateway of your web filter to force the traffic through that, but be aware of the possible limitations of routing to the internal network if you do this.

 

So in your example you need to know what IP address your core switch is using inside this VLAN so you can exclude it in DHCP because your core switch will have to have an IP in that range somewhere.

[CapnPugwash]

Your core switch (or whatever is doing the routing) will have multiple IP addresses, one on each of your subnets (VLAN's). Everything on each VLAN will have a default gateway address of the core switch as that is the device you want to route your traffic.

 

The only time I've seen it work any differently to this is in some wireless deployments where you may wish to keep guests separate from the rest of your network and you can give these devices a default gateway of your web filter to force the traffic through that, but be aware of the possible limitations of routing to the internal network if you do this.

 

So in your example you need to know what IP address your core switch is using inside this VLAN so you can exclude it in DHCP because your core switch will have to have an IP in that range somewhere.

 

Great answer, thanks.

 

My problem all along has been that another company is programming the switches so it's been hard for me to visualise how everything connects.

 

They've put a bit of pressure on me to come up with VLAN IDs and IP ranges & told me I need to get it all into DHCP... almost like this is in isolation from what they are doing... when it's not. I'm not sure why they have made this so complicated. A bit more communication and we could have bottomed this by now.

[Davit2005]

Your core switch (or whatever is doing the routing) will have multiple IP addresses, one on each of your subnets (VLAN's). Everything on each VLAN will have a default gateway address of the core switch as that is the device you want to route your traffic.

 

The only time I've seen it work any differently to this is in some wireless deployments where you may wish to keep guests separate from the rest of your network and you can give these devices a default gateway of your web filter to force the traffic through that, but be aware of the possible limitations of routing to the internal network if you do this.

 

So in your example you need to know what IP address your core switch is using inside this VLAN so you can exclude it in DHCP because your core switch will have to have an IP in that range somewhere.

 

This is similar to what we do, guest WiFi goes directly to Firewall because that does ou Filtering, all the other vLANS have their defualt gateway as their vLAN on the Core Switch. i.e. vLAN 70 10.10.70.1/24

[CSE]

Yes that's what I would do too, attach the VLAN ID to an IP range (if you can) so the VLAN ID is not some random number with no connection to anything else