how to block local access guest-portal
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-10-2015 03:57 AM
Hi,
We are using v2100 identify controller. We create captive portal its using our Guest.
once the Guest is connected the portal he can access my internal network also. any option to block my internal network. i need Guest only use internet.
We are using v2100 identify controller. We create captive portal its using our Guest.
once the Guest is connected the portal he can access my internal network also. any option to block my internal network. i need Guest only use internet.
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-10-2015 12:07 PM
Hi Mohhamed ,
another method would be to bring your DMZ to the second port of your Wireless Controller (even if its Virtual 2110 controller , you just assign in in your ESXi server) . Then assign this Topology as Default Topology on your Guest WLAN Service . By doing that you physically separating your Corporate network from the Guest access .
another method would be to bring your DMZ to the second port of your Wireless Controller (even if its Virtual 2110 controller , you just assign in in your ESXi server) . Then assign this Topology as Default Topology on your Guest WLAN Service . By doing that you physically separating your Corporate network from the Guest access .
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-10-2015 04:21 AM
Jasheer,
Follow the below links for configuration
https://www.youtube.com/watch?v=xQFVE3o5W6I
To block your internal networks you have to make sure your guest's authenticated roles are:
1. Setup rules to block internal subnet or
2. Contain to VLAN
Regards
Karthikeyan M.
Follow the below links for configuration
https://www.youtube.com/watch?v=xQFVE3o5W6I
To block your internal networks you have to make sure your guest's authenticated roles are:
1. Setup rules to block internal subnet or
2. Contain to VLAN
Regards
Karthikeyan M.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-10-2015 04:21 AM
Nice call out Karhikeyan.
We're in the process of migrating these Videos to GTAC Knowledge and in the near future, starting to release some new ones. Our Community Manager, Drew C. and a colleague are busy prepping them now.
We believe this will make them easier to find going forward for those who believe in a little purple in their network!
We're in the process of migrating these Videos to GTAC Knowledge and in the near future, starting to release some new ones. Our Community Manager, Drew C. and a colleague are busy prepping them now.
We believe this will make them easier to find going forward for those who believe in a little purple in their network!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-10-2015 04:05 AM
Hi Mohammed,
we have two separate SSIDs for internal and guest and both have separate VLANs. The VLAN/SSID with the guest user is not routed to our internal net.
Additional: you can use the policy rules (VNS Configuration on the Controller) to deny or allow traffic to/from the Networks.
Regards, Ralf
we have two separate SSIDs for internal and guest and both have separate VLANs. The VLAN/SSID with the guest user is not routed to our internal net.
Additional: you can use the policy rules (VNS Configuration on the Controller) to deny or allow traffic to/from the Networks.
Regards, Ralf
