- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 2 2021
May 1 2021
Apr 30 2021
This requires a fix to https://github.com/FRRouting/frr/issues/8403 first
Apr 29 2021
Looks good on 1.4-rolling-202104280417:
Looks good on 1.4-rolling-202104280417 and 1.3-rolling-202104280642:
A possible reason it tried to remove " neighbor 10.0.0.2 remote-as 65002" after " neighbor 10.0.0.2 interface peer-group foo"
But if we delete " neighbor 10.0.0.2 interface peer-group foo" it also delete and "" neighbor 10.0.0.2 remote-as 65002"
So it can't delete this string
Apr 28 2021
PR's for Equuleus, save frr configurations.
https://github.com/vyos/vyatta-cfg/pull/39
https://github.com/vyos/vyatta-cfg-quagga/pull/75
For crux we use parser of " ipsec statusall {peer}"
Output if IKE established and esp SA not installed
vyos@r2-lts:~$ sudo ipsec statusall peer-192.0.2.1-tunnel-vti | grep Connections -A 50 Connections: peer-192.0.2.1-tunnel-vti: 192.0.2.2...192.0.2.1 IKEv1 peer-192.0.2.1-tunnel-vti: local: [192.0.2.2] uses pre-shared key authentication peer-192.0.2.1-tunnel-vti: remote: [192.0.2.1] uses pre-shared key authentication peer-192.0.2.1-tunnel-vti: child: 0.0.0.0/0 === 0.0.0.0/0 TUNNEL Security Associations (2 up, 0 connecting): peer-192.0.2.1-tunnel-vti[3]: ESTABLISHED 12 minutes ago, 192.0.2.2[192.0.2.2]...192.0.2.1[192.0.2.1] peer-192.0.2.1-tunnel-vti[3]: IKEv1 SPIs: 0ab8c2ee5815350e_i 271fba46aab245da_r*, pre-shared key reauthentication in 29 minutes peer-192.0.2.1-tunnel-vti[3]: IKE proposal: AES_CBC_256/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
PR for Equuleus https://github.com/vyos/vyos-1x/pull/823
Apr 27 2021
@joolli Re-check please it in any Linux system with the option "-I "
Is it different?
ping -I dum0 10.0.12.40
Works perfect in VyOS 1.4-rolling-202104260417
sa_data wrong format
vyos@r6-roll:~$ show vpn ipsec sa [[b'peer-203.0.113.2-tunnel-vti', 'up', '4m33s', '168B/168B', '2/2', '203.0.113.2', 'N/A', 'AES_CBC_256/HMAC_SHA1_96/MODP_1024'], ['peer-192.0.2.2-tunnel-vti', 'down', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A']] Connection State Uptime Bytes In/Out Packets In/Out Remote address Remote ID Proposal ------------------------------ ------- -------- -------------- ---------------- ---------------- ----------- ---------------------------------- b'peer-203.0.113.2-tunnel-vti' up 4m33s 168B/168B 2/2 203.0.113.2 N/A AES_CBC_256/HMAC_SHA1_96/MODP_1024 peer-192.0.2.2-tunnel-vti down N/A N/A N/A N/A N/A N/A vyos@r6-roll:~$
To reproduce the bug, we need to add a source nat rule first.
configure set nat source rule 100 outbound-interface 'eth0' set nat source rule 100 source address '192.168.0.0/24' set nat source rule 100 translation address masquerade commit save exit
Then if we try to list the nat tables with iptables iptables -t nat -L, we will get error like table 'nat' is incompatible, use 'nft' tool.
Next, if we use podman to create a container sudo podman run -d ubuntu:latest, podman will return the error because it will look up nat rules with iptables.
Work as expected on 1.4-rolling-202104260417
vyos@R1:~$ show dhcpv6 server leases IPv6 address State Last communication Lease expiration Remaining Type Pool IAID_DUID ------------------ ------- -------------------- ------------------- ----------- ----------------- ----------- ----------------------------------------------------- 2001:db8:290::/64 active 2021/04/23 14:52:48 prefix delegation VyOS-DHCPv6 00:00:00:00:00:01:00:01:28:15:9b:bd:50:00:00:06:00:00 2001:db8:3456::15b active 2021/04/27 05:07:51 2021/04/27 17:07:51 10:28:27 non-temporary VyOS-DHCPv6 00:00:00:00:00:01:00:01:28:15:9b:bd:50:00:00:06:00:00
Apr 26 2021
Fixed in
@Yuanandyuan Can you reproduce it with vyos cli? Or it raw podman commands?
Apr 25 2021
Retested this with VyOS 1.3.0-rc3 and the bahavior is the same.
Turns out the example config has a typo. Issue is reproducible by:
Analysing the provided configuration file has shown that this is unrelated to the change. The supplied configuration used a non existing route-map/prefix list on the CLI. As this is now properly validated for existence the error was triggered.
How were you be able to set this on the CLI?
Apr 24 2021
Apr 23 2021
Looks good on 1.3-rolling-202104220921:
Looks good on 1.3-rolling-202104220921 (including migration from 1.2.7).
Discussed on slack channel (#lobby) with @christian Poessinger. He has the relevant original configuration file in PM.