Wired Guest Network
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 04:53 PM
How have you implemented guest access on your wired network? I currently have a fully segregated guest network on wireless, but nothing in place on wired. I would like to implement it on wired, but it needs to be able to switch to staff access based on domain credentials (derived from Windows if possible).
So, ideally:
So, ideally:
- User plugs into network and doesn't have a domain account (or is in a non-staff OU) they get internet only access.
- User plugs into network and has logged onto their laptop with domain accepted credentials they get staff access (internet and internal resources).
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 09:54 PM
Hello Terren,
If you are using EXOS, you could try Netlogin feature.
http://documentation.extremenetworks.com/exos/EXOS_21_1/Netlogin/c_overview.shtml
Best regards,
If you are using EXOS, you could try Netlogin feature.
- For guest user: you could use Web-based authentication and associate one vlan for guest user only.
- For staff user: you could use 802.1X authentication.
http://documentation.extremenetworks.com/exos/EXOS_21_1/Netlogin/c_overview.shtml
Best regards,
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 07:27 PM
We do this using Extreme Policy and NAC. If you are an unknown computer, not owned by the school and not in AD, you get redirected to a registration page. You will then get an internet only policy that restricts you to the internet. If you have a campus owned computer, you might be doing .1x or MAC AUTH based on groups, AD groups, end-system groups, location groups etc... The sky is the limit.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 07:27 PM
You can create a network resource that maybe all of your servers are on. 10.0.1.0/24
You can then block all access to that network resource, but use IP socket destination to punch a hole through it, say you have 10.0.1.4 and it's a DNS server. You could create a rule to open up socket 53. Anyway, you will have to make it your own and these things very greatly!
You can then block all access to that network resource, but use IP socket destination to punch a hole through it, say you have 10.0.1.4 and it's a DNS server. You could create a rule to open up socket 53. Anyway, you will have to make it your own and these things very greatly!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2017 07:27 PM
If possible, could you share your internet only policy? There's one that was pre-built in my Policy but it does not restrict web traffic to internal resources.
