Cisco catalyst 3850 switch wireless Guest setup
Hi experts,
compliments for the new year...
I'm back and lets call this phase two.
my previous questions were: ID: 28539488, Asked On2014-10-17 at 14:46:34
You guys help me on a Cisco catalyst 3850 switch wireless controller configurations... All my AP's are controller based and they all connect just fine now. thanx
But, with phase two, I needs to split this network into two... There are tons of document available but I don't get one related to my device.
I did some research and went through some videos too but I first wanted to know if any you guys have worked on this before and it will help a lot.
The client will technically have three options
1. Put more Wireless LAN controllers into the Network by placing on in the DMZ zone but this would be more costly but the best approach and it's scalable.
2. If they have small DMZ such as only a firewall, then we'll need some sorts of layer 2 connection to that firewall. A vlan should be created that all guest traffic should be passed to that port
The last option would be to create
3. ACL's on what the guest could and shouldn't access
In my case, I only have one WLC which is my switch and will it be best if practice I connect one cable directly from my WLC switch to the firewall and offload guest traffic to it?
I hope this is informative and if possible send me links again.
I don't see any Cisco as a topic
compliments for the new year...
I'm back and lets call this phase two.
my previous questions were: ID: 28539488, Asked On2014-10-17 at 14:46:34
You guys help me on a Cisco catalyst 3850 switch wireless controller configurations... All my AP's are controller based and they all connect just fine now. thanx
But, with phase two, I needs to split this network into two... There are tons of document available but I don't get one related to my device.
I did some research and went through some videos too but I first wanted to know if any you guys have worked on this before and it will help a lot.
The client will technically have three options
1. Put more Wireless LAN controllers into the Network by placing on in the DMZ zone but this would be more costly but the best approach and it's scalable.
2. If they have small DMZ such as only a firewall, then we'll need some sorts of layer 2 connection to that firewall. A vlan should be created that all guest traffic should be passed to that port
The last option would be to create
3. ACL's on what the guest could and shouldn't access
In my case, I only have one WLC which is my switch and will it be best if practice I connect one cable directly from my WLC switch to the firewall and offload guest traffic to it?
I hope this is informative and if possible send me links again.
I don't see any Cisco as a topic
ASKER
@craigback you're on track... but I'm a newbie to this and I will need links to the configs. The links I found are for other devices. thanx
I'll share my configs and the configs that I think will make this work, please edit if you think otherwise.
Yes, no traffic should go to the internal network...
I'll share my configs and the configs that I think will make this work, please edit if you think otherwise.
Yes, no traffic should go to the internal network...
I think I remember participating in the previous question... what configs do you have on your switches at the moment?
ASKER
I've cut the configs in half as the WiFi will be the only important part. I only have one profile in this config, no guest settings or a second profile has been added yet.
from a basic scenario, how would you configure you guest wireless network?
The corporate WiFi points to client vlan100 and we do get IP's from our DCHP server as the IP helper.
Let me know if you need more info
switch-config.docx
from a basic scenario, how would you configure you guest wireless network?
The corporate WiFi points to client vlan100 and we do get IP's from our DCHP server as the IP helper.
Let me know if you need more info
switch-config.docx
from a basic scenario, how would you configure you guest wireless network?It depends on a few things...
1] Where guest traffic will go (we know this already)
2] How you want to authenticate guest users
3] What you want to let guest users access (generally internet only)
There are other questions but generally this is what we need to establish first.
ASKER
Thanx for coming back...
you right,
1. guess should go straight to the net only.
2. We'll need to implement Mac security on the internal wifi too.
I thought of setting a second SSID where all guest connects to, which is the obvious... then from there a web portal should ask them for a username and password. The password should expired after a specific period.
3. yes, on point'
now... trying to put the configs together. let me know if you need more info about the switch, I'll quickly go through one document and share my Ideas. If you perhaps have more docs, please share the links.
you right,
1. guess should go straight to the net only.
2. We'll need to implement Mac security on the internal wifi too.
I thought of setting a second SSID where all guest connects to, which is the obvious... then from there a web portal should ask them for a username and password. The password should expired after a specific period.
3. yes, on point'
now... trying to put the configs together. let me know if you need more info about the switch, I'll quickly go through one document and share my Ideas. If you perhaps have more docs, please share the links.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Craig... you're on point, I want to ask you something before I jump back to the wireless guest side.
mac address security/ Port security...
The client wants to implement this on his network too and might required this for the wireless side too. Cam overflow protection purpose...etc
with port security basics...
one gets three options: static, dynamic and sticky... I believe sticky's the best option for a larger network, rather then putting every mac address in manually,
is it good practice to set all specific ports to a limit of only one mac address?
in my scenario, 1 core switch 3850s, and 4 2950 switches, should one configure port security only on one switch or is it necessary to do this only all switches.
violations:
Protect, restrict and Shutdown...
is it good practice to use aging with these options? I'll also use the Automatic recovery process.
again, thanx for all your help.
mac address security/ Port security...
The client wants to implement this on his network too and might required this for the wireless side too. Cam overflow protection purpose...etc
with port security basics...
one gets three options: static, dynamic and sticky... I believe sticky's the best option for a larger network, rather then putting every mac address in manually,
is it good practice to set all specific ports to a limit of only one mac address?
in my scenario, 1 core switch 3850s, and 4 2950 switches, should one configure port security only on one switch or is it necessary to do this only all switches.
violations:
Protect, restrict and Shutdown...
is it good practice to use aging with these options? I'll also use the Automatic recovery process.
again, thanx for all your help.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanx,
Just want to clarify on something in your previous comment...
"If you use 802.1x you don't want port-security"
Since 3850 wlc switch will be handle my wireless configs... will port security on it have any impact? we won't do mac address for wifi devices anymore.
Just want to clarify on something in your previous comment...
"If you use 802.1x you don't want port-security"
Since 3850 wlc switch will be handle my wireless configs... will port security on it have any impact? we won't do mac address for wifi devices anymore.
Port-security does nothing for wireless clients but it will for the APs. If you use port-security at the switchport you don't want to be authenticating the AP using 802.1x (actually the AP itself, not clients connected to it).
Port-security shouldn't be confused with wireless MAC authentication, which only applies to clients and is enforced at the AP's wireless interface, not the switchport.
When talking about 802.1x and port-security together we're talking about wired only. Don't consider wired 802.1x and wireless 802.1x in the same sentence as they won't affect each other.
Port-security shouldn't be confused with wireless MAC authentication, which only applies to clients and is enforced at the AP's wireless interface, not the switchport.
When talking about 802.1x and port-security together we're talking about wired only. Don't consider wired 802.1x and wireless 802.1x in the same sentence as they won't affect each other.
ACLs won't be enough to keep things secure.