I pick this up as I did the rewrite of this whole stuff

@Viacheslav thank you for testing!

https://github.com/vyos/vyos-1x/pull/178

Wha cant the change which adds the completion helper be backported? Git best practice is you should group changes per commit. But in this commit you add the completion helper and also other regexes (BAD!)

Thanks

Can this please be splittet in a host and a port node? Only WireGuard uses this notation all other services have a dedicated port node

Personally I would keep it under the interface itself but @dmbaturin should have the final decission

If FRR has all we need we should use it - drops one additional dependency

I just have a gut feeling its better suited under the interface instead of a dedicated service. For FRR, have a look into the BFD implementation

• What other nodes will be unter the prefix tagNode?
• How would namesevrers be configured?

On the other hand it still can live in the interface directly which would spare the migrator. VLANs are a good example - I‘ve written a common function to parse it in each interface. I am not fully convinced on any implementation be it under an interface or as dedicated service.

That is definately much better then before. But it doe not fix the second problem.

Works as expected. Now I can use VyOS 1.3 on my PPPoE link(s)

Backported

As noone complained that this option is not working (and it is an extension to regular ppp) I propose to remove it.

This is not possible as it requires changing the C source code of vyatta-bash during runtime.

This should be done when rewriting the whole flow-accounting portion

An alpha version can be found here: https://github.com/c-po/vyos-1x/tree/pppoe-rewrite

aone migrator for all interfaces is sufficient (see mew bridge interface and migrator 0-to-1 in interfaces)

How is it planned to implement this in the new style configuration? As own service bound to interfaces (denest) or as part of an interface?

Thanks, should be backported to crux then as I found it there

done

Nope, I was talking about completionHelper, which is not implemented - same as constraint nodes for udp/tcp regex.

Reproducible via:

Depending on your configuration, in SNMPv3 you can limit the scope, in SNMPv2 we export all.

VyOS 1.2.3 has agentx enabled:

Hmm the way I have understood SNMP this is not a VyOS issue. VyOS only deliveres the MIB tree to the SNMP poller. The MIBs database must be up2date on the client side to map the OIDs to their specific values.