That commit has the side effect that using sudo or even just committing some configurations will return "sudo: unable to resolve host vyos: System error" every time. Applications that rely on the system hostname will also not be able to reach localhost if the hostname is not a FQDN.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Feb 29 2024
Thanks for that.
Feb 28 2024
Firewall failed migration due to incorrect subnet, 1.3 firewall did not correctly validate those fields. Correcting source address on rule 30 on TO-ROUTER chain should migrate the firewall properly.
PR for global solution extends the local solution in T5839:
https://github.com/vyos/vyos-1x/pull/2659
PR
https://github.com/vyos/vyos-1x/pull/2659
updated and extended for T5660.
Tested in VyOS 1.5-rolling-202402280022 and it works now :
Feb 27 2024
This was resolved by merged PR. Build process now succeeds.
We should keep this behavior in 1.3.7 but change it for 1.4 and onwards
Not a regression as far as this task is concerned. Will update T6073
Full configuration:
Reopened on @Apachez request
Provide please show configuration commands or attach /config/config.boot file.
How do one re-open? :-)
Similar task(s):
Yes, this is only used by the GraphQL API.
Thank you very much!
While at it having a description for a firewall rule within the firewall itself thats longer than 256 is just "wrong" IMHO aka "you are doing it wrong".