OK so @Viacheslav would the maintainers be OK with adding all standard Kea DHCP options to the vyos config interface? That seems like it also could be overwhelming, but maybe it is the best option.

My use case is testing the newish rfc9463 which is DHCP option 162 for IPv4.
In Kea, the config looks like this

@fmertz would it help if I was able to get one of the LCD components and send it to you?
I did write a little program that pulls VyOS specific stats and prints them to the screen, it's working as long as I limit the text to plain characters. So ultimately proper driver support would still be ideal.

Update on current discoveries.
So pfSense has the same issue with garbage showing on the screen if I kill it's lcdproc_client.php process. That PHP script loads all the custom stats and writes them to the LCDd socket. But it only prints plain text which is why I assume it has no issues.

I messed around with it today, and made some progress!

Yeah I was running lcdproc in a separate window in the foreground as well, and restarted it each time I change a setting in LCDd

The LCDd exit with code 1 was resolved by simply changing Driver=cwlnx to Driver=CwLnx

I now have an appliance to use for testing. Tried setting the driver to hd44780 and nothing seems to happen. Set ReportLevel to 5 on both lcdproc and LCDd.
On lcdproc the only output is

I can probably help with this in August when I'll have access to one of these appliances again.

Hey @n.fort yes I did test it per my comment on Jan 23rd. It's fine just different in that type used to be a name and now it's an integer with a separate option of type-name. It's fine was just noting the difference compared to previous versions.
Thanks for checking!

@n.fort I just built a fresh image and tested. The first thing I noticed is that icmpv6 now only accepts integers while previously it accepted names. I'm assuming this is a purposeful design change where users now have to set type-name instead.
The any option has been removed, which I suspect is OK as you'd simply leave it unset if you want to accept all icmp types.
Overall this should eliminate the user confusion so I think it's a good change.

Confirmed, I just built a new image using 1.4-rolling-202201212148 and I can no longer reproduce the issue.

In T4199#117215, @n.fort wrote:

@Viacheslav this is great. I hope to get around to testing it this week.

Thanks @jestabro this seems like a good place to start learning VyOS internals, will give it a go when I have some off time and submit a pull request.

@jack9603301 I tried building jool into the VyOS image but because their deb packages uses DKMS which is not compatible with VyOS so somebody has to create a VyOS specific deb package.

I'm thinking about trying to run either tayga or jool as a docker container inside of VyOS. Has anyone tried something like this? If I wrote a guide on how to do this I wonder if it would be an OK temporary solution until it's integrated into VyOS.

ddclient version 3.8.2 is currently include with VyOS which is 2 versions behind. Latest is 3.9.0 which has the required fixes.