Having this feature would eliminate any use of vyatta-postconfig-bootup.script for me, which would lead to a "clean" vyos installation again.

I am not sure, if I should update here or at github. I did some tests and fixes with my PR. Now generate and show seem to work fine.

Adding a dummy interface to VRF:

Adding interfaces to VRFs seems to be a bit of a hazzle:

I created a pull request for those features: https://github.com/vyos/vyos-1x/pull/238
It is still work in progress, as I was not able to test it (yet).

Hi @rps ,
Very good summary of what is needed. I think what you state fits perfectly in our (and most) uses cases. We need to sync RAs with VRRP state, and we would need to use a "virtual IP" like fe80::1 to be announced to neighbors as the default gateway.
So for me makes absolutely sense, thanks for your effort!
If you need any help defining/testing, just let me know!

Quick win :) - you find the latest rolling to be fixed

thanks for the quick fix!

Yes, closing.

Thank you @jestabro. I see now, I didn't get that sentence. So then I guess this task can be closed?

Issue introduced in T640 when we removed recommended packages. vyatta-op had a missing dependency on rsync.

The 'showConfig' op is not considered ready for 1.2.5, and specifically json configFormat is not yet backported to crux. Regarding the output in the blog, see the line following the screen shot: "In reality that output is not pretty-printed, though we may add a flag for it. "

Checked on vyos-1.2.5-epa1:

@c-po can you look https://github.com/vyos/vyos-1x/pull/236

To dust off this one...

Confirmed NTP is broken in 1.2.4 due to interface ignore wildcard statement in ntp.conf. When present NTP will never sync with time servers showing them perpetually in INIT.

Here is a solution (based from https://github.com/jansegre/dhcplib/blob/master/dhcplib/rfc.py#L225-L232):

For 1.3, i use this: https://github.com/Elbandi/vyos-1x/commit/f364770fdb5ea8b61d42cb22ca428604d9c6b1df

@Lochnair any chance you can translate this into Linux tc syntax?

Thanks! As an additional note from my testing: the check for DHCP settings in the config always returns false, even if the interface uses DHCP. This could easily be fixed by checking if the values of the node contain DHCP, but if we skip this interface it won't be brought back up, so I believe the current solution is the best, even though the DHCP check line is now redundant (I noticed you removed the check itself).

good point,
probably need to handle this via excluding such interfaces

@syncer One thing to consider. If dynamic interfaces are used and there are several thousand of them (ipoe/ppp), this will kill the server, if we try to pull this data.

Should be pretty straight forward once we have migrated vyatta-nat to XML/Python. On first glance the rewrite looks easy as it just operates on the NAT table.

it seems no additional work needed for LibreNMS so i close this one

@Viacheslav let's discuss
I think we need to implement template for the server (both SNMP based and agent-based)
Need to decide what we expose, but most likely, interfaces, VRRP, VPN metrics, etc
I also add this to collect user feedback