Auto completion should be done on a per CLI path:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feb 20 2020
Feb 19 2020
Why do we need to explicitly create the routing table? why not name the routing table entry like the VRFs name? We should try to keep the CLI as minimal as possible. More CLI nodes, more headache.
I have just pinned the VyOS 1.3-rolling branch to the official FRR 7.3 release (https://github.com/vyos/vyos-build-frr/commit/076de23ed1d951aafd48d59f6f7ea410288b5991 - which contains your fix).
A new ISO image will be available shortly (it must be more recent then vyos-1.3-rolling-202002190217-amd64.iso. Please give it a try.
Feb 18 2020
thanks for reporting this. As we always want to maintain config upgrade compatibility could you please share your full config with me so I can reproduce it?
Feb 17 2020
Feb 16 2020
As in rolling the OpenVPN is rewritten to XML/Python the backport is not easily possible, it must be completely reimplemented in the old Perl code thus we should encourage users to migrate to 1.3 rolling to get better testing.
Closing as no response and can not reproduce.
tested working on latest rolling. No BGP session reset occured.
Thanks for reporting this nasty issue. The fix is applied to rolling release starting with build: vyos-1.3-rolling-202002161021-amd64.iso
Feb 15 2020
There is a faulty delta check in interfaces-bonding.py leading to the fact that physical interfaces are not enslaved. As soon as they are enslaved all works (eth2 and eth3 in my case):
Feb 14 2020
Hello @dongjunbo what are the benefits of ocserv over the other VPN Solutions already in place?
Feb 13 2020
$ make drivers/net/ethernet/chelsio/cxgb3/cxgb3_main.i $ grep UNIQUE_ID_firmware drivers/net/ethernet/chelsio/cxgb3/cxgb3_main.i
Unfortunately I have no idea how that zone option works. I'd rather solve this by an automatic code path then specifying it on the commandline (which is now possible).