The neighbor interface section needs to be updated
It was in the old template.
https://github.com/vyos/vyos-1x/commit/570886631deae3de8c38ea4ff70710e7a4858cbd#diff-c8405ef7cc0b5938bde66328e60f83c3cdc8d47f26a59bf86d646a63d1d4e5a7R512
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jan 18 2021
Further debugging revelead it's a problem inserting the VRF BPF code, but I wonder why systemd does not restart the service one more time, then it works.
Can you provide the full configuration? Or re-test it on the latest rolling release?
What is the IP address 10.64.0.1?
On 1.3-rolling-202101061750 has changed to kernel 5.10,
Put in a PR for this request.
Jan 17 2021
Fixed
vyos@r5-roll:~$ show ntp
remote refid st t when poll reach delay offset jitter
==============================================================================
*194.0.5.123 85.199.214.102 2 u 4 64 3 39.557 -2.748 2.504
+167.86.115.96 235.106.237.243 3 u 39 64 3 45.816 5.476 0.830
+195.128.100.150 131.188.3.222 2 u 4 64 3 43.219 -1.425 1.734
vyos@r5-roll:~$
vyos@r5-roll:~$ show versionI found a workaround (persists across reboots and upgrades):
cat <<'EOF' >/config/scripts/vyos-preconfig-bootup.script #!/bin/bash
Fixed in VyOS 1.4-rolling-202101171022
This actually also happens for BGP which will confuse users
vyos@vyos# set protocols bgp 100 neighbor 1.1.1.1 remote-as internal
'internal' is not a valid integer numberSTPBridgeIf has been decomissioned
Could you please try the latest 1.3 beta version or 1.4 rolling from https://downloads.vyos.io ?
Thank you @craterman for starting testing of our new BGP implementation.
Jan 16 2021
Fixed, VyOS 1.3-beta-202101160442
@maznu Can you re-check that all work as expected?
Fixed in VyOS 1.4-rolling-202101160747 and VyOS 1.3-beta-202101160442
Better document improvement
If you could extend the smoketest that would be even better, local test is okay, too
Quoted Text
If I use
Reverted to 7.3 let's wait for the fix to pop up in 7.5 FRR branch and we can try again.
Jan 15 2021
This can be fixed by copying the two profile directories you're using (/usr/lib/tuned/network-throughput and /usr/lib/tuned/network-latency) to /etc/tuned and changing the sysctl section to only contain enabled=false. Here's it working:
root@cr01a-vyos:~# diff /usr/lib/tuned/network-latency/tuned.conf /etc/tuned/network-latency/tuned.conf 13,16c13 < net.core.busy_read=50 < net.core.busy_poll=50 < net.ipv4.tcp_fastopen=3 < kernel.numa_balancing=0 --- > enabled=false root@cr01a-vyos:~# diff /usr/lib/tuned/network-throughput/tuned.conf /etc/tuned/network-throughput/tuned.conf 10,16c10 < # Increase kernel buffer size maximums. Currently this seems only necessary at 40Gb speeds. < # < # The buffer tuning values below do not account for any potential hugepage allocation. < # Ensure that you do not oversubscribe system memory. < net.ipv4.tcp_rmem="4096 87380 16777216" < net.ipv4.tcp_wmem="4096 16384 16777216" < net.ipv4.udp_mem="3145728 4194304 16777216" --- > enabled=false
Do I need to test the image before closing the task? I'm on a older image version and I manually applied the patch which works. Otherwise I'd need to upgrade the image which I won't have time for in the near future.
Fixed in the new bgp format, VyOS 1.4-rolling-202101150632
CLI command will be: set interfaces tunnel tun10 parameters ip no-pmtu-discovery, Also PMTU can not be changed in IPv6 sourced tunnels, a validation check has been added.
As of T3218 we no longer utilize the out-of-tree drivers as there is no performance gain. Both current and equuleus branch (1.4 and 1.3) not use the Linux Kernel stock drivers.
Backported to equuleus branch
Backported to equuleus branch
Backported to equuleus
Fixed VyOS 1.4-rolling-202101150632
set protocols isis FOO interface eth1 no-three-way-handshake set protocols isis FOO net '49.0001.1921.6800.1002.00'
If it's just because of overlay, you can merge two XML into one XML
It seems the problem not solved, "show ipv6 route" declared in different XML scripts, so one of them rewrites another.