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

VyOS 1.2.7-rc1 reports:

@Viacheslav . Ok this is not a problem, because we have a workaround with pseudo ethernet interfaces

set interfaces pseudo-ethernet peth1 source-interface 'eth1'
set service pppoe-server interface peth1 
set service pppoe-server interface eth1 vlan-id '50'
set service pppoe-server interface eth1 svlan 1000 vlan-range '1-4095'

Now all looks good and works properly, but need to add better help value

vyos@vyos# set service pppoe-server interface eth3 vlan-id 
Possible completions:
   <text>       VLAN monitor for the automatic creation of vlans (user per vlan)

There are two versions that have been developed, reasonably feature complete, pending testing. One presents an OpenAPI schema of application/x-www-form-urlencoded (multipart forms); the other, application/json. The latter uses middleware (strictly speaking, a custom request and route class, instead of the Starlette middleware capability, although that may change) to intercept multipart requests, so as to remain backwards compatible.

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

Implemented in VyOS 1.4

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

Example configurations:

I'm curious, I did a little research on Tacacs +, and I'm not sure what you want the certification service to do for you? SSH certification or?

Also CUMULUS has a nice looking package

thank you very much ! Very responsive 😄

Tomorrows 1.3 beta image and 1.4 rolling will have the fix included.

Yeah, that would work. We still try to keep the number of custom validators to a minimum.
The XML file is changed now for 1.4 (and soon 1.3).

When I create dedicated validator and modify manually file /opt/vyatta/share/vyatta-cfg/templates/interfaces/tunnel/node.tag/parameters/ipv6/encaplimit/node.def it work :)

commit now produces an error:

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

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

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

Yes, some time ago, it could produce kernel issues https://www.mail-archive.com/netdev@vger.kernel.org/msg218964.html
And I think it will be good to add the possibility to control unit-cache to have the opportunity to influence this.

Any reason to not default enable it?

Assuming T3356 can be backported to equuleus, this fix will not be needed.

Still does not work in 1.4-rolling-202102060218