strange behavior of shared network
Simon Hobson
dhcp1 at thehobsons.co.uk
Wed Oct 2 19:50:18 UTC 2019
Milan Kovac <kovac65 at gmail.com> wrote:
>I have a few routed networks each with 2 subnets ( public and private )
...
>Here is dhcpd.conf
...
>shared-network 001 {
>default-lease-time 43200;
>max-lease-time 43200;
># divina-private
>subnet 10.64.0.0 netmask 255.255.240.0 {
> option broadcast-address 10.64.15.255;
> option subnet-mask 255.255.240.0;
> option routers 10.64.0.1;
> range 10.64.0.2 10.64.15.254;
> }
>
># divina-public
>subnet 157.157.56.128 netmask 255.255.255.240 {
> option broadcast-address 157.157.56.143;
> option subnet-mask 255.255.255.240;
> option routers 157.157.56.129;
> deny unknown-clients;
> range 157.157.56.130 157.157.56.142;
> host Divinka-Uhliarik {
> hardware ethernet cc:2d:e0:3f:fa:42;
> fixed-address 157.157.56.130;
> }
> host Divinka-Obecny-Urad {
> hardware ethernet 00:4f:74:31:b4:03;
> fixed-address 157.157.56.131;
> }
> }
>}
You need to fix this to start with.
Host statements must always be defined in the global scope - they cannot be defined in a lower scope as you have done here. Wherever you define them, they are always global in scope - but they can inherit options from where there are defined. This is almost certainly not what you want.
So I suggest you fix this first and if the problem persists, then we can try and diagnose it.
More information about the dhcp-users
mailing list