Opened 4 months ago

Last modified 7 weeks ago

#5537 new enhancement

Turn Radius responses into Radius options

Reported by: tomek Owned by:
Priority: low Milestone: Kea1.4-final
Component: hook-radius Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

The RadiusDesign covers implementing communication with Radius and using the responses to assign specific IP address or use specific address pool. The responses will contain certain Radius attributes that Kea could represent as Radius options. Once #5536 is done, we could add an optional mechanism to insert Radius option with the attributes being received.

On a related note, in typical deployment it is the relay that communicates with Radius, as described in RFC4014 or RFC7037. Our solution is somewhat uncommon, but valid. With the feature described in this ticket, both scenarios (relay communication and server communication) could be handled in uniform way.

Subtickets

Change History (1)

comment:1 Changed 7 weeks ago by tomek

  • Milestone changed from Kea1.4 to Kea1.4-final

As discussed on 2018-04-26 call, moving low and some med priority tickets to 1.4-final.

Note: See TracTickets for help on using tickets.