May 1 snapshot, dnsmasq and missing static leases
-
Updated to latest snapshot of May 1 and now all my static leases are gone. I disabled and enabled DNS forwarder but they did not reappear. Just the localhost and the hostname are there. Dynamic leases are updated.
I saw there was a commit "Fix dnsmasq host overrides and dhcp integration" and that is the problem I guess.
-
now all my static leases are gone.
Are you looking in the correct place? I presume you mean Static DHCP assignments which should be visible in Services -> DHCP Server and click on the tab for the appropriate interface.
-
They are there, just not in my hosts file. Sorry that I was not clear enough
-
Also the Host Overrides for custom DNS records do not end up in the host file. (read /etc/hosts - 2 addresses, only pfsense internal entries) Happens also in the may 2 build.
Back to the april 30 snapshot fixes this (read /etc/hosts - 26 addresses) -
2.1-BETA1 (amd64)
built on Wed May 1 12:20:46 EDT 2013
FreeBSD 8.3-RELEASE-p8I think I'm seeing the same thing. Static dhcp leases do not resolve for local lookups, despite the option being enabled in the DNS Forwarder options. This worked on my last snapshot from early March, and prior 2.0.x releases.
-
Neo14 posted a fix at line 257 in /etc/inc/system.inc
https://github.com/pfsense/pfsense/commit/ea1aca1326c79d5c819ec7c22c068b1c63074828
-
mmmhhh… still not working with the snapshot built on Sat May 4 05:25:20 EDT 2013...
also to you all?
Thanks,
Michele -
mmmhhh… still not working with the snapshot built on Sat May 4 05:25:20 EDT 2013...
also to you all?
Thanks,
MicheleSame here.. todays snapshot has the same error.
Doing the change described from gogol above, editing the /etc/inc/system.inc file and doing a reboot fixed the problem for now tho :)
Hopefully it will be updated the next few days, and i usually dont run the upgrades that often anyway.. so i hope by my next snapshot it is peachy.
C
-
Yeah, May 4 snapshot, neither DNS registration for static DHCP entries nor host overrides seem to work.
-
mmmhhh… still not working with the snapshot built on Sat May 4 05:25:20 EDT 2013...
also to you all?
Thanks,
MicheleSame here.. todays snapshot has the same error.
Doing the change described from gogol above, editing the /etc/inc/system.inc file and doing a reboot fixed the problem for now tho :)
Hopefully it will be updated the next few days, and i usually dont run the upgrades that often anyway.. so i hope by my next snapshot it is peachy.
C
Applying that patch shouldn't be possible on builds newer than 05/01/2013 since the commit should be in the code already.
If it is possible to apply the patch on newer builds (will test this later when I have time) it means the commit is not getting applied to newer builds correctly for some reason, and that would be the issue that needs to be addressed.
Or are you saying removing that line is fixing the issue for you?
-
Issue was only patched 2 hours ago thats why the problem hasnt been resolved yet in previous snaps.
https://github.com/pfsense/pfsense/commit/a80cb9ca40fb5b485d03d7b64a3fd99a7a15b880
Need to try the next snapshot after 20130504-0557
-
Neo14 posted a fix at line 257 in /etc/inc/system.inc
https://github.com/pfsense/pfsense/commit/ea1aca1326c79d5c819ec7c22c068b1c63074828
This worked for me. I updated to the May 4 snapshot just this evening & had to patch this myself.
-
Issue was only patched 2 hours ago thats why the problem hasnt been resolved yet in previous snaps.
https://github.com/pfsense/pfsense/commit/a80cb9ca40fb5b485d03d7b64a3fd99a7a15b880
Need to try the next snapshot after 20130504-0557
Ahh, I see, didn't catch the new dnmasqcfg variable ;-p
Ok, so clearly then it was meant that removing that line would fix the issue, not applying the old patch. Thanks!
-
Issue was only patched 2 hours ago thats why the problem hasnt been resolved yet in previous snaps.
https://github.com/pfsense/pfsense/commit/a80cb9ca40fb5b485d03d7b64a3fd99a7a15b880
Need to try the next snapshot after 20130504-0557
Ahh, I see, didn't catch the new dnmasqcfg variable ;-p
Ok, so clearly then it was meant that removing that line would fix the issue, not applying the old patch. Thanks!
I did not remove anything, i just edited the dnsmasq from the line and changed it to dnsmasqcfg. No remove, or add lines, just a edit manually with nano.
C
PS. I havent tried todays build.. anyone know if its fixed?
-
Issue was only patched 2 hours ago thats why the problem hasnt been resolved yet in previous snaps.
https://github.com/pfsense/pfsense/commit/a80cb9ca40fb5b485d03d7b64a3fd99a7a15b880
Need to try the next snapshot after 20130504-0557
Ahh, I see, didn't catch the new dnmasqcfg variable ;-p
Ok, so clearly then it was meant that removing that line would fix the issue, not applying the old patch. Thanks!
I did not remove anything, i just edited the dnsmasq from the line and changed it to dnsmasqcfg. No remove, or add lines, just a edit manually with nano.
C
PS. I havent tried todays build.. anyone know if its fixed?
I just upgraded. It seems to be OK, but I don't know if it was because I patched it myself yesterday or what.
-
I just upgraded. It seems to be OK, but I don't know if it was because I patched it myself yesterday or what.
When you upgrade /etc/inc/system.inc will be overwritten, so this bug is gone.
I will close this topic.
