VyOS 1.2.0 currently has this enabled, closing.

Is this related to T20 ?

VyOS runs on 4.19.28 for a week now. Update can be used for both crux and current.

AS Curretn and Crux kernels and modules are build the same way, it's on @dmbaturin to use the packages. From the source side everything is there.

There's nothing special to do for crux, just build the packages for the next release.

There is no specific crux branch here. @dmbaturin only needs to build the appropriate packages and we're good.

Please test latest rolling release

Both use cases mentioned above have been solved in a different maner.

How should we proceed?

Same goes for DHCPv6 server

Okay, here is my setup on ESXi 6.7:

I rather would prefer only one option. The more options you have for things to configure - the more trouble you get.

@Gislaved I need to reconfigure my ESX environment from Portgroups with fixed VLAN configuration to a trunk and then to one of my VyOS instances as DHCP server - maybe today or tomorrow. Please apologize if you feel this takes too long but some of us do VyOS maintenance for fun besides a day job.

I prefere set service syslog preserve-hostname as we use hostname in other configuration nodes, too

@Gislaved I need to adjust my lab to this, first. Let me get back to you.

@byteshifter unfortunately you refer to the wrong version. we are using isc-dhcp-relay from Debian Jessie, as VyOS 1.2.0 is based on Debian Jessie, please see https://manpages.debian.org/jessie/isc-dhcp-relay/dhcrelay.8.en.html

@byteshifter, I do not see the -id and -iu options in the man page of isc-dhcp-relay. Where dis you retrieve that options?

@byteshifter VyOS provides no explicit way in configuring upstream and downstream interfaces. It supports only "interfaces".

See

as soon as I did

set interfaces ethernet eth3 pppoe 0 enable-ipv6
set interfaces ethernet eth3 pppoe 0 ipv6 address autoconf

Is it really required to only update the QLogic part? I ather propose that we drop all firmware-* packages and include the "real" matching firmware packages from git.kernel.org

I‘m on Telekom FTTH (Germany) and could test an ISO, too.

Why not use a combination of two?

No further complaints - seems to be resolved.