PR for Equuleus: https://github.com/vyos/vyos-1x/pull/2776
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jan 9 2024
Hi, If it helps
Warning would be much better because it would solve the problem.
When you have the image already loaded and the system was rebooted, the image should still exist and therefore the user/pass is not required (for the moment).
There could be another bug related T5407
I guess we should not Raise config but use the Warning here https://github.com/vyos/vyos-1x/blob/864524ba86b0a4d57ab64d6e9398c3fd5eb2fce4/src/conf_mode/container.py#L405-L408
Viacheslav suggested the following change which worked for me:
PR for 1.5 https://github.com/vyos/vyos-1x/pull/2768
PR for 1.4 https://github.com/vyos/vyos-1x/pull/2774
Can you please paste the output of ls -ld /config/dhcp and ls -l /config/dhcp. It is possible you might have installed a version _before_ 1.5-rolling-202401030023 and the instance is carrying forward the misconfigured directory/file persmissions.
I replied to jestabro via email a couple of hours back, but noticed that it didn't show up here. For the benefit of anybody else interested in this bug I'm cutting and pasting the email below:
Jan 8 2024
PR for VyOS 1.4 https://github.com/vyos/vyos-1x/pull/2774
Well, the webserver is for an API - if you wan't to server files you can either use the default document root, or spawn a container. We should focus on packet pushing and administration.
The errors here were fixed in:
https://vyos.dev/T4052
https://vyos.dev/T4053
in equuleus and subsequent.
The new firewall implementation by Nicholas et al. supports bridge firewalls.
I suppose with the new firewall implementation, this is no longer relevant.
With the migration to nftables, I suppose this is not relevant anymore.
With the current smoke test infrastructure, I'm inclined to call the original task resolved.
Neither 1.1.8 nor Crux are supported anymore.
I presume the issue is no longer relevant since people do successfully use QAT now, but feel free to reopen if anything.
If the issue is still relevant, feel free to reopen.
I suppose the current PKI CLI does fulfill the requirements of this task.
Just to clarify the issue: note that one can specify the choice of serial console during the 'install image' process; are you not seeing the boot messages with this setting ? or are you unable to set it during installation ? Thanks.
I don't think anyone saw this issue lately, but if it resurfaces, feel free to reopen the task.
Now that 1.4 is about to be released and 1.3 going into maintenance mode, we definitely will not include it in 1.3.6.
User creation works fine now.
Yes.
Yes I tested again upgrading with today's latest rolling release no ip address is served to clients so issue persists no changes
The dynamic DNS system has been revamped since then, so I assume this is no longer an issue, but feel free to reopen if it manifests again.
I'm closing this since no new details surfaced. If it's still relevant, feel free to reopen.
1.2 is now EOL, so no new changes will be made there.
Multiple people report both working UDP offload and firewall configurations, so I presume this issue is no longer relevant. Feel free to reopen if new details surface.