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

Configuring Guest WLAN using Cisco WLC 2106

I've already read many posts here concerning similar issues, but have yet to find a solution that will help me. First of all, I am by no means a Cisco guru but have been in the computer support field for over 36 years. I'm really good at taking direction.

We currently have a WLAN that is used inside our firewall for tablets and laptops. I would like to expand and create a GUEST WLAN that will be isolated from our internal network. I do not currently use VLANs, but I do have a home run that connects to a switch which is directly connected to tha cable modem outside the firewall. I ve tested the home run cable with a laptop and all is good as far as connectivity to the outside world.

I have configured the 2106 to the best of my ability using the correct subnet 192.168.23.0/24
The internal DHCP server in the 2106 is providing IP addresses to the wireless devices. All looks good except I cannot reach the outside world. As a matter of fact, the 2106 appaently does not see the cable modem at all. When I created the Guest WLAN, I configured it to Port 4  where the home run is connected.
I know you may need additional info, but I thought I would start here and see if someone can shed some light. Any assistance is appreciated. thank you.

-norm
0
WEBEUS
Asked:
WEBEUS
1 Solution
 
Fred MarshallPrincipalCommented:
Here's something to look at at least....
Once you have an idea of the architecture you want then getting into the specifics of various devices is all that much easier.  Of course, you may iterate between the two.
Wireless-Router-as-a-Simple-Swit.pdf
Multiple-Subnets.pdf
0
 
WEBEUSAuthor Commented:
After staring at my configuration for a bit, it suddenly dawned on me what the issue was. When I configured the GUEST WLAN, I tagged it with a VLAN number. I changed the entry to "0" (untagged) and problem solved.

Thank you for the documents...


-norm
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

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