Bug 43309 – No possibility to assign VLANs based on SSIDs

Bug 43309 - No possibility to assign VLANs based on SSIDs


Summary:	No possibility to assign VLANs based on SSIDs

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Radius
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-01-06 14:31 CET by Valentin Heidelberger
Modified:	2021-05-14 16:38 CEST (History)
CC List:	4 users (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Valentin Heidelberger

2017-01-06 14:31:27 CET

It is currently not possible in UCS to assign VLANs to SSIDs, so that clients authenticating to an AP which in turn authenticates them with the RADIUS on UCS end up with a previously configured VLAN tag.
According to the RADIUS mailing list, such a thing would be possible with a configuration like this in the post-auth section of the right virtual server in /etc/freeradius/sites-available:

if (&Called-Station-Id =~ /:SSID$/) {
        update reply {
            &Tunnel-Type := VLAN
            &Tunnel-Medium-Type = IEEE-802
            &Tunnel-Private-Group-Id = "20"
        }
    }
    elsif (&Called-Station-Id =~ /:SSID$/) {
        update reply {
            &Tunnel-Type := VLAN
            &Tunnel-Medium-Type = IEEE-802
            &Tunnel-Private-Group-Id = "40"
        }
    }

Comment 1 Stefan Gohmann

2019-01-03 07:19:58 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.

Comment 2 Valentin Heidelberger

2019-01-03 14:13:00 CET

Still relevant for UCS 4.3

A radius config for this was documented in the German blog:
https://www.univention.de/blog-de/2017/10/wlan-fuer-schultraeger-byod-gyod/

Comment 3 Ingo Steuwer

2021-05-14 16:38:18 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.