openmediavault-dnsmasq feedback

    • OMV 2.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • openmediavault-dnsmasq feedback

      System info: This system is a 64-bit Wheezy VM running Stoneburner 2.1.4 with a 3.2.0 kernel.

      I've been using the dnsmasq plugin for probably close to a year now as my only DNS server on the network and have had no issues with DNS resolution (public or private).

      Recently I've started using the DHCP more and that's where I'm running into some issues. I've noticed that many times I'll have a newly powered on DHCP system that has an active lease, but that lease does not show in the plugin. I can list the contents of /var/lib/misc/dnsmasq.leases and find the IP of the system (if I know that MAC ahead of time), but it can get cumbersome with more systems on the network. I tried reducing the lease time to 1 hour in hopes of it trying to refresh and display all the leases, but that doesn't seem to make much difference.

      The first problem lead to the second, since all leases aren't always displayed I decided to make Static dhcp lease assignments. After every attempt to create a static lease, it would display an error message. Yet after logging out and back into the web-interface I would see the static lease that I tried to create.

      However when I tried to power on the system (of the static lease) it would be issued a different IP address. Usually one IP integer number greater than it was previously. I then tried creating the static lease from a current lease that was shown, but it was the same error and sequence as before.

      Lastly I tried to enable additional DHCP logging via the plugin, but that returned an error too.

      I don't believe I have anything misconfigured, or maybe I'm not entering the static lease information in correctly? I've been trying to figure this out, but right now just looking for any help or advice, but also curious if there's anyone else out there seeing the same thing?

      I've attached some pictures that hopefully will help.
      Images
      • OMV missing lease.png

        242.74 kB, 1,008×595, viewed 566 times
      • create statip dhcp reservation error.png

        45.52 kB, 963×598, viewed 497 times
      • dhcp static reservation creation error - from a lease.png

        38.5 kB, 923×582, viewed 409 times
      • dhcp static reservation created.png

        15.07 kB, 421×327, viewed 412 times
      • error on enabling Log DHCP.png

        37.66 kB, 1,043×402, viewed 400 times
    • I think it doesn't show the second system because you have more than one system with the name * in the leases list. I can't test so try this package to see if it fixes.

      After installing, can you post the output of the following: omv-mkconf dnsmasq
      omv 4.1.11 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I didn't realize that two or more system names with * would be the break down, but you're probably right. Although I'm not sure how I'll know ahead of time is any system on the network will fall into that category?

      I've installed the new package (thank you) and here's the output of "omv-mkconf dnsmasq"

      Source Code

      1. =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.07.25 11:50:54 =~=~=~=~=~=~=~=~=~=~=~=
      2. login as: root
      3. root@omv.bw's password:
      4. Linux omv 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64
      5. The programs included with the Debian GNU/Linux system are free software;
      6. the exact distribution terms for each program are described in the
      7. individual files in /usr/share/doc/*/copyright.
      8. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
      9. permitted by applicable law.
      10. Last login: Sat Jul 25 10:46:37 2015 from bw018.bwroot@omv:~#
      11. [Kroot@omv:~# omv-mkconf dnsmasq
      12. update-rc.d: using dependency based boot sequencing
      13. update-rc.d: using dependency based boot sequencing
      14. root@omv:~#
      Display All
    • I was hoping the change in the package would allow for more than one system with * for a name. Did it fix the listing? What about the command omv-mkconf dnsmasq 2>&1
      omv 4.1.11 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • No, I don't believe that did make a change. The .161 system still doesn't show in the plugin. I'll see if I can "add" a hostname to either of those systems but I'm not sure if I can or not. the .161 IP system is a factory OS pogoplug and the .176 system is a APC SNMP network card.

      I appreciate the help and all that you've done, and I'll try to do some more testing. This is one of those services than I think many take for granted?

      Source Code

      1. =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.07.25 11:50:54 =~=~=~=~=~=~=~=~=~=~=~=
      2. login as: root
      3. root@omv.bw's password:
      4. Linux omv 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64
      5. The programs included with the Debian GNU/Linux system are free software;
      6. the exact distribution terms for each program are described in the
      7. individual files in /usr/share/doc/*/copyright.
      8. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
      9. permitted by applicable law.
      10. Last login: Sat Jul 25 10:46:37 2015 from bw018.bw
      11. root@omv:~#
      12. [Kroot@omv:~# omv-mkconf dnsmasq
      13. update-rc.d: using dependency based boot sequencing
      14. update-rc.d: using dependency based boot sequencing
      15. root@omv:~# omv-mkconf dnsmasq
      16. update-rc.d: using dependency based boot sequencing
      17. update-rc.d: using dependency based boot sequencing
      18. root@omv:~# omv-mkconf dnsmasq 2>&1
      19. update-rc.d: using dependency based boot sequencing
      20. update-rc.d: using dependency based boot sequencing
      21. root@omv:~# cat /var/lib/misc/dnsmasq.leases
      22. 1437843552 00:19:df:a8:3c:c8 192.168.1.169 DIRECTV-HR22-DFA83CC8 01:00:19:df:a8:3c:c8
      23. 1437843812 28:10:7b:0c:fd:fc 192.168.1.162 cam2 01:28:10:7b:0c:fd:fc
      24. 1437843572 00:c0:b7:81:ae:b3 192.168.1.176 * 00:00:c0:b7:81:ae:b3:00:00:00
      25. 1437842685 90:fb:a6:87:6b:ca 192.168.1.166 revo 01:90:fb:a6:87:6b:ca
      26. 1437843181 00:25:90:0a:fe:1a 192.168.1.161 * 01:00:25:90:0a:fe:1a
      27. 1437842401 00:25:90:0a:f5:40 192.168.1.152 BW022 01:00:25:90:0a:f5:40
      28. 1437843747 00:25:31:00:bf:2e 192.168.1.163 debian *
      29. root@omv:~#
      Display All
    • Well, the leases list should be ok in the latest package (same location). Try it out and then we can work on the static leases.
      omv 4.1.11 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!