- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2013 07:56 AM - edited 03-10-2019 12:21 PM
This isn't a big deal as the rest of the ACL works fine, but this is an annoynace since the web auth redirects to our company website (internal for now) after successful login.
We have a Cisco WLC that provides access to our production and guest wireless environments. The guest environment of course is in a separate vlan (10.10.50.0/24). So I created this ACL:
access-list 107 permit udp any host 10.10.2.13 eq bootpc <----internal DHCP server
access-list 107 permit udp any host 10.10.2.13 eq bootps
access-list 107 deny ip any 10.10.0.0 0.0.255.255 <---all internal networks
access-list 107 deny ip any 172.28.16.0 0.0.0.255 <----DR Network
access-list 107 permit ip any any
int vlan 50
Desc "Guest wireless network"
ip access-group 107 in
This ACL basically gives the wireless guests access to an internal DHCP server and full access to the internet. For the 10.10.50.0/24 scope, the DHCP server assigns Internet DNS servers and my rationale is that wireless clients would access it via the external IP address but I suppose it doesn't work quite like that with the website being behind the same router as the client machines. What's the best way to get this working?
Solved! Go to Solution.
- Labels:
-
Other Switching
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2013 11:38 AM
Okay I fixed it. Had a mental freeze. If I want them to access an internal website on the internal LAN the machines need to use the internal DNS server. I added the internal DNS servers to the DHCP scope for the guest network and then added them to the acl along with the web server IP and it works.
Somehow I thought it was more secure to have the guests use an external DNS server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2013 11:38 AM
Okay I fixed it. Had a mental freeze. If I want them to access an internal website on the internal LAN the machines need to use the internal DNS server. I added the internal DNS servers to the DHCP scope for the guest network and then added them to the acl along with the web server IP and it works.
Somehow I thought it was more secure to have the guests use an external DNS server.
