This bug is fixed in latest rolling releases 1.3.
Tested on
[email protected]# run show vers Version: VyOS 1.3-rolling-201912040242
This bug is fixed in latest rolling releases 1.3.
Tested on
[email protected]# run show vers Version: VyOS 1.3-rolling-201912040242
It work for 1.2 version (used systemd-shutdownd.service).
For 1.3 some bug with:
[email protected]:~$ sudo ip addr add "192.168.1.1/24" dev eth1.100
That command (above) don't correct for vif-s, with sudo you assign ipv4 only to one tag 8021q (Cvlan) .
[email protected]:~$ sh version Version: VyOS 1.3-rolling-201912040242
cat /opt/vyatta/share/vyatta-op/templates/reboot/node.def
help: Reboot the system
run: sudo ${vyos_op_scripts_dir}/powerctrl.py --rebootIf we replace string 108 in file /usr/libexec/vyos/op_mode/powerctrl.py
@zsdc Can you take a look at that?
Ref
https://phabricator.vyos.net/T1721
https://github.com/FRRouting/frr/pull/4602/commits
We are a little confused.
As far as I know, Bgp instance on all router's platforms always one.
And it use socket with 179 tcp port.
VRF is working on same bgp instance, but support multiple autonomous system at once.