@SteveP Thanks!
I created a PR to exclude these rules https://github.com/vyos/vyos-build/pull/832

It seems to be the 50-usb-realtek-net.rules file causing the strange behaviour.

Thank you, though I wish I didn't have to, just have no choice. There are projects that already show how it should be done, better than I ever could. Some even offer choice of paid full supported or free basic unsupported version as pre-built VM appliance, or free full unsupported self-built from sources. Build process is documented, and they don't hate those who publish build scripts that make it easier. Please look at Xen Orchestra for example, management add-on for XCP-NG which is itself free (with optional commercial support) and stable at the same time, and the story how it started from Citrix XenServer was quite similar to how VyOS started from Vyatta. So yes, it can be done.

@MPStudyly thanks for spotting this
merged in as duplicate

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

We use suricata only for the rolling
backport not required

Probably a duplicate of https://vyos.dev/T6679.

Probably a duplicate of https://vyos.dev/T6714.

Good luck with migration to Alpine and own fork of Accel PPP, finally you will show us how true open source should be done

Sorry @syncer - I beg to differ.
It should be clear from the context that I mean the sagitta branch and at https://github.com/vyos it is no longer being updated.
I did participate, it's easy to find some evidence so I won't repeat it here, and all was well until a few months ago.
Only discovered and started using VyOS 1.2.x in 2020 (easy to check when I registered), not for 11 years. Earlier there was Vyatta, later EdgeOS on ERPro-8 for BGP, and MikrotTik as PPPoE server.
The only reason for moving to VyOS was non-commercial - wanted to enable IPv6, no customer asked or paid extra for it, it's just that I feel it was the right thing to do, but both EdgeOS and RouterOS had poor IPv6 support.
My business is a small local ISP for a few hundreds of people in a rural area, yes really that small and it's just me doing everything (no employees), not what you usually think when you see "ISP" (big companies with lots of money).
All IPv4 address space I use is 1024 addresses, easy to check in BGP (AS56523), and no CGNAT so each customer gets a single static IPv4, so you get the idea about the size of my business. My service costs about $15/month and I also provide some free services (for example to volunteer firefighters - Ochotnicza Straz Pozarna), also have two local schools in range but they were not interested (already have EU subsidized Orange fiber).
I never said I was smarter, and I don't understand what you mean by shit-talking. It's the first time ever in my life when I'm being accused of such things. Looks like some horrible misunderstanding.
If you mean something specific, please point me to it, and if it was indeed the case I will publicly apologize. Really I have no idea what you mean here.
But simply having some different opinions is not shit-talking. Actually I highly respect the Team for all the good work, it's just the last few months when things went horribly wrong in relations with some (not all) of you.
One more thing, I've been using Linux and other open source projects since 1994 (yes 30 years), and VyOS was the only ever open source project I supported with donations, $25/month from March 2022 to June 2024 when you stopped accepting them, and I did that voluntarily (didn't have to do it to get access to images, as I already had it granted as open source contributor).
So I hope you can see why I don't want to go away until we can talk like normal people and clear all the horrible misunderstandings.

Source is at https://github.com/vyos
Project around for 11 years but instead of participating, you decided you were smarter than everybody else and would abuse subscriptions for home users to run your business.
When we cut of people like you, instead of joining our efforts, you again decided you were smarter, you wanted per GPL, and now it will be per GPL
Not even to mention your shit-talking about Team and me. Go elsewhere, you are not welcome here

It's not just me, there is significant interest in the community to do builds from source, and even in your own words @syncer https://vyos.dev/T6264#185011 it appears it was OK just a few months ago.
People took the challenge and have done some good work to make builds reasonably easy, complete with de-branding to address the tradermark concerns, and a few fixes in the build process.
As with any open source project, it's kind of natural to want to build from source. So I really don't understand all this hostility. I try to stay calm and not insult anyone, please try to do the same.
BTW, I try to contribute to some related projects (accel-ppp) and even though I'm strictly technical there (testing, reporting bugs, sending patches), issues are converted to discussions but that's all, just silence.
Let's stop fighting against each other and start some normal discussion (OK maybe here is not the best place, so I'll stop now). Peace.

codeowners added in private repo too
https://github.com/VyOS-Networks/vyos-1x/blob/circinus/CODEOWNERS

According to https://old.reddit.com/r/vyos/comments/1ggzxye/setting_forward_error_correction_in_vyos/lv09d09/ using eth-tool to both set (and show) current fec-setting(s) should be doable (tested on Intel and Mellanox nics using transceivers from FS.com, Flexoptix and Mikrotik):

I believe I am bumping into this issue aswell:

Nobody cares what you need @marekm

@Viacheslav please, one of the free ways that I know and actually used was to build from source - and it's not updated anymore (moved to private repo). BTW, it''s still mentioned on the VyOS website, which is misleading. So this is very much related to this report, I'd like to build my own sagitta images using the new improved build system (hooray no more Jenkins!) but can't, it's not spamming just raising valid concerns. I don't care about pre-built LTS images anymore, just open the sources again so it is possible to build own images as before. Thank you.

@marekm, stop spamming in every message about LTS.
You know all the ways to get LTS images, including entirely free ones.
Thanks!

@Apachez i think we need to add status Implemented for feature request it makes more sense
and for bugs mark them as resolved

Thanks - resolved means its implemented as the blog post stated :-)

The new build system is welcome, thank you. Restricted access to LTS sources, not so much...

The blog post over at https://blog.vyos.io/vyos-project-october-2024-update claims this have been implemented, there is a merge from 10th sept 2024 claiming to be merged - yet this task have been closed with "not applicable - out of scope for VyOS".