If you use interface as a peer, you have to use interface peer-group
in FRR
r1(config-router)# neighbor eth1 interface peer-group
VyOS
vyos@r1# set protocols bgp 65001 neighbor eth1 interface peer-group Possible completions: <text> peer group for this peer
I did some modification to fix this problem.
https://github.com/vyos/vyos-build/pull/386
Adding geo-ip and fqnd too:
https://github.com/vyos/vyos-1x/pull/2188
@csszep Yes it is expected, IPv6 has no sysctl and requires the nftables rule to function. The nftables execution is slightly slower, so there's no benefit to change it for IPv4.
This was resolved, and present in 1.3.0.
This is superseded by T5528.
This possible corruption on system update is resolved in the commit; further investigation of the effect of coreutils behavior change will be in subtask T5527.
PR is created https://github.com/vyos/vyos-build/pull/385
Cherry-pick for 1.3.4 https://github.com/vyos/vyos-1x/pull/2187
It cannot reproduce in the current 1.3 VyOS 1.3-stable-202308240442
vyos@r1:~$ sudo sysctl -a | grep send_redire net.ipv4.conf.all.send_redirects = 1 net.ipv4.conf.default.send_redirects = 0 net.ipv4.conf.dum0.send_redirects = 0 net.ipv4.conf.eth0.send_redirects = 0 net.ipv4.conf.eth1.send_redirects = 0 net.ipv4.conf.eth2.send_redirects = 0 net.ipv4.conf.eth3.send_redirects = 0 net.ipv4.conf.eth4.send_redirects = 0 net.ipv4.conf.eth5.send_redirects = 0 net.ipv4.conf.eth6.send_redirects = 0 net.ipv4.conf.lo.send_redirects = 1 vyos@r1:~$ vyos@r1:~$ vyos@r1:~$ reboot now
It could be added the same way https://github.com/vyos/vyatta-cfg-quagga/commit/db2f0bbeb375e0d568ef4740bad2b50690cd8644 (if required)
If not, just close it. Already have in 1.4
This also affects latest rolling release as of 1.4-rolling-202308240020 which is available @vyos.io
We won't extend the old Perl code anymore (for 1.3.x) https://github.com/vyos/vyatta-cfg-qos/pull/19
Implemented for 1.4
Fixed on this op-mode commands were introduced on PR https://github.com/vyos/vyos-1x/pull/2186
Corrections and improvements were applied. Please check on next rolling release
Provide some logs and examples of configuration.
Do you use SNMP?
PR for 1.3.4 https://github.com/vyos/vyatta-cfg-quagga/pull/101
Works fine VyOS 1.3-stable-202308240442
vyos@r1# run generate wireguard client-config c1 interface wg0 server 203.0.113.1 address 10.0.0.2/32
@dsummers Could you re-check? Should be fixed in https://github.com/PowerDNS/pdns/pull/12203
We didn't get the requested information.
Reopen it if it is required with steps to reproduce and some output.
Implemented, checked in VyOS 1.3-stable-202308240442
vyos@r1# set policy local-route Possible completions: > local-route IPv4 policy route of local traffic > local-route6 IPv6 policy route of local traffic
@Rhongomiant could you re-check it? Clear conntrack table between tests
Not reproduced
Reopen it with instance details if required
Should be fixed, needs testing.
I tried on VyOS 1.4-rolling-202308300021 .
PR1 didnt seem to have any affect on this night build:
Duplicate
Available for 1.4
It's trying to find the template in /etc/, but it is located in /opt/vyatta/etc
vyos@r1:~$ generate vpn x509 key-pair testone
Can't open /etc/key-pair.template for reading, No such file or directory
140089191929024:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('/etc/key-pair.template','r')
140089191929024:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:
vyos@r1:~$ cat /etc/key-pair.template
cat: /etc/key-pair.template: No such file or directory
vyos@r1:~$
vyos@r1:~$ sudo find / -name key-pair.template
/boot/rw/opt/vyatta/etc/key-pair.template
/opt/vyatta/etc/key-pair.templateImpossible to expand with the old firewal l backend
There is a warning that doesn't now you to do it.
vyos@r1# set fire group address-group foo add 10.1.0.2-10.1.0.3
[edit]
vyos@r1# set fire group address-group foo add 10.1.0.2-10.1.0.5
[edit]
vyos@r1# compare
+firewall {
+ all-ping enable
+ broadcast-ping disable
+ config-trap disable
+ group {
+ address-group foo {
+ address 10.1.0.2-10.1.0.3
+ address 10.1.0.2-10.1.0.5
+ }
+ }
+ ipv6-receive-redirects disable
+ ipv6-src-route disable
+ ip-src-route disable
+ log-martians enable
+ receive-redirects disable
+ send-redirects enable
+ source-validation disable
+ syn-cookies enable
+ twa-hazards-protection disable
+}
[edit]
vyos@r1# commit
[ firewall group address-group foo ]
Address 10.1.0.2 exists in more than one configuration enrty