@c-po i think we not offer ntp service as of now, but i think maybe we should?

@dmbaturin leave it to you, some stuff in set interfaces uses duplex output somewhere

@dmbaturin stock quagga also missing pbr?

Welcome!

I'll take it on.

Hi, I agree too in that option 2 makes more sense IMHO. It will require more effort regarding migrations, but in the long term it seems better to me.

I'm not sure if HTML encoding is really the best thing to do, but I agree the problem exists.

This is a bit of ubunt's bug #1 by now. ;)

Do you think we should replace "+" with +-"?

@EwaldvanGeffen Good point. Do you have ideas how to implement it?

Curiously, the rewrite introduced exactly the problem @UnicronNL warned against. Entering an invalid interface at set time is only one part of the story — the worst case no set-time or commit-time check can protect against is when a once valid interface is removed, e.g. by pulling a physical or virtual NIC out of the router. Then that validation becomes a time bomb because the config will stop loading.

I did test NTP in 1.2.0 and it works now.

I verified that with the new CLI (run monitor traffic interface ... filter ...) it works.

The basic commands are working now, I suppose subsequent additions need their own tasks.

Thinking ahead: what happens when you have a very active DHCP server? Shouldn't we rate-limit reload-zones to max once/n sec ?

We can make a script that checks if service is configured and reload it if it's not then.

pdns doesn't have a built-in reload (at least not available through systemd), but i've just tested and the following works:

We can use something like
https://jpmens.net/2011/07/06/execute-a-script-when-isc-dhcp-hands-out-a-new-lease/
but reload pdns instead

In T201#14503, @c-po wrote:

any updates on this?

any updates on this?

looks like a missing check on commit. Will add this case to the new Python script.

I see the same messages in EdgeOS 1.10.3 if that helps

in VyOS-1.2.0-rolling+201805220337 with latest strongsSwan only one deprecated keyword is remaining:

I see the same lines still in log on VyOS-1.2.0-rolling+201805220337 as @c-po .
In filesystem there is no directory '/etc/lldpd.conf' but there is a '/etc/lldpd.d' and a file '/etc/init.d/lldpd.conf'

Ah, there it is! Thanks!

I just tested this one again in VyOS-1.2.0-rolling+201805220337. Setting IPSec log-modes works! commit without errors. Maybe fixed by update to latest strongSwan version.

I have running VyOS-1.2.0-rolling+201805210337 with working SNMPv3.

I think it is. In any case, it's irrelevant by now since there's no dnsmasq anymore, and pdns doesn't have this problem.

The dnsmasq equivalent is already in place I suppose.