This command is used to generate the ssh fingerprint of your host when vyos cannot verify the legitimacy of the remote server

PR https://github.com/vyos/vyos-1x/pull/792

Possible reason "> 2" in description "Ruby > 2.3"

vyos@r5:~$ echo "Package versions:"; dpkg -l | grep ruby-curse -A 2
Package versions:
ii  ruby-curses                          1.2.4-1+b1                          amd64        curses binding for Ruby
ii  ruby-did-you-mean                    1.2.1-1                             all          smart error messages for Ruby > 2.3

This is resolved by T3412.

Fixed VyOS 1.4-rolling-202103251004

T3436

PR: https://github.com/vyos/vyos-1x/pull/791

PR https://github.com/vyos/vyos-1x/pull/790

PR: https://github.com/vyos/vyos-1x/pull/789

equuleus: https://github.com/vyos/vyos-1x/pull/788

bug fix PR: https://github.com/vyos/vyos-1x/pull/787

I will give it a try once the image is out. The latest right now is still showing 2021-03-23.

Draft PR linked below; it is a draft pending the addition of a supporting package (vyos-http-api-tools). All data validation for application/json requests is done implicitly using Pydantic models/validators; for multipart forms requests, all explicit validation has been moved out of the endpoint function bodies and into the middleware --- this is a pedantic block of code, but allows consolidation and review of all manual checks. An OpenAPI 3.0.2 schema is automatically generated and presented at server-name/docs (Swagger) and server-name/redoc (ReDoc version; slightly more pleasing to the eye).

Works fine for me as well, thanks.

T3333

PR https://github.com/vyos/vyatta-cfg-quagga/pull/72

Please try with the next rolling release - issue should be fixed

PR for saving configurations to /run/frr/{daemon}.conf
https://github.com/vyos/vyos-1x/pull/784

We have two problems here

• the execution here is yet not possible with vyos-configd
• also wihthout configd the routes are not always applied into FRR - still investigating

I can confirm:

Yes, I made mistake when adding the command to the ticket and I corrected it now. It should read:

Something wrong in your configuration

Fixed in the latest version:1.4-rolling-202103230217

PR: https://github.com/vyos/vyos-build/pull/153

@Asteroza With Vyos, any service should be turned off by default unless it is explicitly configured by the user

There are genuine use cases, especially for small/home networks. But UPnP is a literal minefield of problems, and on top of that has had some serious security issues in the past due to fundamental design. If you were going to do this, I would want it off by default.

@c-po, you cherry-picked the wrong commit: equuleus needs the fix from current, not crux.

In T3418#90244, @c-po wrote:

The first error is related to T2759 and can be ignored.

For the second one, can you please provide your full BGP config by pasting the content of show configuration commands | match bgp\|policy

Post the migration of the script from /opt/vyatta/bin/vyos-strip-config.pl to /usr/libexec/vyos/strip-private.py, the strip-private seems to be not working when the ipv6 address is configured to an interface.

@jack9603301 It is not a matter of different codes, but rather what python libraries have been provided so far: the focus has been on abstracting the config session, in several directions, and previously there had not been a use case for reading config settings from op mode.

The first error is related to T2759 and can be ignored.