@fernando Could you please re-test in the latest rolling release image?

I've issued a PR for this at https://github.com/vyos/vyos-1x/pull/4482, attempting to address a few things T5816 missed.

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

In T6253#190207, @giuavo wrote:

Are you sure your DHCP server honors the no-default-route option?
I may be wrong, but I think the no-default-route just sets an option in the DHCP request, asking the DHCP server to not send back the default route.
I have the same issue with my ISP, and they told me they will always send a default route via DHCP.
I have solved the issue using DHCP hooks.

Any updates on this? I am also affected.

Tested as working in: VyOS 2025.04.19-0018-rolling

If you have a device that beeps, could you check if this changes anything?

beep-if-fully-booted was renamed to startup-beep in T3078 / 193323b.

Please can this be considered for VyOS 1.5?

@trae32566 It is not reproduced in the test lab.
Are you still having issues with it?

There was no a change - I tested with the existing code in trunk and could not replicate the issue - hence the question, given this is a pretty old bug report

@Apachez I believe @evgmol was referring to:

In VMware vSphere, in multiple devices these log messages are seen after upgrading to 1.4.1 version:

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

I am implementing this feature now!

In T6821#217838, @evgmol wrote:

Are we happy with the above patch (fixing the terminal)?

Hi,
I tested with 520-700+ character long strings and the bug is not evident in 1.3- or1.4+ versions
Can you please re-rest and advise this issue still persist

Are we happy with the above patch (fixing the terminal)?

After some investigation, it can be advised, that the described issue is to do with netcomm_cli module implementation used by VyOS Ansible Galaxy - namely, the ansible_net_version is set for a connection and stays so until reconnects and re-reads the modified hostname.
As such, this is currently outside of the collection's control.
That said, the issue can be easily avoided by reading ansible_facts mid-playbook:
Example Playbook:

https://github.com/vyos/vyos.vyos/pull/400

Hello! Any news regarding this issue?

@pasik Hi mate! Were you the original reporter of this bug please?
If so, can you clarify a few questions I asked above?
thank you

I cannot see the virtual interface names are supported in 1.3-1.5 -

PR: https://github.com/vyos/vyos-build/pull/922

@Apachez could you please assign this task to me?

OK - a manual and specifically targetable workaround for this is possible using firewall matches for IPsec payloads, as part of T4694.

https://github.com/vyos/vyos.vyos/pull/398 - Ready

I will look into after https://github.com/vyos/vyos.vyos/pull/387

Closing this, new tasks can be opened for any issues found in new WLB.

Please re-open if this is encountered in new WLB.

This should not be an issue in new implementation

PR for new implementation: https://github.com/vyos/vyos-1x/pull/4356

Module updates (6.0.0) add support for encrypted passwords, including idempotence and tests.

Resolved with latest changes for 6.0.0

this issue doesn't reproduce on:

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?

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.

fix for another git commit archive related problem:
https://github.com/vyos/vyos-1x/pull/4333

looks like the problem was fixed in this task: T7048

I'm willing to work on this issue to implement solution proposed by @Viacheslav.

should be fixed by https://github.com/vyos/vyos.vyos/pull/382

This issue appears to persist. I have been trying to run QAT with 8970 cards, and I am also running into this issue. Ultimately I have two separate instances of VyOS which exhibit the same lockup issue (separate hardware and locations). The frequency of the locks ups is far more frequent than what lucasec mentioned. Anywhere in the 12 hour range after a reboot the system crashes.

This issue should have been resolved by a number of already implemented PRs - e.g. https://github.com/vyos/vyos.vyos/pull/354 or https://github.com/vyos/vyos.vyos/pull/368, therefore I am closing this ticket now. Please feel free to re-open if I am wrong

Are we closing this? Or we have some glowing example of the wrong processing?

I had a look at T5965 and several discussions on the forum.
It seems as though under certain circumstances there will be no answer from DHCP even though I can see the DISCOVER being sent out the wwan0 interface, but the connection works if I setup the parameters that can be betrieved from ModemManager.

fix for decimal DSCP values:
https://github.com/vyos/vyos-1x/pull/4302

i retested this issue:
could not reproduce the original problem on versions 1.4 and 1.5

The recent updates to vyos_user should support updating encrypted passwords, including appropriately understanding if there was a change.

@sdwilsh Unless you have an objection, I'm going to close this out as fixed by the current version in Main.

OMG. I just spent hours trying to diagnose why I was getting Sending reply: error_code 1 with output "error". The logging really needs to be improved.

Hello, I know that to debug, I have to read the tables

Raised a Draft PR https://github.com/vyos/vyos.vyos/pull/368

Fixed for 1.3+ along with test verifications