I don't see the repo for "bullseye"
http://repo.powerdns.com/

PR for current https://github.com/vyos/vyos-1x/pull/967

Fixed, thanks.

It seems impossible to delete network and container and add a new one in one commit

Another bug.
From time to time I get errors in debug mode ("touch /tmp/vyos.frr.debug" and "sudo systemctl stop vyos-configd") when changing lsp-mtu size

vyos@r1-roll# set protocols isis lsp-mtu 1308
[edit]
vyos@r1-roll# commit
[ protocols isis ]

Similar task T2315, also there is bug related T1976, etc.
It should be a migration script that determines ip/ipv6 neighbor and set neighbor to properly afi.
So there is one question, how to determine which afi we should to use if we see "peer-group" in configuration?
I don't think that we can implement it in 1.3 as it uses an old codebase.

To reproduce in 1.4:

As Workaround in T3350 set raw option "config /path/to/config/file"

@fernando Thanks.

@fernando Can you check this feature in the next rolling release?

set service snmp community public client 127.0.0.1
set service snmp oid-enable route-table

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

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

• Backport configquerry.py [Done]

https://github.com/vyos/vyos-1x/commit/2aa75521a829712256c3c34685e60a9d36b33791

Maybe with FRR 8.1
In any case, we'll do more tests.

It is possible this bug.
https://github.com/FRRouting/frr/issues/9181

@dtoux Did you test it in 1.3.0-rc5?

@xrobau As I mentioned before, peer-group can't exist without peer-as/remote-as in your case remote-as should be internal. It can exist without remote-as but with "route-reflector-client" it shouldn't
You can check it with vtysh FRR:

I closed it. Can't reproduce it.
Re-open it if necessary. Just attach your vpn configuration.

The same task T1375

@maznu
Add these lines:

Already rewritten in 1.4 and 1.3 T3535
https://phabricator.vyos.net/rVYOSONEX21527ef4551613fe9b7eed9e4b2ce33ad46fe540

Reopen
It doesn't work properly

PR https://github.com/vyos/vyatta-cfg-quagga/pull/87
PR https://github.com/vyos/vyos-1x/pull/954
PR https://github.com/vyos/vyos-1x/pull/955

As I understand there are 2 bugs:

1. It expected --iroute-ipv6, i.e

iroute-ipv6 2001:470:1f14:af1:: ffff:ffff:ffff:ffff::

2. Something wrong with such format (ipv6 address/ ipv4 mask)

ifconfig-push 2001:470:1f14:af1::2 255.255.240.0

I don't see this bug in 1.3.0-rc5,

In T2851#99364, @lawrencepan wrote:

As a workaround it can help in such cases:

@xrobau You have to set remote-as for peer-group or for neighbor

[email protected]# set protocols bgp 65001 peer-group FOO 
[edit]
[email protected]# set protocols bgp 65001 neighbor 203.0.113.2 peer-group FOO
[edit]
[email protected]# set protocols bgp 65001 neighbor 203.0.113.2 remote-as 65002
[edit]
[email protected]# commit
[edit]
[email protected]#

Fixed, tested in 1.3.0-rc5

set firewall ipv6-name WAN6_IN6
set firewall ipv6-name WAN6_LOCAL6
set interfaces ethernet eth1 address '192.0.2.1/24'
set interfaces ethernet eth1 description 'FOO'
set interfaces tunnel tun1 6rd-prefix '2607:FA48:6ED8::/45'
set interfaces tunnel tun1 6rd-relay-prefix '24.225.128.0/17'
set interfaces tunnel tun1 address '2607:FA48:6ED8:8A50::1/60'
set interfaces tunnel tun1 description 'Videotron 6rd Tunnel'
set interfaces tunnel tun1 encapsulation 'sit'
set interfaces tunnel tun1 firewall in ipv6-name 'WAN6_IN6'
set interfaces tunnel tun1 firewall local ipv6-name 'WAN6_LOCAL6'
set interfaces tunnel tun1 mtu '1480'
set interfaces tunnel tun1 multicast 'disable'
set interfaces tunnel tun1 parameters ip ttl '255'
set interfaces tunnel tun1 remote '192.0.2.2'
set interfaces tunnel tun1 source-address '192.0.2.1'

Commit:

[email protected]# commit
[edit]
[email protected]# sudo ip tunnel show
sit0: ipv6/ip remote any local any ttl 64 nopmtudisc 6rd-prefix 2002::/16
tun1: ipv6/ip remote 192.0.2.2 local 192.0.2.1 ttl 255 tos inherit 6rd-prefix 2002::/16
[edit]
[email protected]#

@trae32566 Can you re-check it?

There are different outputs from "iptables" between 1.2 and 1.3:

By default:

[email protected]:~$ sudo netstat -tulpn | grep 161
udp        0      0 0.0.0.0:161             0.0.0.0:*                           1405/snmpd          
udp6       0      0 :::161                  :::*                                1405/snmpd          
[email protected]:~$

After rebooting router starts with a clean routing configuration.
After that, it loads/commits configuration from /config/config.boot file.
It can be a cause, needs more tests.
It will be must impossible to get another behavior.

PR for current version https://github.com/vyos/vyos-1x/pull/952

@kroy Can you re-check it with your environment? I can't reproduce it in 1.3.0-rc5.

@ciprian.craciun

On VyOS 1.2-rolling-201910180117, setting ip source-validation loose seems to have the same outcome as setting it to disable, i.e. results in rp_filter = 0.

What do you expect to see here?

Fixed in T2745

PR for 1.3 https://github.com/vyos/vyos-1x/pull/950

it should be timeout ~1.8 sec between adding ipv6 address and create l2tp interface

By default, FRR uses all neighbors in afi ipv4.
This behavior can be disabled with:

Large community format:

"1:2:3"
"1:2:3 5:6:7"
"4123456789:4123456780:4123456788"
"^5:.*:7$"

As I see it's already fixed:

[email protected]# set protocols bgp 64512 neighbor 192.168.5.5 local-as 64513
[edit]
[email protected]# set protocols bgp 64512 neighbor 192.168.5.5 remote-as 64513
[edit]
[email protected]# commit
[ protocols bgp 64512 neighbor 192.168.5.5 local-as 64513 ]
local-as: 64513 and remote-as: 64513 can't be the same