- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Aug 9 2021
- 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
Aug 7 2021
Aug 6 2021
@maznu
Add these lines:
Aug 5 2021
Already rewritten in 1.4 and 1.3 T3535
https://phabricator.vyos.net/rVYOSONEX21527ef4551613fe9b7eed9e4b2ce33ad46fe540
Reopen
It doesn't work properly
As I understand there are 2 bugs:
- It expected --iroute-ipv6, i.e
iroute-ipv6 2001:470:1f14:af1:: ffff:ffff:ffff:ffff::
- Something wrong with such format (ipv6 address/ ipv4 mask)
ifconfig-push 2001:470:1f14:af1::2 255.255.240.0
Aug 4 2021
I don't see this bug in 1.3.0-rc5,
Aug 3 2021
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
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#
Aug 2 2021
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
Jul 31 2021
@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
Jul 30 2021
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
Jul 29 2021
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
Jul 28 2021
Jul 27 2021
@fetzerms The feature "policy local-route" in the 1.3/1.4 only.