PR for 1.4 sagitta https://github.com/vyos/vyos-1x/pull/2732
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jan 3 2024
Jan 2 2024
PR for 1.4 sagitta https://github.com/vyos/vyos-1x/pull/2732
Jan 1 2024
What I noticed is whenever you update rolling versions it breaks dhcp ,but when you make a new install it is fine.
Just to report back
Dec 31 2023
Related to the list provided in https://vyos.dev/T5706 ?
Dec 30 2023
It is more of a question for Jool.
Or you can use a range of required ports that aren't used by the system
I've tinkered with this a bit , but a problem I have is that I need multiple ip addresses on the outgoing interface(s). I understand that Jool takes all ports, so It's needed for everything to work properly.
On my own WAN interface, this is not a problem, I can just assign another ip from my ISP.
Removing 1.3 backport as it's not trivial. Implementation depends on python3-pyhump (not available and must be self build) and also on vyos.opmode framework which does not exist for 1.3 equuleus
Dec 29 2023
Thank you for the report.
PR for 1.5 https://github.com/vyos/vyos-1x/pull/2716
Fixed via podman update - upstream bug
Dec 28 2023
PR for 1.5 https://github.com/vyos/vyos-1x/pull/2704
@c-po apologies for the delay, missed this over the holidays.
Fix for 1.5 which will be backported
https://github.com/vyos/vyos-1x/pull/2703
This is actually caused by a missing priority value from ddclient. This is an ancient bug indeed.
Package added to 1.4
I haven't been able to test beyond 1.5-rolling-202312130023 due to T5863. I'll test it again once I'm able to update to the latest rolling. Thanks!
@trae32566 Are you experiencing this with the latest rolling version? 1.5-rolling-202312130023 was released mere hours before the fix was pushed. See also: T5774