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] network declaration for dhcp peer #422

Closed
cm91 opened this Issue Nov 30, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@cm91
Copy link

cm91 commented Nov 30, 2018

Please prefix your issue title with one of the following: [BUG], [ISSUE], [FEATURE REQUEST], [MODULE REQUEST], [OTHER].

Replace everything between stars with current version of your facileManager and module installations:
fM Version : *3.2
{fmdhcp} Version : 0.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:

network has to be declared befor the pool.

shared-network testlan {
authoritative;
default-lease-time 3600;
max-lease-time 3600;
option routers 10.10.0.1;
option subnet-mask 255.255.255.0;
option broadcast-address 10.10.0.255;
option domain-name "test.lan";

    subnet 10.10.0.0 netmask 255.255.255.0 {

    pool {
            range 10.10.0.100 10.10.0.200;
            failover peer "dhcp-test";
    }

    }

}

(BUG | ISSUE) Actual Behavior:

When using dhcp peer option i have declared:

  1. shared network
  2. network
  3. pool

I assigned the network and the pool to the shared network and it looks like this:

shared-network testlan {
authoritative;
default-lease-time 3600;
max-lease-time 3600;
option routers 10.10.0.1;
option subnet-mask 255.255.255.0;
option broadcast-address 10.10.0.255;
option domain-name "test.lan";

    pool {
            range 10.10.0.100 10.10.0.200;
            failover peer "dhcp-test";
    }

    subnet 10.10.0.0 netmask 255.255.255.0 {
    }

}

The Problem is, that the pool is declared before the network declaration --> isc.dhcp fails!

@WillyXJ

This comment has been minimized.

Copy link
Owner

WillyXJ commented Dec 15, 2018

This is now fixed in fmDHCP 0.3 and later.

@WillyXJ WillyXJ closed this Dec 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment