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:

I am not sure why these extra options are parsed to begin with. My view is Vyos gives the possibility to write extra config file elements because it is not yet supported by the Vyos system configuration. Therefore it should be up to the user to write the correct data as it was in the past.
There should be absolutely no parsing whatsoever and options must be passed through the file unchanged.

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

Proposed changes
Add hook/magic word string and write values in one string if word string in options is present

@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

FRR coder Donald Sharp kicked ass and fixed it here...

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

Ok so I need to allocate a /127 to the eth interfaces.

VyOS 1.2.7-rc1 reports:

To disable udev link_config redundancy call we need to delete /usr/lib/systemd/network/99-default.link

https://github.com/vyos/vyos-1x/pull/777

https://github.com/jestabro/vyos-1x/tree/stdout_redirected

@dmbaturin, don't forget to backport the other two PRs to 1.3:
https://github.com/vyos/vyatta-cfg-firewall/pull/20
https://github.com/vyos/vyos-1x/pull/730

Waiting on backport to 1.3.

@dmbaturin please cherry-pick this to equuleus. Successfully tested on VyOS-1.3-RC1

Thanks, @erkin --- I'm sure you can cherry-pick from 1.4 to 1.3; 'backporting' is not quite the right word, as it is development branch to stable branch. I really like this solution to the mess that was remote.py.

In T3409#89863, @runar wrote:

What about this? https://docs.vyos.io/en/latest/configuration/firewall/index.html?highlight=Mss#tcp-mss-clamping

I'll give backporting a try. It should be doable as long as Paramiko is in our reach. If not, I'll see if I can cobble together something to check for hostname resolution failure.

What about this? https://docs.vyos.io/en/latest/configuration/firewall/index.html?highlight=Mss#tcp-mss-clamping

Thanks for the feedback.

I've found out conf string with "--" works the same way like string without "--". Sorry to trouble you with this question.

Hi, how is the container support now

Implemented in VyOS 1.4 rolling

Example config: https://github.com/vyos/vyos-1x/blob/current/smoketest/configs/vrf-ospf

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

@svd135 please retest with the latest 1.4 rolling or 1.3 beta version. The issue should be corrected.

A migration script is available from 1.3 onwards.

I have successfully added a *ton* of address families in my build. I will PR it, but we also have found an error. The error that we have found is an FRR error at this link here.

Sadly, this isn't a trivial update due to dependencies. However, Microsoft's own documentation says the version that is unsupported for real is 2.2.10, and 2.20 is still supported, even if they recommend the very latest one.

This is a config syntax design mistake on our side indeed. The "preference" option should have always been under "cache".