- User Since
- Oct 26 2018, 5:22 PM (50 w, 6 d)
Tue, Oct 15
Jul 24 2019
With the new versions of the open-vm-tools you can explicitly disable the pulling of the routing-table. Maybe that's a better way then disabling the whole pulling of information.
Jan 5 2019
It's possible to get the information through the FRR-cli (vtysh) as long as the function is not part of the vyos-cli with the following command:
show bgp ipv6 route-map ebgp-v6-import-as6939
Dec 28 2018
i played with different values and in my case (full table IPv6 router) the error continues during the following values:
3s, 5s, 10s, 20s, 30s
At 60s the CPU load starts to cycle between >30s full load, than it drops for a few seconds and raises again.
Dec 20 2018
Uh. That's pretty crazy! I'll play around with the option on the other VMs I am migrating from Proxmox VE to VMWare ESXi.
Yes, but only IPv6. It seems that the VMware Tools only produce the load when the BGP sessions are established. Pretty strange! Maybe some sort of memory problem?
Yep, seems to do the job.
Dec 18 2018
Looks like the cache server is pushed into the FRR configuration multiple times if the configuration get's updated.
I tested it on one of my border routers today and it seems to be working with IPv6 (dropping 692 routes because of invalid ROA state). Sadly i am unable to test IPv4 at the moment.
Dec 15 2018
Nov 27 2018
Sadly not. I can reproduce the error but i am not able to fix the problem in the code.
Nov 20 2018
Found another bug. Routes are shown via received-routes but with a wrong next-hop address (:: instead of fe80::465:1337:1 in my case) and they are not installed in the FIB.
admin@rt-1:~$ show ipv6 bgp neighbors fe80::465:1337:1 routes
The BGP seems to be working but the summary is not quite correct (State/PfxRcd is wrong).
admin@rt-1:~$ show ipv6 bgp summary
Nov 18 2018
Oct 29 2018
Listing the specific ip addresses was my legacy configuration. I removed it in the current configuration. I played a little with the interface routes and the seem to work properly on the technical side of things as i am able to ping the opposit device. But somehow the routing daemon lists routes to the peers as 'inactive' which makes the configuration unusable for me.
I rebased the router with the rc-4 image. After importing the configuration and rebooting the router a similar error occurs. The boot screen shows the error message "vyos-config: Configuration error". Looking into the configuration using 'show configuration' only shows the configuration of the wg2 interface but 'cat /config/config.boot' shows all three interfaces with correct configurations. The wireguard tool shows threee interfaces similar to the output before without any configuration.
That's intresting. I rebooted the system a few seconds ago and the tunnels dom't become active.
Oct 28 2018
this is the configuration which i need to set again after each reboot (and i remove the ip address from the interface and set it again as ip + peer address as there is no configuration option at the moment). I removed some unimportant information.