I'm not in the VyOS core team so I'm not able to make direct decisions on the resolution, but as I see it, there are several possible ways to approach this.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Mar 10 2020
Max positive value for Integer32 = 2147483647
Max negative value = -2147483648
Mar 9 2020
I'd like to know what the long term plan is here. How are "small time" developer supposed to be able to build the kernel related packages? I was in the middle of testing some change to wireguard, but now everything is on hold because I can't build the current kernel anymore without a significant effort. I'm open to help but I would need to know what the plan is for builds without Jenkins.
Thanks for the quick fix c-po, I noticed this also needs to be fixed in /usr/libexec/vyos/op_mode/reset_openvpn.py in case someone runs for example:
Hi @SteveP , VyOS has own CLI for ping command, use ping and <TAB>
vyos@R1:~$ ping 1.1.1.1 Possible completions: <Enter> Execute the current command adaptive Ping options allow-broadcast audible bypass-route count deadline flood interface interval mark no-loopback numeric pattern quiet record-route size timestamp tos ttl verbose
Good topic. Hopefully can be done as soon as possibly :)
Mar 8 2020
sorry for this oversight.
is this still actual?
i propose to close it
VRF route leaking needs to be added to CLI. Routes can be leaked using:
already resolved in latest rolling due to rename of the node from secret to key.
Fixed via T2089