Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] fmDHCP + Raspberry Pi #426

5 tasks done
cm91 opened this issue Dec 22, 2018 · 1 comment
5 tasks done

[BUG] fmDHCP + Raspberry Pi #426

cm91 opened this issue Dec 22, 2018 · 1 comment


Copy link
Task lists! Give feedback

@cm91 cm91 commented Dec 22, 2018

Please prefix your issue title with one of the following: [BUG]
Replace everything between stars with current version of your facileManager and module installations:
fM Version : 3.3
{Module Name} Version : 0.3.2

In raising this issue, I confirm the following (please check boxes, eg [X]):

  • I have read and understood the contributors guide.
  • I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present.
  • I have checked that the issue I'm posting isn't already reported.
  • I have checked that the issue I'm posting isn't already solved and no duplicates exist in closed issues and opened issues
  • I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.

(BUG | ISSUE) Expected Behavior:

ISC DHCP on Raspberry Pi should reload when building config.

(BUG | ISSUE) Actual Behavior:
Config Build fails.

(BUG | ISSUE) Steps to reproduce:
Build Config on RPi dhcp server

I found out, that the config build on Raspberry Pi fails.
The config file gets written, but the reload fails.

I think this is due to the osversion parameter which is checked by the clients functions.php

I could fix this by adding this line to the clients functions.php file:

'Raspbian' => array(findProgram('service') . ' isc-dhcp-server restart', findProgram('systemctl') . ' restart isc-dhcp-server.service'),

Maybe this could be included in future versions, or you find a better way to fix it :)

Copy link

@WillyXJ WillyXJ commented Mar 17, 2019

This is now fixed in fmDHCP 0.4 and later.

@WillyXJ WillyXJ closed this Mar 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants