There is no protocol under facility settings anymore, so the issue is no longer relevant.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 9 2024
The new interface handling infrastructure is firmly in place now.
The last old-style definitions are gone, so the tool is no longer relevant.
The new firewall implementation solved it.
Since we do have proper support for IKEv2 remote access VPN, the issue of configuring it with a workaround is no longer relevant, I suppose.
Let's give it some thought for 1.5/Circinus.
It is impossible to create the config in question now.
I agree this is an issue, but it's a feature for the new configuration backend. Trying to fix it in the current legacy backend is likely futile.
Now the readthedocs process is well-established.
We have sorta decent contribution guidelines now, or so I hope. ;)
The use case for it will be addressed by the future support for true (ignored by the parser) comments.
PR for Equuleus: https://github.com/vyos/vyos-1x/pull/2776
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.