net/freeradius - custom default vlan-ID for mikrotik attributes
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 863
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 10
Description
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
- I have searched the existing issues, open and closed, and I'm convinced that mine is new.
I found these issues with a similar topic:
- When the request is meant for an existing plugin, I've added its name to the title.
Is your feature request related to a problem? Please describe.
I use the mikrotik vlan attributes in opnsense from (1) and it works as expected.
If I activate the checkbox for the VLAN-fallback from (2) all users without an entry in the radius database were assigned to my management-VLAN. I expect the reason ist the special Mikrotik VLAN attribute.
Is there also a way to assign a default VLAN id to a Mikrotik AP?
Describe the solution you'd like
I think it is only necessary to add a query in the users template to change the parameter for the fallback VLAN if the mikrotik attributes and the vlan fallback are activated in /ui/freeradius/general/index
I hope my explaination is clear and comprehensible.
Describe alternatives you've considered
- a solution similar to the dhcp option in /ui/dnsmasq/settings#dhcpoptions to create every kind of parameter you want
- Using a extern radius for auth a txt config in the worst case
Additional context
nothing for the moment, please ask if need some
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the FreeRADIUS general settings entry point, /ui/freeradius/general/index, and the users template mentioned in the request; compare the existing VLAN-fallback and MikroTik attribute handling. Confirm the desired default VLAN behavior for both options and verify that users without a RADIUS database entry receive the configured VLAN.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100