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.

This is still a issue i build a new image with https://github.com/vyos/vyos-1x/commit/911fe645928750f3ce38061a94c9b6db50db0749 and it was spitting out errors :/

Sorry, I have a question, why are there different codes for operation mode fetch configuration tree and configuration mode fetch configuration tree? Is it because of the uncertainty of the mode of action in the user's actions (such as the possibility of abruptly terminating the command)?

Service still with no description VyOS 1.3-beta-202103170443

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

I think vlan range should be 1-4094

Works correct for q, but still show backtrace by Ctrl+C

:Traceback (most recent call last):
  File "/usr/libexec/vyos/op_mode/ppp-server-ctrl.py", line 74, in <module>
    main()
  File "/usr/libexec/vyos/op_mode/ppp-server-ctrl.py", line 63, in main
    print(output)
KeyboardInterrupt

Lets change except BrokenPipeError: to except:

@juesor there is a difference in an IPv6 address you explicitly mention as 2606:ab00:abe1::2/127 and an IPv6 EUI64 address.

@juesor, please try my command; it doesn't have ipv6 or eui64 in it and I just double-checked that it works on 1.3.

Is it something with the eui64 in the syntax ?

This is a p2p link between vyos and a VM.

Ok so the IP assignment of the p2p on eth0 needs to be

Assign it with set interfaces ethernet eth0 address 2006:ab00:abe1::2/127