... | @@ -80,6 +80,10 @@ Multiple interfaces with the same VLAN should be allowed on the same system, but |
... | @@ -80,6 +80,10 @@ Multiple interfaces with the same VLAN should be allowed on the same system, but |
|
|
|
|
|
This is imagining interfaces as a 1:1 mapping with host interfaces, i.e. we'd generally name the interfaces to reflect the OS enumerated interfaces on the system (em0, em1 etc..). We'd then use salt to configure the interfaces correctly on the host, and FreeRADIUS to do the correct dynamic tagged/untagged assignment when the machine authenticates to the network..
|
|
This is imagining interfaces as a 1:1 mapping with host interfaces, i.e. we'd generally name the interfaces to reflect the OS enumerated interfaces on the system (em0, em1 etc..). We'd then use salt to configure the interfaces correctly on the host, and FreeRADIUS to do the correct dynamic tagged/untagged assignment when the machine authenticates to the network..
|
|
|
|
|
|
|
|
### mapping subnet / vlan
|
|
|
|
|
|
|
|
To expand on this, we would need the ability to define a subnet, and map it to one or more VLANs. This is really adding references from a VLAN object to the subnet objects by DN.
|
|
|
|
|
|
## Benefits:
|
|
## Benefits:
|
|
|
|
|
|
* Easy to list the interfaces of a system (just put in subtree on the machine)
|
|
* Easy to list the interfaces of a system (just put in subtree on the machine)
|
... | | ... | |