- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feb 13 2025
Feb 12 2025
Feb 11 2025
Dunno how this is done for IPv6 but for IPv4 we got these kernel parameters to play with:
Feb 10 2025
@takehaya
Hi Takeru-san,
@tarik.haddouchi
Hi Tarik-san,
Priorities seems correct
vyos@r14# /usr/libexec/vyos/priority.py | match "container|firew"
450 container.py ['container']
489 firewall.py ['firewall']
[edit]
vyos@r14#Feb 9 2025
"Failed to listen on syslog.socket" doesnt look good if you ask me ;-)
Reportedly this problem did not exist in VyOS 1.5-rolling-202410260007 (according to slack with @evgmol ). I've seen the problem occur in versions as far back as Vyos-1.5-rolling-202411070006, so that may shed some light on where it occurs.
The individual tests look good - must be a permutation
Feb 8 2025
It looks like this commit wasnt properly tested before pushed to the public tree according to:
Feb 7 2025
@HollyGurza the vyos-network-event logger service could be used to superseede netplugd which we wanted to remove for a long time.
Feb 6 2025
Hi, I'd like to get back on this task and give it a shot, but I have troubles building and testing images from scratch.
What's the recommended procedure? Installing the latest rolling release and hacking that one?
Thank you for the feature; I really appreciate it.
I would rather fail the commit if the user tries to enable surricata and those offload types at the same time.
It will require a migration script, but otherwise it's simple to implement a check.
I suppose we could just add a "guesstimate" check, say, 2GB of free space. At the moment, rolling release images are about 600M, 2GB should be enough for a while, hopefully.
The official recommendation will be to build new images. A blog post on the flavor system is coming, and it will be in the docs, too.