If it reappears, please reopen.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 18 2020
Could anyone test if it's still reproducible?
Sorry for a very late reply. The script-template already takes care of everything, there is no need to use vyatta-cfg-cmf-wrapper.
With migration to nftables this is a very real possibiliy.
1.3 rolling supports it already, see https://github.com/vyos/vyos-1x/blob/current/src/services/vyos-http-api-server#L195
I wonder if it may be a good idea to make reboot and poweroff commands create a file in our own format.
The rolling release images are not signed. Never were, though I hope at some point they will be. But then again, automatically signing images, with a key stored on a public-facing machine, without a password... kinda defeats the purpose of signing.
Making it a default can make sense, if everyone agrees.
Jun 11 2020
Jun 10 2020
I'm pretty sure it's my failure to correctly handle an edge case. I'll look into it today, should be simple enough.
Jun 8 2020
I think we can safely remove it indeed.
May 19 2020
May 16 2020
Sometimes I wonder if we should just silently wrap every op mode command in sudo, at least those in the families other than show. It's hard to name a command that doesn't need sudo, and everyone (myself included!) has forgotten to add it at least once.
May 9 2020
All sounds good to me.
Apr 26 2020
Apr 16 2020
Apr 13 2020
As far as I remember, originally in our Quagga days, it was the case: nothing was advertised if it wasn't present in the RIB. So if you wanted to advertise e.g. 192.0.2.0/24 but had it split into /25's, you'd need both set protocols bgp ... network 192.0.2.0/24 and set protocols static route 192.0.2.0/24 blackhole.
Apr 12 2020
Apr 10 2020
Apr 9 2020
Apr 4 2020
Mar 30 2020
I think I agree: at commit time, user's CLI edit level is irrelevant and should have no effect on the script behaviour.
Mar 25 2020
Mar 22 2020
Mar 18 2020
Could you describe your "dream syntax" for it?
The op mode node.def's simply don't have a concept of value help in vyatta-cfg, only comp_help (<completionHelp> in XML terms).
Mar 15 2020
Mar 14 2020
Mar 9 2020
Mar 8 2020
Feb 23 2020
Feb 10 2020
Feb 4 2020
Jan 31 2020
Jan 16 2020
We took other steps that allows us to take the image back to a manageable size, and this task lost its immediate relevance.
Jan 9 2020
Jan 2 2020
Dec 10 2019
Good point! PR merged.
Dec 5 2019
The runtime errors are fixed by the above commit.
I agree. If it works in a way that is consistent with what the command promises, let's use it.
Nov 19 2019
Nov 17 2019
Frankly, I can see why FRR doesn't want it to be modifiable at runtime. If you are decreasing the number, it would force a big routing table rebuild, and tracking whether the user increased or decreased it to decide if command should be allowed or not is more trouble than it's worth.
The original client-id has been cherry-picked into crux, but the vendor-class commands are not backportable since they rely on the new interface scripts.
Also in crux now.
Cherr-picked into crux.
Nov 16 2019
Nov 14 2019
I agree. Users should be able to change the port independently from the address.