- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Does Meraki accept RADIUS Tunnel-Private-Group-Id attribute being VLAN name and not VLAN ID ?
Dear Meraki community,
I am considering using OneLogin RADIUS service for my company wired and wireless authentication.
The problem being that I can only configure the RADIUS attribute Tunnel-Private-Group-Id value to be the matching role name of my user and not the role VLAN ID.
So for example, if I'm assigned the HR role on OneLogin, the RADIUS reply message will be the following
Tunnel-Private-Group-Id:0 = "HR" Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IPv4 Filter-Id = "HR;Social Media"
Can Meraki properly interpret this RADIUS reply message and assign the "HR" VLAN declared in my Dashboard ?
Thank you all in advance 🙏
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So the answer is no to tunnel-group-id, but I see there is Filter-Id in the response. You can use that to assign a Group Policy to the user/device, which in turn can specify a VLAN. Maybe that approach will work for you?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So the answer is no to tunnel-group-id, but I see there is Filter-Id in the response. You can use that to assign a Group Policy to the user/device, which in turn can specify a VLAN. Maybe that approach will work for you?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, I take that back! I should know better to double check before I answer!
It looks like tunnel-group-id is honoured, but it needs to be the VLAN number, not the name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you @jdsilva and @PhilipDAth @for your answers !
I’ll probably stick with the group policy through the filter-id.
feature request might take a while at OneLogin.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To add to @jdsilva response further - Meraki has no concept of a VLAN name. So you can only use id's (and group policy names).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hallo Guys.
Me by working on a project using a radius that is combined with the radius of the server.
Type radius of what server is suitable for use with Cisco Meraki. Does Freeradius be able to do "Tunnel-Private-Group-ID" in Cisco connection with the Meraki?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>Does Freeradius be able to do "Tunnel-Private-Group-ID" in Cisco connection with the Meraki?
Yes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thanks for your answers @PhilipDAth .
btw do you have some tutorial or documentation configure tunnel-private-group-id on freeradius ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Google is thick with answers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi BeepBeep1,
check out firmware version 15.x for MS.
With this version VLAN Profiles are introduced. With this feature you can use named vlans via RADIUS Tunnel-Private-Group-Id attribute.
