Not so Stuby Tunnels

[DanPartelly]

Some stars aligned, and this (see below) seems to work OK. It marks it as [stub] :P Can we count it will stay the same in future ?

links:
  - group: tunnels
    members: [r1, r2, r3, r4]
    prefix: mgre
    type: tunnel
    name: mGRE R1-R2-R3-R4

[ipspace]

What you did created four separate links with one router attached to each link (that's why they're all stubby). The only reason it works is because you used a named prefix, so all four links got the same base prefix, and ID-based allocation (usually used on stub links) did the trick. And yes, I don't see any reason to change that behavior any time soon.

I would, however, define a single link with four routers attached to it.

[DanPartelly]

Thank you.

I did that because it didn't crossed my mind that if I mark a multiaccess link as a tunnel it would work. So I made an assumption, and as it's often the case with assumptions I fucked it up. However, I think this behavior is worth documenting.

Custom prefixes are intentional. Those will become later part of a larger topology, and I have no inclination to count devices. With custom prefixes, the custom supplementary config files I have to apply can be written/modified from head, with no external reference, and will withstand a lot of topology modifications (assuming those devices are the only clients)