The only reason I see why this can happen is that the config.boot format can be unexpected. But this should not happen anymore, because now Cloud-init always runs migrations before doing any work, which should always add required metadata if the original file is a valid VyOS config.

I tend to say that this is not necessary and very dangerous. These modules can easily destroy the VyOS filesystem when used improperly.

I think this one would be fixed by my PR for https://vyos.dev/T6045

@bernhardschmidt Are you able to share the relevant pieces of your VXLAN and VRF config as well?

Personally I thing there should be a difference between setting PKI manually like set pki certificate and set pki ca vs whatever the command is to utilize letsencrypt or acme or whatever they might be called automatically through VyOS (lets say set pki letsencrypt and set pki acme etc).

documentation : https://github.com/vyos/vyos-documentation/pull/1479

Documenting what I've found regarding Bug #2:

confirmed working

please excuse the comment. i ended up on the wrong issue due to a fat finger

Sure thing!

I would have put it on my list. @Fabse if you get stuck or need some support just slack me.

Sure @Viacheslav! I'll try to add the PR. Also thanks for the documentation @nvollmar :)

@nvollmar Do you want to claim the task?

Relevant telegraf documentation: https://github.com/influxdata/telegraf/blob/release-1.31/plugins/outputs/loki/README.md

PR for 1.5: https://github.com/vyos/vyos-build/pull/654

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

It will be easy to add; you need to generate a new CLI like with "prometheus-client" for example https://github.com/vyos/vyos-1x/blob/03d8c16a12d182a2fb2ab9f7acec5d8cb83937ba/interface-definitions/service_monitoring_telegraf.xml.in#L188-L250
And add template changes https://github.com/vyos/vyos-1x/blob/03d8c16a12d182a2fb2ab9f7acec5d8cb83937ba/data/templates/telegraf/telegraf.j2#L45-L58

@a.apostoliuk

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

For 1.5-rolling-202406120020 it doesnt work even without having a vrf:

vyos@vyos-a# run update geoip 
Downloaded GeoIP database
Error: GeoIP failed to update firewall
[edit]
vyos@vyos-a#

Unfortunately there is no explaining logging (at least I didn't found any).

Looking into this a bit more. This request is to enable VyOS as a LAC - l2tp v2 client support against an LNS server, for which VyOS already has support. Most LAC's are presented to LNSs as PPPoE connections they are authenticated as LAC clients to an LNS. But there are cases such Andrews & Arnold who allow the l2tp tunnel to come from anywhere.

Upstream bug https://github.com/FRRouting/frr/issues/16013 fixed in https://github.com/FRRouting/frr/pull/16023

Care to elaborate some on that "data integrity issues" claim since you will have integrity changed by all sort of writes (atomic or not)?

There are 2 usecases of option82 when it comes to DHCP:

@aidan-gibson You can build current with the microcode packages included by passing the following to the build script:

In upgrade process

Happened across this one while trying to find support for defining client classes in Kea in order to pass different PXE boot files depending on client architecture. The following has an example of how this is achieved in kea.

Can you please retest with the latest ISO as additional fixes got added to the code.

Just to notice: This task focuses on container part of multi arch support. I can take a look at multiarch pieces outside docker support, but it will demand a deeper knowledge of vyos build system and the vyos goal on multiarch (Or for now, arm) support.

Hey, is this feature currently being worked on? If not then I wouldn't mind working on support for it (I've also created a basic wpa2-enterprise option for client mode)

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

@a.apostoliuk this one should be resolved in the current rolling release, if you're able to check it out?

I have https://github.com/vyos/vyos-1x/pull/3616 and https://github.com/vyos/vyos-1x/pull/3637 as works in progress.