@xrobau You have to set remote-as for peer-group or for neighbor
vyos@r4-1.3# set protocols bgp 65001 peer-group FOO [edit] vyos@r4-1.3# set protocols bgp 65001 neighbor 203.0.113.2 peer-group FOO [edit] vyos@r4-1.3# set protocols bgp 65001 neighbor 203.0.113.2 remote-as 65002 [edit] vyos@r4-1.3# commit [edit] vyos@r4-1.3#
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:
vyos@r4-1.3# commit [edit] vyos@r4-1.3# 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] vyos@r4-1.3#
@trae32566 Can you re-check it?
There are different outputs from "iptables" between 1.2 and 1.3:
By default:
vyos@r4-1.3:~$ 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 vyos@r4-1.3:~$
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.
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:
vyos@r4-1.3# set protocols bgp 64512 neighbor 192.168.5.5 local-as 64513 [edit] vyos@r4-1.3# set protocols bgp 64512 neighbor 192.168.5.5 remote-as 64513 [edit] vyos@r4-1.3# commit [ protocols bgp 64512 neighbor 192.168.5.5 local-as 64513 ] local-as: 64513 and remote-as: 64513 can't be the same
The original issue with the name ( type "u32") was solved.
I'll create a separate task for comm-list bug that can't be used without the "delete" option. (T3712)
Config to reproduce in 1.4
set interfaces ethernet eth1 address 2001:db8::2/64 set interfaces l2tpv3 l2tpeth1010 address '192.168.37.2/27' set interfaces l2tpv3 l2tpeth1010 encapsulation 'ip' set interfaces l2tpv3 l2tpeth1010 source-address 2001:db8::2 set interfaces l2tpv3 l2tpeth1010 peer-session-id '100' set interfaces l2tpv3 l2tpeth1010 peer-tunnel-id '200' set interfaces l2tpv3 l2tpeth1010 remote 2001:db8::1 set interfaces l2tpv3 l2tpeth1010 session-id '100' set interfaces l2tpv3 l2tpeth1010 tunnel-id '200'
commit
Traceback (most recent call last):
File "/usr/libexec/vyos/conf_mode/interfaces-l2tpv3.py", line 105, in <module>
apply(c)
File "/usr/libexec/vyos/conf_mode/interfaces-l2tpv3.py", line 94, in apply
l = L2TPv3If(**l2tpv3)
File "/usr/lib/python3/dist-packages/vyos/ifconfig/interface.py", line 264, in __init__
self._create()
File "/usr/lib/python3/dist-packages/vyos/ifconfig/l2tpv3.py", line 46, in _create
self._cmd(cmd.format(**self.config))
File "/usr/lib/python3/dist-packages/vyos/ifconfig/control.py", line 51, in _cmd
return cmd(command, self.debug)
File "/usr/lib/python3/dist-packages/vyos/util.py", line 161, in cmd
raise OSError(code, feedback)
FileNotFoundError: [Errno 2] failed to run command: ip l2tp add tunnel tunnel_id 200 peer_tunnel_id 200 udp_sport 5000 udp_dport 5000 encap ip local 2001:db8::2 remote 2001:db8::1
returned:
exit code: 2PR for current https://github.com/vyos/vyos-1x/pull/949
PR for 1.3 https://github.com/vyos/vyatta-cfg-quagga/pull/86
add option "solo" for neighbor.
PR for 1.3 https://github.com/vyos/vyatta-cfg/pull/40
It was a lot of problems with high CPU utilization with these mibs T1705.
https://forum.vyos.io/t/high-cpu-usage-by-bgpd-when-snmp-is-active
@fetzerms The feature "policy local-route" in the 1.3/1.4 only.
We only have source routing now:
I can confirm that happens only if you ssh via vrf and set static route6 in default vrf
And it works without debug, if you stop vyos-configd service
I can't reproduce it in any version.
Let's check what is different, and why only in your case do you have a problem, but other users never have this issue.
The latest .deb with fixed in pr above
Interesting. But I never saw it.
Can you check the latest rolling? I have no other ideas yet.
I think it is already fixed in T3674
@ramaxlo You can try to set this workaround:
In T3694#98436, @ernstjo wrote:How to get the debug logs? I already enabled debug mode.
Tested configuration:
set interfaces ethernet eth1 address '192.0.2.1/24' set interfaces ethernet eth1 address 'dead:beef:b004:3::1/64' set interfaces tunnel tun0 address '2a0f:5707:b004:3::1/64' set interfaces tunnel tun0 encapsulation 'sit' set interfaces tunnel tun0 parameters ip ttl '255' set interfaces tunnel tun0 parameters ipv6 hoplimit '255' set interfaces tunnel tun0 remote '192.0.2.2' set interfaces tunnel tun0 source-address '192.0.2.1' set protocols static route6 cafe:e1f:b046:1::/64 next-hop 2a0f:5707:b004:3::2 set protocols static route6 cafe:e1f:b046:c000::/56 next-hop 2a0f:5707:b004:3::2
Try to touch frr debug to collect more information
https://docs.vyos.io/en/latest/debugging.html#frr
@ernstjo Can you share an example of your tunnel interface?
I don't understand yet how to reproduce it.
If you delete routes and add again, do you get the same result?
Will be available in the next 1.3 beta release.
PR https://github.com/vyos/vyatta-cfg-quagga/pull/85
set protocols static table 1 route6 ::/0 next-hop fe80::11 interface eth0 commit
To reproduce, without the "interface" option
set protocols static table 1 route6 ::/0 next-hop fe80::11 commit
Also, the bug still present, fix for which I sent above in diff
vyos@r5-1.3-myb# compare
[edit interfaces]
+vxlan vxlan0 {
+ mtu 1430
+ remote fe80::2
+ source-address fe80::3
+ source-interface eth0
+ vni 0
+}
[edit]
vyos@r5-1.3-myb# commit
WARNING: RFC7348 recommends VXLAN tunnels preserve a 1500 byte MTU@c-po It seems doesn't work
@Scoopta Provide please example of configuration with every task.
If it a possible example of frr, for what you get and what you expected.
Can you send more examples how it looks like in podman cli?
Which parameters do you set, and how to check if it is successfully applied?
In T3686#98142, @Scoopta wrote:My config which breaks
set interfaces openvpn vtun2 device-type tap set interfaces openvpn vtun2 mode site-to-site
For first we have to solve this bug T3689
In my test configuration all works fine.
set interfaces bridge br0 address '10.0.0.1/30' set interfaces bridge br0 member interface vtun0 set interfaces openvpn vtun0 device-type 'tap' set interfaces openvpn vtun0 encryption cipher 'aes128' set interfaces openvpn vtun0 mode 'server' set interfaces openvpn vtun0 server subnet '192.168.1.0/24' set interfaces openvpn vtun0 tls ca-cert-file '/config/auth/openvpn/ca.crt' set interfaces openvpn vtun0 tls cert-file '/config/auth/openvpn/central.crt' set interfaces openvpn vtun0 tls dh-file '/config/auth/openvpn/dh.pem' set interfaces openvpn vtun0 tls key-file '/config/auth/openvpn/central.key'