Did not work as expected

[Han Koster]

Besides the remarks you already got on shared networks, in the configuration of pool#2 you define in option routers the first IP address(129) of the range.
It will not solve your problem, but I suggest you start the range at 130.
Han Koster

From: <dhcp-users-bounces at lists.isc.org<mailto:dhcp-users-bounces at lists.isc.org>> on behalf of Leandro <ingrogger at gmail.com<mailto:ingrogger at gmail.com>>
Reply-To: Users of ISC DHCP <dhcp-users at lists.isc.org<mailto:dhcp-users at lists.isc.org>>
Date: Monday 29 June 2015 22:42
To: Users of ISC DHCP <dhcp-users at lists.isc.org<mailto:dhcp-users at lists.isc.org>>
Subject: Did not work as expected

Hi guys , while trying to get my config working, got this unexpected result.
After setting following connection diagram:

[rel]

Having following dhcpd.conf subnet config:

shared-network Public {
        subnet 192.168.88.0 netmask 255.255.255.0{
                #pool1
                pool{
                range 192.168.88.2 192.168.88.126;
                option broadcast-address 192.168.88.127;
                option subnet-mask 255.255.255.128;
                option routers 192.168.88.1;
                }
                #pool2
                pool{
                range 192.168.88.129 192.168.88.254;
                option broadcast-address 192.168.88.255;
                option subnet-mask 255.255.255.128;
                option routers 192.168.88.129;
                }

        }

}


I got following lease asigment:
Jun 29 17:04:42 centos86_64 dhcpd: DHCPDISCOVER from 08:00:27:95:d9:62 via 192.168.88.129
Jun 29 17:04:42 centos86_64 dhcpd: DHCPOFFER on 192.168.88.33 to 08:00:27:95:d9:62 via 192.168.88.129
Jun 29 17:04:42 centos86_64 dhcpd: DHCPREQUEST for 192.168.88.33 (20.1.1.254) from 08:00:27:95:d9:62 via 192.168.88.129
Jun 29 17:04:42 centos86_64 dhcpd: DHCPACK on 192.168.88.33 to 08:00:27:95:d9:62 via 192.168.88.129

What is wrong ?I expeted that request coming from 192.168.88.129 would receive some lease from pool2 since 192.168.88.129 falls there.
Instead I, receibing a lease from pool1 including the router option ... The client connected behind relay2 will never go out.
Any Ideas ?

Thanks in advance,
Leandro.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150630/a1d6c29b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ralay.png
Type: image/png
Size: 86860 bytes
Desc: ralay.png
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150630/a1d6c29b/attachment-0001.png>