We do not need add tasks for the documentation. There are a lot of things that are not documented or require improvements.
Just create a PR to the documentation repo.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 31 2024
This is a new feature that was added after EPA-3 release
It was added 3 days ago https://github.com/vyos/vyos-1x/pull/3535
Provide the full (minimal) set of commands to reproduce.
PR opened here: https://github.com/vyos/vyos-1x/pull/3563/
May 30 2024
The similar task T6409
May 29 2024
May 28 2024
May 27 2024
I made a PR that uses an implementation with a separate function: https://github.com/vyos/vyatta-cfg/pull/79
May 25 2024
Only recently moved from 1.3 to 1.5 and noticed rollback-soft immediately (great stuff), the completion message was annoying me too.
May 24 2024
FYI: The configuration is valid and works. It just fails during boot.
The similar task for redirect T260
May 23 2024
The idea is feasible for parameters with constraints (like number ranges) defined in the XML, but there are many other cases where human input is necessary. We could give the tool a set of parameters to randomly generate, or a half-complete config with slots to fill in with random values. Worst case, we'd discover new constraints for more rigid templates; best case, we'd have a proper tool for generating corner cases for smoke tests and fuzzing.
May 22 2024
May 21 2024
May 20 2024
May 19 2024
May 18 2024
May 17 2024
Yeah, my bad!
In T6344#188757, @n.fort wrote:Maybe we should create another xml file identical to listen-address.xml.i but without multi option define in line 16.
Maybe we should create another xml file identical to listen-address.xml.i but without multi option define in line 16.
May 16 2024
@molocho see the tasks T5301 T5154 and https://chrony-project.org/doc/4.3/chrony.conf.html#bindaddress
May 15 2024
This expected behavior due to change from ntpd to chrony
@rob needs to update documentation for 1.4 to reflect changes
May 14 2024
Why just not sign repositories?
May 13 2024
Many thanks. I think it was actually fixed earlier than 1.3.7 - I've been using VRF to allow SSH access only from a separate private management network, on a router that routes only public IP addresses (BGP, OSPF, PPPoE) otherwise, since about 1.3.5 or so.
May 12 2024
May 11 2024
I sent you a message on Slack, as a person with >10 Pull Requests, for us you are contributor and as such eligible for LTS images access.
I get it, not a bug then. Sad, but very understandable.