PR for 1.5 https://github.com/vyos/vyos-1x/pull/2768
PR for 1.4 https://github.com/vyos/vyos-1x/pull/2774
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jan 9 2024
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.
Jan 8 2024
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.
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.
Yes I tested again upgrading with today's latest rolling release no ip address is served to clients so issue persists no changes
The issue with the missing domain name in /etc/hosts with hostfile-update, as mentioned above, seems to trigger another problem. The hostname requested by the client seems to be added to /etc/hosts verbatim and some clients (eg. some Windows machines and printers) request a fully qualified name with a trailing dot. Since pdns-recursor unconditionally appends a dot, there are now two trailing dots, causing pdns-recursor to crash if it restarts.
I said it in the PR, but I'll say it here too -- I really don't have an idea, nor do I have enough knowledge of the codebase to get debugging data. I suspect that partprobe is either getting an error back from the kernel or is throwing its own error, and partx isn't. if I could step through the process and look at a couple things (like, is some partition actually mounted when partprobe runs, which could trigger this?) I would, assuming I've got the spare cycles. I don't at the immediate moment, and especially not to run through the code to try and figure out debugging on my own. Even being told "set debug here, here, and here, then retry the install" would help.
Jan 7 2024
Is this still an issue on newer rolling images? This PR addresses ownership issues in /config on system update: https://github.com/vyos/vyos-1x/pull/2731
How come partprobe fails but not partx?
Jan 6 2024
This affected my install. PR submitted with fix above (with very basic testing done successfully) in the link below.
Having support for vhost is handy when you dont want just to blindly share a single documentroot but have the ability to use multiple at a single host.
Jan 5 2024
same issue. but as a work around, instead of reinstalling, have you tried clearing /config/dhcp folder and create empty dhcp4-leases.csv dhcp4-leases.csv.2 with _kea:_kea permission.
Hopefully this can be resolved for VyOS 2.0 in the future...
Hopefully this can be resolved for VyOS 2.0 in the future...
New PR for dynamic address groups: https://github.com/vyos/vyos-1x/pull/2756
Jan 4 2024
Complete config
Admin@vyos:~$ show dhcp server leases
Happy new year!
Can you provide your DHCP server config?
Workaround for clouds introduced in:
https://github.com/vyos/vyos-cloud-init/pull/68
https://github.com/vyos/vyos-cloud-init/pull/69
This might fix this problem
https://github.com/vyos/vyos-1x/pull/2752
Still issue persists when u create a new install its fine but upgrading breaks dhcp server ,tried in latest rolling releases 😢 why no solution??? YET...........
Jan 3 2024
OK, local-route actually worked!
Thanks!
The same issue could be with any dynamic interface like PPP that could be don't exists during the boot process/ISP issues