Opened 20 months ago

Closed 4 weeks ago

#4482 closed enhancement (complete)

Provide easy access to v6 relay options from relay closest to client

Reported by: sar Owned by:
Priority: medium Milestone: Kea1.3-final
Component: classification 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

In 4265 we provided access to the v6 relay options and fields but the admin needs to know the correct nesting level for the relay they wish to access.

The nesting level works fine for either a single relay, the relay closet to the server or if the admin knows exactly where to look. However if they may have multiple relays and want to access the relay closest to the client they need to figure out the correct level. It would be more convenient for them if we were to provide one or more strings to access various relays.

One way to provide this feature would be to have a set of strings that result in the evaluate routine finding the proper relay. For example

first => closest to server (not really needed as 0 will do)
last => closest to client
last_any => start closest to client and work towards the server
first_any => start closest to server and work towards client

This was mentioned in the design document as a possible enhancement, I believe that "last" is the most useful of the possible options.

Subtickets

Change History (2)

comment:1 Changed 20 months ago by hschempf

  • Milestone changed from Kea-proposed to Outstanding Tasks

Per team meeting Apr 7, move to outstanding. Good candidate for 1.2 possibly.

comment:2 Changed 4 weeks ago by fdupont

  • Milestone changed from Outstanding Tasks to Kea1.3-final
  • Resolution set to complete
  • Status changed from new to closed

Done in #5287. Closing.

Note: See TracTickets for help on using tickets.