Rare project developers

[mc36 <>]

hi,
hi,

On 2/27/22 08:30, mc36 wrote:
> >        * The user doesn't have to create "export-port" stanzas for
> >            sub-interfaces explicitely
>
> right now, the dynamic range is also user managed...
> there will still be special interfaces that need to be exported,
> but my idea for them now is to allow the knob "dynamic" where we
> accept frontpanel names or mostly subifids... these are pppoe
> virtual accesses, tunnels, hairpins, and basically everything
> that is not sdn interface... we already scan the available interfaces
> for virtual-accesses, i can easily extend that part to subinterfaces too...
> the dataplanes already inform freerouter of the dynamic ranges they
> support so it seems easy-peasy as said before... that'll be the
> next pokemon to catch... :)

for this to happen, a bit stricter dataplane behavior will be enforced:
the capability, platform, portname and dynrange messages will be processed
at the beginning of the session, the dynrange will terminate this phase...
all the future messages must be sent interleaved in between these...
freerotuer will not send anything during this phase at all...
after the dynrage message, these messages wont be interpreted anymore
and freerouter will send the same messages that it's already sending...

frederic, maybe alox: please prepare the bffwd for this thing...
right now i dont get portname messages at all, the rest seems to be
already fulfilled, but you maintain the code, please ensure...

thanks,
cs