VLANing a network

[rhys1984]

That's great - thank you.

 

Speckytecky: I'm browsing on my phone, and can't actually see a facility to say thanks?

[FN-GM]

OK Thanks for that. We do have an alternative range already set-up by our LA which is for future use (10.56.75.0) - so could I just configure static routing on our L3 Switch between this range and our existing range?

 

Thanks

 

Rhys

 

No need to touch static routes. Can you go on your core and run this command and post the results please? Command: Show IP Route

 

Sorry guys - one last question: If we decide to go ahead with this, and create two VLANs (one on the 10.56.75.0 - VLAN1, with VLAN2 on the existing 10.56.80.0 interface), how would we then go about tagging the relevant wireless box port on the switch?

 

I.E: Our Wireless box will need to be configured as follows:

Staff wireless: VLAN2 - 10.56.80.0

Guest wireless: VLAN1 - 10.56.75.0

 

So what configuration would be required on the switch? Am I correct in thinking that a port on a switch can be configured with multiple VLANS?

 

Thanks,

 

Rhys

 

What wireless are you using? I see a screenshot for Ruckus, is this the solution your a using? If it is Ruckus and as you have Cisco I will be able to guide you end to end as I have set this up many times before.

Edited August 22, 2015 by FN-GM

[FN-GM]

So the staff wireless will be the same ip range and vlan as the main network as well as the management interface of your ap's, and the guest wireless will be on a different vlan/ip range? If so on the switch port connected to the ap, untag the staff vlan (this should pass through to the default ssid) and then tag the guest vlan and link it to the guest ssid.

 

Do not do this. A you are using Cisco so you don't tag anway. And B if you try and translate this to cisco you may break your existing wireless.

[FN-GM]

@rhys1984 Can you also do the command "Show Running-Config" from your core and the access switch that your Access point is connected to and copy and paste the configuration for the following ports:

 

1: The port that connects the core Switch to the access switch

2: The port on the Access Switch that connects to the core.

3: The port on the Access Switch that connects to the access point.

 

Do not post the whole config as it will show your switch password.

[rhys1984]

Thanks - could you explain why I wouldn't need to configure static routing if I am routing between two VLANs on different subnet ranges? What would the alternative method be?

And yes, I'm not in work for a few days but as soon as I can I'll get the confit info sorted.

And we are using Aironets here - a few schools teamed together and got a good price for them.

 

Thanks,

 

Rhys

Edited August 22, 2015 by rhys1984

[rrrrr]

We also use cisco aironets in the tag/untag config i mentioned in previous post. We are slowly replacing with ruckus

[FN-GM]

Thanks - could you explain why I wouldn't need to configure static routing if I am routing between two VLANs on different subnet ranges? What would the alternative method be?

 

When you create your new VLAN it will be automatically added to the routing table.

[rrrrr]

When you create your new VLAN it will be automatically added to the routing table.

 

This is true for internal traffic if your using a switch as your default gateway but static routes may need to be added to your webfilter for internet traffic to be routed to correct vlan

[lholland421]

We had to setup static routes on our web servers so people on our guest wireless could access them.

 

That was only because our guest wireless runs a 172.16 scheme and our lan is on 10.82 .

[speckytecky]

Fair point @rhys1984

 

I've noticed on an iPad that the thanks button doesn't appear every time as well.

 

 

That's great - thank you.

 

Speckytecky: I'm browsing on my phone, and can't actually see a facility to say thanks?

[FN-GM]

We had to setup static routes on our web servers so people on our guest wireless could access them.

 

That was only because our guest wireless runs a 172.16 scheme and our lan is on 10.82 .

 

But that does not necessary apply here, sounds like your router/L3 switch wasn't setup correctly.