SwimGeek
SwimGeek
I think the problem is related to IPv6... ... # show interfaces wireguard wireguard wg0 { address 10.10.10.2/24 mtu 1420 peer YKDblahblahblahblahblahblahblahblahblahblah= { allowed-ips 10.10.10.1/32 endpoint vpn.atomic.ac:51820 persistent-keepalive 25 }...
Hi, about the last part of your message - the 1, 2, 3 part. This is pretty much what I did. It boots into v4 only config, and then everything...
This solves my problem. Boot with v4 config, add v6 config later. I can now reboot my router and everything works as expected. ... cat /config/scripts/post-config.d/boot.sh #!/bin/vbash source /opt/vyatta/etc/functions/script-template configure...
Seems like it's not ready yet: https://m3.material.io/develop/web "Web support is planned"
Hi And the idea to move some of the RPKI load to extra cpu core?
Hi, all 55k routes had the same ~prepend, and if you prepend that you cant find the routes in WHOIS. If you take away the ~prepend, you can find many...
CPU load went crazy at that point, but we don't really know what went wrong.
At the point that log event gets generated, do you know the reason for it failing? That would be useful info to have even in non debug mode.