Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Kea
Kea
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 445
    • Issues 445
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 71
    • Merge Requests 71
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #1660

Closed
Open
Opened Jan 22, 2021 by Wlodzimierz Wencel@wlodekMaintainer

vivso suboptions (125) are not included unless suboptions are configured with space name starting with 'vendor-' opposite situation with option 43

While I was working on #1546 (closed) I was writing forge tests, for each scenario I wanted to have example for option 43 and option 125. And we have weird problem with including suboptions to option 125.

If option is defined with vendor- prefix in space name, it will be included. If prefix vendor- is missing suboption wont be included:

working configuration:

        "client-classes": [
            {
                "name": "VENDOR_CLASS_41112", 
                "option-data": [
                    {
                        "data": "41112", 
                        "name": "vivso-suboptions"
                    }, 
                    {
                        "always-send": true, 
                        "data": "11.11.11.11", 
                        "name": "unifi-address", 
                        "space": "vendor-41112"
                    }
                ]
            }
        ],
        "option-def": [
            {
                "array": false, 
                "code": 1, 
                "encapsulate": "", 
                "name": "unifi-address", 
                "record-types": "", 
                "space": "vendor-41112", 
                "type": "ipv4-address"
            }
        ],

but If I remove vendor- or change it to anything else e.g. abc defined suboption won't be send.

Exactly opposite situation is with suboptions of option 43 working configuration:

        "client-classes": [
            {
                "name": "VENDOR_CLASS_339", 
                "option-data": [
                    {
                        "name": "vendor-encapsulated-options"
                    }, 
                    {
                        "always-send": true, 
                        "data": "123", 
                        "name": "vlanid", 
                        "space": "339"
                    }, 
                    {
                        "always-send": true, 
                        "data": "sdlp://11.11.11.11:18443", 
                        "name": "dls", 
                        "space": "339"
                    }
                ], 
                "option-def": [
                    {
                        "code": 43, 
                        "encapsulate": "339", 
                        "name": "vendor-encapsulated-options", 
                        "type": "empty"
                    }
                ]
            }
        ], 
        "option-def": [
            {
                "array": false, 
                "code": 2, 
                "encapsulate": "", 
                "name": "vlanid", 
                "record-types": "", 
                "space": "339", 
                "type": "uint32"
            }, 
            {
                "array": false, 
                "code": 3, 
                "encapsulate": "", 
                "name": "dls", 
                "record-types": "", 
                "space": "339", 
                "type": "string"
            }
        ],

If options would be configured with "space": "vendor-339" those would not be included in response.

I couldn't find statement in documentation when this prefix required, and looks like ppl on user mailing list also didn't. Easy solution would be to update ARM, but I would prefer to make configuration of those options consistnat.

Edited Jan 22, 2021 by Wlodzimierz Wencel
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/kea#1660