On current Debian Buster tose are the lsit of installed packages. I have not found the reasion why building with --apt-recommends false makes the ISO unbootable

https://github.com/vyos/vyos-build/pull/70

Maybe it's because I have multiples? Or on vlans (not that that should matter)

@fcqpl any chance to test it in your environment?

@kroy can you please share your config? I used a minimal one and everything works without issues.

This is fixed/was not present in 1.3-rolling.
1.2 is not possible to fix, the bug is in isc-dhcp which would need to be upgraded to a newer version.

Works correct on 1.3-rolling-201912190503

After some more testing, after a reboot, a tcpdump -n -i interface icmp6 on a client machine shows nothing until restarting the radvd service on the routers.

Hello @zsdc
I didn't tested it.

@c-po I can't find any usable from vyatta-ravpn now, seem we can archived it and drop from build process.

What services are provided by vyatta-ravpn?

Also fixed additional issue with multiple snmp script-extensions entry (jinja2 sort)

Hello, @elbuit!
As I see, NAT events can be recorded only by nfacctd, and therefore this is not possible with the current way to capture traffic (by NFLOG + uacctd). Fix me, if I was missed something, please.

In latest rolling 1.2-rolling-201912180217 permission problem solved, but exist one more problem with script path.
CLI allow us to choice script, which stored on '/config/user-data'

Also mention in https://phabricator.vyos.net/T1058

Thanks @Dmitry, building it again.

To avoid confusion, this will only be in the equuleus branch:
https://github.com/vyos/vyos-1x/compare/equuleus...jestabro:T1585?expand=1

Initial version for equuleus here:
https://github.com/jestabro/vyos-1x/tree/T1585

Hello @zsdc
I was also porting old style vyatta to a new one.
I've ported interface xml definition and almost finished the conf python script:

MPLS requires Linux Kernel 4.5 or higher (LDPcan be built, but may have limited use without MPLS).
Ref https://readthedocs.org/projects/frrouting-developers-guide/downloads/pdf/latest/

Hello, @elbuit !
We almost ready to release rewritten flow-accounting, and maybe we will be able to include your request into it. Can you describe more detailed what exactly records you want to have? It would be good to see an example pmacct configuration for your case.

PR https://github.com/vyos/vyatta-op/pull/32
Fix "show monitoring" command.

@sento own build 1.2.4 this is 1.2-rolling (branch current), in crux branch all works as expected.

T1350 T1820
Adding mentioned tasks which can solved

@Dmitry I had it once more on the production system - see attached log with the above loggin features enabled.

PR https://github.com/vyos/vyos-1x/pull/185

Now it works perfect.

PR https://github.com/vyos/vyos-1x/pull/184

patch will be proposed after keepalived.service modification
https://github.com/DmitriyEshenko/vyos-1x/commit/807864242773f482aa1894ca968a4396a3507187

end: sudo sh -c "VYOS_TAGNODE_VALUE='$VAR(../../@)' ${vyos_conf_scripts_dir}/router-advert.py" would have to be in /opt/vyatta/share/vyatta-cfg/templates/interfaces/ethernet/node.tag/ipv6/router-advert/node.def
I can set that statically, which removes then the benefit for the use of other passes, IPv6 RAs can be sent over quite some interfaces.

Turns out that it might not be a smart move to keep it under interfaces, as it would have to implemented within the ethernet script or if it's a separate one, it needs to be called with VYOS_TAGNODE_VALUE, otherwise there won't be a way to find out what interface needs to be configured. If placed under service or any other path, it can be integrated into the config itself e.g. set service ipv6-ra interface eth0 <more options>, set service ipv6-ra interface eth1 <more options> etc.
That would only required to parse and compare configs for 2 interfaces which can be determined from the config.

The issue can be reproduced by the following configuration:

@leacho Sorry, I didn't have the time to look deeper into that, as far as I know we currently have no workaround for it.

HI @hagbard - is there currently any work around to get the flow-accounting working on the rolling release? I raised T1838 as a similar issue. You mention above about starting pmacctd?

PR https://github.com/vyos/vyatta-op-quagga/pull/4/commits/7659873869d92c9ec6b363db7e06d2ba5b41e5f6
New syntax for commands "monitor protocol bgp enable", "monitor protocol bgp disable"

Its IKEv2, correct. Loglevel increased

@c-po this is IKEv2?
can you increase log level?

@syncer why remove 1.2? Bug should be fixed in 1.2.x bugfix releases

Actually i'm currently unable to reproduce the bug because since i removed the configuration for RPKI everything works fine. Even more interesting is that my second router with the exact same configuration does not have the problem.

It looks like the VyOS has the old command syntax.

Similar bug with FRR ref https://github.com/FRRouting/frr/pull/5450

Hi @MrXermon
Can you describe how we can reproduce this bug?
Can you show share your configuration?

current hop limit is per default set to 64, but can't be set in frr while is was/is possible for radvd. I'd propose to use the the frr options only and not using the current existing ones, that way migration will become easier since the option 'current hop limit' could be just skipped and removed during migration.
Any ideas? Or should we stay with radvd for that purpose?
I would only do it for 1.3 and not backport into 1.2-rolling.

Protocol rewrite is more then overdue now ... :)

@c-po
I get other result.
After set from your example I see correct area
FRR

tagNode has been renamed to dnssl

[edit system static-host-mapping]
vyos@vultr# set host-name test.lan inet 127.0.0.1
[edit system static-host-mapping]
vyos@vultr# commit
[edit system static-host-mapping]
vyos@vultr# save
Saving configuration to '/config/config.boot'...
Done
[edit]
vyos@vultr# show system static-host-mapping
host-name test.lan {

inet 127.0.0.1

}
[edit]
vyos@vultr#

https://github.com/vyos/vyos-1x/pull/182
We have to ship our own /etc/{init.d,default}/isc-dhcp{v4,v6}-server files since we can't overwrite the ones supplied by the debian package.