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

Was fixed here https://github.com/vyos/vyos-1x/commit/ea1be032e98fd1634e71d3c2d61b3e93bff841de

Yep, I use RADIUS.

Some days ago a cleanup was done on 1.4 to clean away some old legacy code, it looks like this cleanup has removed a bit to much...
https://github.com/vyos/vyatta-cfg-system/pull/136

Hi, it's ok with : 1.4-rolling-202101130217
Thank you and have a nice day.

In T3207#84000, @Viacheslav wrote:

@craterman It the same? https://github.com/FRRouting/frr/issues/739

Please verify with a 1.4 rolling image from 20210113 so we can consider this to be backported.

Just wanted to add I’m seeing this issue on 1.2.6 LTS as well running on a dell r220 ii with dual Samsung 840s. I was not seeing it in rolling nor if I switch to mbr boot.

@craterman It the same? https://github.com/FRRouting/frr/issues/739

@stepler, it looks like WIDE does not support type 2 DUID.

@stepler for what it's worth, it does seem to persist across reboots if you just overwrite the file but obvs doesn't survive upgrades

@craterman It makes sense, thanks.
PR https://github.com/vyos/vyos-1x/pull/679

Can we reopen this bug? I need to set a type 2 DUID to get a DHCPv6 PD from my ISP. This is the only thing keeping me from switching from an EdgeRouter to VyOS.

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

Have you had any time to look into this more? I am at a point of wanting to migrate off a Mikrotik RouterOS virtualized instance to a piece of hardware and would love to move to VyOS at the same time.

Unable to set update source "lo" interface
For afi6 should be "redistribute ospfv3" instead "ospf"

p.s. 478 and 479 referred to qmimux0.pcap

Line 478 and 479 seem to be the important ones here.
The MRU of 1450 appears to be correctly negotiated. i.e. Vyos is setting the remote side to a maximum of 1450 bytes, because that is what the remote side requested!

Looks good on 1.3-beta-202101111823:

vyos@vyos:~$ configure
WARNING: You are currently configuring a live-ISO environment, changes will not persist until installed
[edit]
vyos@vyos# set interfaces ethernet eth0 vif 10
[edit]
vyos@vyos# set interfaces ethernet eth0 vif 11
[edit]
vyos@vyos# set interfaces ethernet eth0 dhcpv6-options pd 0 interface eth0.10 sla-id 0
[edit]
vyos@vyos# set interfaces ethernet eth0 dhcpv6-options pd 0 interface eth0.11 sla-id 1
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# delete interfaces ethernet eth0 dhcpv6-options
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# set interfaces ethernet eth0 dhcpv6-options pd 0 interface eth1
[edit]
vyos@vyos# set interfaces ethernet eth0 dhcpv6-options pd 0 interface eth2
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# delete interfaces ethernet eth0 dhcpv6-options
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# set interfaces ethernet eth0 dhcpv6-options pd 0 interface eth1
[edit]
vyos@vyos# set interfaces ethernet eth0 dhcpv6-options pd 0 interface eth2 sla-id 0
[edit]
vyos@vyos# commit
Site-Level Aggregation Identifier (SLA-ID) must be unique per prefix-delegation!
[[interfaces ethernet eth0]] failed
Commit failed
[edit]
vyos@vyos# exit discard
exit
vyos@vyos:~$ show version

Will be fixed in rolling releases starting 20210112. Thanks for reporting.

Hello.
Do you need something else?

systemd-container - easiest way to get containers rapidly into VyOS because all of the infrastructure (systemd) is already there.
We build our images with it, works fine.

You might want to take a look at the patches in T228 - its a 5.4 build with a bunch of C fixup, but using the Intel proprietary drivers for an in-tree build (permits signing of all modules at kernel build time).
We have this running on a host with a dual-port 740 (not doing all that much, some routing, NAT, ACL, and a couple of OpenVPN and IPSEC tunnels), and it seems to be fairly happy in that low intensity environment.
I can try to beat up on it and see how it fares, but probably worth a try.

Needs to add that expression with the right logic.

$VAR(../../../../@) != $VAR(../../../interface/remote-as/@)

1.2 crux the same behavior