You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gateway need to setup route table entries that correspond to the defined micronets.
Currently, the route table entries are assumed to be setup on the gateway ahead-of-time.
One question that needs to be answered is whether the gateway needs to be able to dictate/designate what subnets are allocatable - either by designating an allocatable network to be subnetted or a list of subnets that can be allocated, or perhaps another method.
The text was updated successfully, but these errors were encountered:
Design decision point here: The json that's sent to define the subnets/devices for DHCP (and also for switch flows currently) could also be used to setup the route table entries. Should we just setup the route tables off the same rest endpoint/json format or should we define a new endpoint for route table control?
The gateway need to setup route table entries that correspond to the defined micronets.
Currently, the route table entries are assumed to be setup on the gateway ahead-of-time.
One question that needs to be answered is whether the gateway needs to be able to dictate/designate what subnets are allocatable - either by designating an allocatable network to be subnetted or a list of subnets that can be allocated, or perhaps another method.
The text was updated successfully, but these errors were encountered: