Since we dropped XDP, I suppose this is irrelevant now.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 9 2024
No one complained about this issue in a while, but feel free to reopen, if anything.
Already supported as force-udp-encapsulation.
Haven't seen those warnings in a while...
Not reproducible anymore.
It's no longer in current, so this is done.
The new implementation has been working fine for a while now, but if anything, please reopen.
No one complained in a while, but feel free to reopen if anything.
I haven't seen this error in a long while, so I suppose it's fixed.
Host name settings certainly works fine now, but if anything, feel free to reopen.
Should be no longer an issue with the new BGP implementation.
Our use of the utils module is quite consistent now.
Our container infeastructure is in place, any improvements should get their own tasks.
The new interface infrastructure largely solves the original issues.
I suppose we should close it. Any additional tasks should mention specific issues with current cloud-init versions.
The new firewall implementation makes this no longer relevant.
The PR was rejected.
Already supported in the current nftables-based implementation.
Since ISC DHCP relay is EOLd and unmaintained, we may need to get back to this idea.
The new syntax has explicit listen and upstream interface settings.
I think we should include lshw indeed — it offers JSON and XML outputs.
iperf was definitely updates in newer releases, so I presume the issue is solved.
Since the firewall group implementation was migrated to nftables native groups, the issue is no longer applicable.