@bbs2web you can try use sysctl params from set

Xml for interface-definitions for commands set protocol mpls
https://github.com/sever-sever/vyos-1x/blob/current/interface-definitions/protocols-mpls.xml.in

I think we can close this task.
Nothing like that has happened in the last few months.

@elbuit

vyos@mpls# sudo nft list table nat
table ip nat {
	chain PREROUTING {
		type nat hook prerouting priority -100; policy accept;
		counter packets 0 bytes 0 jump VYATTA_PRE_DNAT_HOOK
	}

@elbuit
Rolling is support nft now.

vyos@mpls:~$ sudo nft -v
nftables v0.9.0 (Fearless Fosdick)

PR https://github.com/vyos/vyos-1x/pull/203
Adding commands for show mpls

Service custom don't support 2 ddns entries now.
It overwrite login/pass to (login02) for each custom service

First tests for MPLS.
Latest rolling releases is supported it.

Update
The problem was resolved by manually removing the interfaces from the file /config/config.boot (section flow-accounting)

@bbabich If router A and router B connected via iBGP you need use nexthop-self

Hi @bbabich
How we can reproduce this bug?
I tested with 55 bgp-sessions. Each with its own unique filter. All filters applied as needed.
Without filters I announced 111 routes.
With filters per session I export 1 route to each peer.

@wcktklwn Can you provide vyos config for dynamic service and config ddclient.conf
Which lines do you add manually?

It fixed in 1.3 version. With "next-hop-interface "

In the latest VyOS 1.3-rolling-201912261106 all work fine.

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/

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

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

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

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

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?

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

I check it in latest rolling releases and it work fine (ipv4 and ipv6).

In the VyOS 1.2-rolling-201912090217 and VyOS 1.3-rolling-201912090242 all work fine

Over the past 3 months of rolling releases, I haven't seen this problem in KVM with virtio.

@hagbard An inactive route in this case can be resolved using the command "ebgp-multihop 10".

In the latest rolling VyOS 1.3-rolling-201912090242 it work fine.
R1 advertise ipv6 routes with community 65001:666
R2 receives these routes.

Similar task https://phabricator.vyos.net/T1838

/opt/vyatta/sbin/vyatta-firewall.pl contains lines

Hi @systo
Can you describe step by step what you did not succeed?
The example below is just an example.

Confirm the problem on edit level.

I don't see this bug in the latest versions of the VyOS (VyOS 1.2-rolling-201912090217 and VyOS 1.3-rolling-201912090242).

@zsdc Maybe Incorrect file location. "ddclient.pid"

Wrong logic.
Need to return line 108 code

print (cmd.decode (). split (",", 1) [0])

Bug in latest rolling

@christopher.crews07
In you example some mistake (2 times vif-s)

This bug is fixed in latest rolling releases 1.3.
Tested on

vyos@1.3-roll# 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:

cpo@LR1.wueIII:~$ 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) .

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

If 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.