PR for 1.3: https://github.com/vyos/vyos-1x/pull/3130

Did this test again, and I got the same result.

Close the task due to the reporter not responding.
Reopen if you still have this bug.

For 1.3 you have to add a separate PR

Do we need it for 1.3?
If yes, a separate PR should exist, as a backport is impossible.

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

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

Instead of that sysrq stuff, how does it work if you try these 3 tests?

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

We should keep this behavior in 1.3.7 but change it for 1.4 and onwards

Any of these changes most likely affected this.

Compat names were dropped in https://github.com/vyos/vyos-1x/commit/c8ef5e8bdce01bbf05297df39e6c6223d0b2a2ea

Not a bug for 1.5/1.4 anymore.

vyos@r11# set service pppoe-server client-ip-pool POOL range 100.64.24.1/24
[edit]
vyos@r11# run show ver
Version:          VyOS 1.4.0-rc3
Release train:    sagitta

It is not a bug for 1.5/1.4

set policy route-map FOO rule 10 action 'permit'
set policy route-map FOOv6 rule 10 action 'permit'