strange behavior of shared network

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

strange behavior of shared network

Milan Kovac

I have a few routed networks each with 2 subnets ( public and private )

Each private subnet is allocated dynamicaly for unknown clients and
public subnet only for known clients.

All networks are behind L3 switch with vlan interface with ip helper
address 157.157.63.224  and two ip addresses as GWs for clien`s subnets.

All worked correctly about 2 years, but now I added the last shared
network " 011 " I can`t get ip address from dhcp server ( unknown-client )

Of course when I define host I will get ip address, and without subnet
157.157.59.160/7 I will get ip address from 10.64.160.0/20

I use version 4.3.3

Do you have any ideas please ?

Thanks in advance

Milan

Here is dhcpd.conf

# option definitions common to all supported networks...
option domain-name "ourcompany.tld";
option domain-name-servers 157.157.67.3, 157.157.67.1;
allow bootp;
default-lease-time 600;
max-lease-time 600;
allow unknown-clients;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

# default
subnet 157.157.63.224 netmask 255.255.255.240 {
     }

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;
                         }
                 }
}






shared-network 002 {
# nededza-private
subnet 10.64.16.0 netmask 255.255.240.0 {
     option broadcast-address 10.64.31.255;
     option subnet-mask 255.255.240.0;
     option routers 10.64.16.1;
     range 10.64.16.2 10.64.31.254;
     }

# nededza-public
subnet 157.157.56.112 netmask 255.255.255.240 {
     option broadcast-address 157.157.56.127;
     option subnet-mask 255.255.255.240;
     option routers 157.157.56.113;
     deny unknown-clients;
     range 157.157.56.114 157.157.56.126;
     host Nededza-Masura-Jozef {
                         hardware ethernet c4:e9:84:f7:f6:31;
                         fixed-address 157.157.56.114;
                         }
     host Nededza-25-Mravec-Marian {
                         hardware ethernet e4:be:ed:b8:b6:d1;
                         fixed-address 157.157.56.115;
                         }
         }
}

shared-network 003 {
     # varin-private
     subnet 10.64.32.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.47.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.32.1;
         range 10.64.32.2 10.64.47.254;
         }
     # varin-public
     subnet 157.157.56.160 netmask 255.255.255.224 {
         option broadcast-address 157.157.56.191;
         option subnet-mask 255.255.255.224;
         option routers 157.157.56.161;
         deny unknown-clients;
         range 157.157.56.162 157.157.56.190;
         host Varin-VJ-control {
             hardware ethernet b8:69:f4:0d:59:b9;
             fixed-address 157.157.56.162;
             }
         host Varin-VAIN-sro {
             hardware ethernet 6c:3b:6b:0a:fa:96;
             fixed-address 157.157.56.163;
             }
         }
     }


shared-network 004 {
     # visnove-private
     subnet 10.64.48.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.63.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.48.1;
         range 10.64.48.2 10.64.63.254;
         }
     # visnove-public
     subnet 157.157.56.144 netmask 255.255.255.240 {
         option broadcast-address 157.157.56.159;
         option subnet-mask 255.255.255.240;
         option routers 157.157.56.145;
         deny unknown-clients;
         range 157.157.56.1157 157.157.56.158;
         host Visnove-skola {
             hardware ethernet e4:8d:8c:78:93:6d;
             fixed-address 157.157.56.1157;
             }
         host Visnove-Mikomix {
             hardware ethernet e4:be:ed:0f:07:bc;
             fixed-address 157.157.56.147;
             }
         host Visnove-NH-Media {
             hardware ethernet b8:69:f4:f4:cd:e6;
             fixed-address 157.157.56.148;
             }
         }
     }

shared-network 005 {
     # vysoka-private
     subnet 10.64.64.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.79.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.64.1;
         range 10.64.64.2 10.64.79.254;
         }
     # vysoka-public
     subnet 157.157.56.48 netmask 255.255.255.240 {
         option broadcast-address 157.157.56.63;
         option subnet-mask 255.255.255.240;
         option routers 157.157.56.49;
         deny unknown-clients;
         range 157.157.56.50 157.157.56.62;
         host Vysoka-1340-Zapalka-Pavol {
             hardware ethernet d8:0d:17:74:53:48;
             fixed-address 157.157.56.50;
             }
         }
     }

shared-network 006 {
     # podvysoka-private
     subnet 10.64.80.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.95.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.80.1;
         range 10.64.80.2 10.64.95.254;
         }
     # podvysoka-public
     subnet 157.157.57.128 netmask 255.255.255.192 {
         option broadcast-address 157.157.57.191;
         option subnet-mask 255.255.255.192;
         option routers 157.157.57.129;
         deny unknown-clients;
         range 157.157.57.130 157.157.57.190;
         host Rakova-K-STORE {
             hardware ethernet bc:16:65:45:08:0e;
             fixed-address 157.157.57.130;
             }
         host Staskov-Kontakt-SK {
             hardware ethernet cc:2d:e0:98:22:98;
             fixed-address 157.157.57.132;
             }

         }
     }

shared-network 007 {
     # krasno-private
     subnet 10.64.96.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.111.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.96.1;
         range 10.64.96.2 10.64.111.254;
         }
     # krasno-public
     subnet 157.157.57.192 netmask 255.255.255.224 {
         option broadcast-address 157.157.57.223;
         option subnet-mask 255.255.255.224;
         option routers 157.157.57.193;
         deny unknown-clients;
         range 157.157.57.194 157.157.57.222;
         host Krasno-Komad-sro {
             hardware ethernet 4c:9e:ff:78:97:57;
             fixed-address 157.157.57.194;
             }
         host Krasno-Kalinov-Kristek {
             hardware ethernet 50:c7:bf:08:51:c9;
             fixed-address 157.157.57.195;
             }
         host Krasno-1413-Auto-omega {
             hardware ethernet 84:16:f9:24:d1:e0;
             fixed-address 157.157.57.196;
             }
         }
     }

shared-network 008 {
     # zborov-private
     subnet 10.64.112.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.127.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.112.1;
         range 10.64.112.2 10.64.127.254;
         }
     # zborov-public
     subnet 157.157.57.224 netmask 255.255.255.224 {
         option broadcast-address 157.157.57.255;
         option subnet-mask 255.255.255.224;
         option routers 157.157.57.225;
         deny unknown-clients;
         range 157.157.57.226 157.157.57.254;
         host Zborov-2-Kral {
             hardware ethernet 04:8d:38:b9:27:6a;
             fixed-address 157.157.57.226;
             }
         host Zborov-dom-dochodcov {
             hardware ethernet e4:be:ed:69:63:8d;
             fixed-address 157.157.57.227;
             }
         }
     }

shared-network 009 {
     # besenova-private
     subnet 10.64.128.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.143.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.128.1;
         range 10.64.128.2 10.64.143.254;
         }
     # besenova-public
     subnet 157.157.60.208 netmask 255.255.255.240 {
         option broadcast-address 157.157.60.223;
         option subnet-mask 255.255.255.240;
         option routers 157.157.60.209;
         deny unknown-clients;
         range 157.157.60.210 157.157.60.222;
         host Besenova-Sedik {
             hardware ethernet cc:2d:e0:2b:94:f0;
             fixed-address 157.157.60.210;
             }
         host Besenova-Remenar {
             hardware ethernet 04:8d:38:bd:0a:c4;
             fixed-address 157.157.60.211;
             }
         }
     }


shared-network 010 {
     # vazec-private
     subnet 10.64.144.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.159.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.144.1;
         range 10.64.144.2 10.64.159.254;
         }
     # vazec-public
     subnet 157.157.60.224 netmask 255.255.255.240 {
         option broadcast-address 157.157.60.239;
         option subnet-mask 255.255.255.240;
         option routers 157.157.60.225;
         deny unknown-clients;
         range 157.157.60.226 157.157.60.238;
         host Vazec-Brtan {
             hardware ethernet 78:8a:20:bc:bb:bb;
             fixed-address 157.157.60.226;
             }
         host Vazec-Zubaj-hotel {
             hardware ethernet ac:84:c6:81:75:a2;
             fixed-address 157.157.60.227;
             }
         }
     }

shared-network 011 {
     max-lease-time 600;
     default-lease-time 600;
     # rakova-private
     subnet 10.64.160.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.175.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.160.1;
         range 10.64.160.2 10.64.175.254;
         }
     # rakova-public
         subnet 157.157.59.160 netmask 255.255.255.224 {
         option broadcast-address 157.157.59.191;
         option subnet-mask 255.255.255.224;
         option routers 157.157.59.161;
         deny unknown-clients;
         range 157.157.59.162 157.157.59.190;
         }
     }


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: strange behavior of shared network

Simon Hobson
Milan Kovac <[hidden email]> 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.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: strange behavior of shared network

Milan Kovac
Hi Simon,

I changed config by your suggestion ( hosts definition in global scope ).

The problem is still here:

Oct  4 09:01:02 dhcpserver dhcpd[9794]: DHCPDISCOVER from
10:27:be:12:08:a7 via 10.64.160.1: unknown client

Do you have some idea please?

Thanks in advance

Milan

Now my config is:

# option definitions common to all supported networks...
option domain-name "tes-media.sk";
option domain-name-servers 178.18.67.3, 178.18.67.1;
allow bootp;
default-lease-time 600;
max-lease-time 600;
allow unknown-clients;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

# default
subnet 46.151.63.224 netmask 255.255.255.240 {}

# hosts definitions
# clients with public IP addresses DIVINA

host Divinka-Uhliarik           {hardware ethernet
cc:2d:e0:3f:fa:42;fixed-address 46.151.56.130;}
host Divinka-Obecny-Urad        {hardware ethernet
00:4f:74:31:b4:03;fixed-address 46.151.56.131;}

# clients with public IP addresses NEDEDZA
host Nededza-Masura-Jozef       {hardware ethernet
c4:e9:84:f7:f6:31;fixed-address 46.151.56.114;}
host Nededza-25-Mravec-Marian   {hardware ethernet
e4:be:ed:b8:b6:d1;fixed-address 46.151.56.115;}

# clients with public IP addresses VARIN
host Varin-VJ-control           {hardware ethernet
b8:69:f4:0d:59:b9;fixed-address 46.151.56.162;}
host Varin-VAIN-sro             {hardware ethernet
6c:3b:6b:0a:fa:96;fixed-address 46.151.56.163;}
host Varin-Strasky              {hardware ethernet
64:66:b3:40:b8:ff;fixed-address 46.151.56.164;}
host Varin-skola                {hardware ethernet
fc:ec:da:43:16:7f;fixed-address 46.151.56.165;}
host Krasnany-Zakopcan          {hardware ethernet
74:4d:28:a2:39:c6;fixed-address 46.151.56.166;}
host Varin-Plastymat            {hardware ethernet
40:4a:03:8d:73:80;fixed-address 46.151.56.167;}
host Varin-Jozek                {hardware ethernet
40:e2:30:2d:37:69;fixed-address 46.151.56.168;}
host Krasnany-Vnuk              {hardware ethernet
94:0c:6d:fe:3a:c7;fixed-address 46.151.56.169;}
host Krasnany-Stancik           {hardware ethernet
e4:be:ed:0e:fe:c5;fixed-address 46.151.56.170;}
host Strecno-Wifi-VJ-control    {hardware ethernet
b8:69:f4:e7:a4:7a;fixed-address 46.151.56.171;}
host Varin-OU-1                 {hardware ethernet
bc:3f:8f:f4:36:f0;fixed-address 46.151.56.172;}
host Varin-OU-2                 {hardware ethernet
00:15:5d:01:e7:08;fixed-address 46.151.56.173;}

# clients with public IP addresses VISNOVE
host Visnove-skola              {hardware ethernet
e4:8d:8c:78:93:6d;fixed-address 46.151.56.146;}
host Visnove-Mikomix            {hardware ethernet
e4:be:ed:0f:07:bc;fixed-address 46.151.56.147;}
host Visnove-NH-Media           {hardware ethernet
b8:69:f4:f4:cd:e6;fixed-address 46.151.56.148;}

# clients with public IP addresseS VYSOKA
host Vysoka-1340-Zapalka-Pavol  {hardware ethernet
d8:0d:17:74:53:48;fixed-address 46.151.56.50;}

# clients with public IP addresses PODVYSOKA
host Rakova-K-STORE             {hardware ethernet
bc:16:65:45:08:0e;fixed-address 46.151.57.130;}
host Staskov-Kontakt-SK         {hardware ethernet
cc:2d:e0:98:22:98;fixed-address 46.151.57.132;}
host Staskov-Kontakt-SK-2       {hardware ethernet
cc:2d:e0:98:25:97;fixed-address 46.151.57.133;}
host Olesna-692-Kontakt-SK      {hardware ethernet
7c:8b:ca:ff:37:a9;fixed-address 46.151.57.161;}
host Podvysoka-209-Vahancik     {hardware ethernet
e4:be:ed:0d:ce:15;fixed-address 46.151.57.138;}
host Podvysoka-422-3pack-group  {hardware ethernet
24:a4:3c:71:d1:70;fixed-address 46.151.57.142;}
host Staskov-19-Mikulenka       {hardware ethernet
e4:be:ed:bd:52:9e;fixed-address 46.151.57.146;}
host Olesna-226-Regulus-sro     {hardware ethernet
e4:be:ed:bd:51:a4;fixed-address 46.151.57.154;}
host Staskov-303-Husar          {hardware ethernet
e4:be:ed:bd:51:a4;fixed-address 46.151.57.160;}
host Rakova-OU                  {hardware ethernet
d4:ca:6d:0a:f8:9a;fixed-address 46.151.57.131;}
host Olesna-Kontakt-SK          {hardware ethernet
7c:8b:ca:ff:b7:a9;fixed-address 46.151.57.134;}
host Podvysoka-13-Jana-Abahaziova-docasna {hardware ethernet
18:0f:76:38:a4:ca;fixed-address 46.151.57.135;}
host STASKOV-805-SAKSON-BETON   {hardware ethernet
74:4d:28:3e:77:94;fixed-address 46.151.57.136;}
host Rakova-Wifi4EU-conect      {hardware ethernet
18:e8:29:42:24:85;fixed-address 46.151.57.137;}
host Olesna-Lukas-Strycek       {hardware ethernet
74:4d:28:3e:8f:16;fixed-address 46.151.57.139;}

# clients with public IP addresses KRASNO
host Krasno-Komad-sro           {hardware ethernet
4c:9e:ff:78:97:57;fixed-address 46.151.57.194;}
host Krasno-Kalinov-Kristek     {hardware ethernet
50:c7:bf:08:51:c9;fixed-address 46.151.57.195;}
host Krasno-1413-Auto-omega     {hardware ethernet
84:16:f9:24:d1:e0;fixed-address 46.151.57.196;}
host Krasno-1277-Sarlina        {hardware ethernet
68:5d:43:71:96:7a;fixed-address 46.151.57.197;}
host Krasno-MsU                 {hardware ethernet
50:c7:bf:2c:aa:2f;fixed-address 46.151.57.198;}
host Krasno-Kalinov-Bozek       {hardware ethernet
f0:b4:29:f4:1a:de;fixed-address 46.151.57.199;}
host Krasno-1001-Kormanec-Lukas {hardware ethernet
04:8d:38:45:93:41;fixed-address 46.151.57.200;}
host Krasno-Kysucka-1-ELLI-Slovakia {hardware ethernet
f0:9f:c2:65:40:7b;fixed-address 46.151.57.201;}

# clients with public IP addresses ZBOROV
host Zborov-2-Kral              {hardware ethernet
04:8d:38:b9:27:6a;fixed-address 46.151.57.226;}
host Zborov-dom-dochodcov       {hardware ethernet
e4:be:ed:69:63:8d;fixed-address 46.151.57.227;}
host Klubina-OU                 {hardware ethernet
b8:69:f4:f4:3b:40;fixed-address 46.151.57.228;}
host Zborov-OU                  {hardware ethernet
d4:ca:6d:24:83:d8;fixed-address 46.151.57.229;}
host Zborov-kamery              {hardware ethernet
b8:69:f4:78:ab:c3;fixed-address 46.151.57.230;}
host Zborov-289-Bukovanova-Bozena {hardware ethernet
c8:60:00:60:5f:6d;fixed-address 46.151.57.231;}
host Klubina-140-Kristek-Jozef  {hardware ethernet
50:c7:bf:08:51:c9;fixed-address 46.151.57.232;}

# clients with public IP addresses BESENOVA
host Besenova-Sedik             {hardware ethernet
cc:2d:e0:2b:94:f0;fixed-address 46.151.60.210;}
host Besenova-Remenar           {hardware ethernet
04:8d:38:bd:0a:c4;fixed-address 46.151.60.211;}

# clients with public IP addresses VAZEC
host Vazec-Brtan                {hardware ethernet
78:8a:20:bc:bb:bb;fixed-address 46.151.60.226;}
host Vazec-Zubaj-hotel          {hardware ethernet
ac:84:c6:81:75:a2;fixed-address 46.151.60.227;}

shared-network DIVINA {
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 46.151.56.128 netmask 255.255.255.240 {
         option broadcast-address 46.151.56.143;
         option subnet-mask 255.255.255.240;
         option routers 46.151.56.129;
         deny unknown-clients;
         range 46.151.56.130 46.151.56.142;
         }
}

shared-network NEDEDZA {
# nededza-private
subnet 10.64.16.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.31.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.16.1;
         range 10.64.16.2 10.64.31.254;
         }
# nededza-public
subnet 46.151.56.112 netmask 255.255.255.240 {
         option broadcast-address 46.151.56.127;
         option subnet-mask 255.255.255.240;
         option routers 46.151.56.113;
         deny unknown-clients;
         range 46.151.56.114 46.151.56.126;
         }
}

shared-network VARIN {
# varin-private
subnet 10.64.32.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.47.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.32.1;
         range 10.64.32.2 10.64.47.254;
         }
# varin-public
subnet 46.151.56.160 netmask 255.255.255.224 {
         option broadcast-address 46.151.56.191;
         option subnet-mask 255.255.255.224;
         option routers 46.151.56.161;
         deny unknown-clients;
         range 46.151.56.162 46.151.56.190;
         }
}

shared-network VISNOVE {
# visnove-private
subnet 10.64.48.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.63.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.48.1;
         range 10.64.48.2 10.64.63.254;
         }
# visnove-public
subnet 46.151.56.144 netmask 255.255.255.240 {
         option broadcast-address 46.151.56.159;
         option subnet-mask 255.255.255.240;
         option routers 46.151.56.145;
         deny unknown-clients;
         range 46.151.56.146 46.151.56.158;
         }
}

shared-network VYSOKA {
# vysoka-private
subnet 10.64.64.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.79.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.64.1;
         range 10.64.64.2 10.64.79.254;
         }
# vysoka-public
subnet 46.151.56.48 netmask 255.255.255.240 {
         option broadcast-address 46.151.56.63;
         option subnet-mask 255.255.255.240;
         option routers 46.151.56.49;
         deny unknown-clients;
         range 46.151.56.50 46.151.56.62;
         }
}

shared-network PODVYSOKA {
# podvysoka-private
subnet 10.64.80.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.95.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.80.1;
         range 10.64.80.2 10.64.95.254;
         }
# podvysoka-public
subnet 46.151.57.128 netmask 255.255.255.192 {
         option broadcast-address 46.151.57.191;
         option subnet-mask 255.255.255.192;
         option routers 46.151.57.129;
         deny unknown-clients;
         range 46.151.57.130 46.151.57.190;
         }
}

shared-network KRASNO {
# krasno-private
subnet 10.64.96.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.111.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.96.1;
         range 10.64.96.2 10.64.111.254;
         }
# krasno-public
subnet 46.151.57.192 netmask 255.255.255.224 {
         option broadcast-address 46.151.57.223;
         option subnet-mask 255.255.255.224;
         option routers 46.151.57.193;
         deny unknown-clients;
         range 46.151.57.194 46.151.57.222;

         }
}

shared-network ZBOROV {
# zborov-private
subnet 10.64.112.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.127.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.112.1;
         range 10.64.112.2 10.64.127.254;
         }
# zborov-public
subnet 46.151.57.224 netmask 255.255.255.224 {
         option broadcast-address 46.151.57.255;
         option subnet-mask 255.255.255.224;
         option routers 46.151.57.225;
         deny unknown-clients;
         range 46.151.57.226 46.151.57.254;

         }
}

shared-network BESENOVA {
# besenova-private
subnet 10.64.128.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.143.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.128.1;
         range 10.64.128.2 10.64.143.254;
         }
# besenova-public
subnet 46.151.60.208 netmask 255.255.255.240 {
         option broadcast-address 46.151.60.223;
         option subnet-mask 255.255.255.240;
         option routers 46.151.60.209;
         deny unknown-clients;
         range 46.151.60.210 46.151.60.222;
         }
}

shared-network VAZEC {
# vazec-private
subnet 10.64.144.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.159.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.144.1;
         range 10.64.144.2 10.64.159.254;
         }
# vazec-public
subnet 46.151.60.224 netmask 255.255.255.240 {
         option broadcast-address 46.151.60.239;
         option subnet-mask 255.255.255.240;
         option routers 46.151.60.225;
         deny unknown-clients;
         range 46.151.60.226 46.151.60.238;
         }
}

shared-network RAKOVA {
# rakova-private
subnet 10.64.160.0 netmask 255.255.240.0 {
         option broadcast-address 10.64.175.255;
         option subnet-mask 255.255.240.0;
         option routers 10.64.160.1;
         range 10.64.160.2 10.64.175.254;
         }
# rakova-public
subnet 46.151.59.160 netmask 255.255.255.224 {
         option broadcast-address 46.151.59.191;
         option subnet-mask 255.255.255.224;
         option routers 46.151.59.161;
         deny unknown-clients;
         range 46.151.59.162 46.151.59.190;
         }
}

Dňa 2. 10. 2019 o 21:50 Simon Hobson napísal(a):

> Milan Kovac <[hidden email]> 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.
>
> _______________________________________________
> dhcp-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: strange behavior of shared network

Milan Kovac
In reply to this post by Simon Hobson
I think I found the problem.

There can not be defined range in subnet which is for static clients.

I will test it more deeply and will give results.

In any case, thanks a lot for ideas.

Milan

Dňa 2. 10. 2019 o 21:50 Simon Hobson napísal(a):

> Milan Kovac <[hidden email]> 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.
>
> _______________________________________________
> dhcp-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: strange behavior of shared network

Sten Carlsen

-- 
Best regards 
Sten Carlsen


"No trees were killed in the making of this e-mail... however,
a large number of electrons were terribly inconvenienced."

On 4 Oct 2019, at 13.04, Milan Kovac <[hidden email]> wrote:

I think I found the problem.

There can not be defined range in subnet which is for static clients.
Well, no.

My shared network has:
192.168.16.0/24 - one single network segment
192.168.16.1 - 192.168.16.30 - static and fixed allocations
192.168.16.31 - 192.168.16.49 - static allocations
192.168.16.50 - 192.168.16.150 - class based allocation - NO router given, no internet access
192.168.16.160 - 192.168.16.195 - class based allocation - router given
192.168.16.200 - 192.168.16.254 - static and fixed allocations

192.168.161.0/24 - for unknown clients until they get a fixed address or are put into a class
192.168.161.100 - 192.168.161.150 - only unknown clients

This works fine.

Looking at the data you give, I see no conflict. Can you be more specific about the problem?


I will test it more deeply and will give results.

In any case, thanks a lot for ideas.

Milan

Dňa 2. 10. 2019 o 21:50 Simon Hobson napísal(a):
Milan Kovac <[hidden email]> 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.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: strange behavior of shared network

Simon Hobson
Sten Carlsen <[hidden email]> wrote:

> Looking at the data you give, I see no conflict. Can you be more specific about the problem?

You can't see it when it's been pointed out ?

>>>> 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;
                                            ^^^^^^^^^^^^^^

Hosts with fixed addresses that are within a dynamic range. Recipe for problems.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: strange behavior of shared network

Sten Carlsen



--
Best regards

Sten Carlsen

No improvements come from shouting:

      "MALE BOVINE MANURE!!!"

> On 4 Oct 2019, at 21.42, Simon Hobson <[hidden email]> wrote:
>
> Sten Carlsen <[hidden email]> wrote:
>
>> Looking at the data you give, I see no conflict. Can you be more specific about the problem?
>
> You can't see it when it's been pointed out ?
Right, simple. Lost in detail. My fault.

>
>>>>> 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;
>                                            ^^^^^^^^^^^^^^
>
> Hosts with fixed addresses that are within a dynamic range. Recipe for problems.
>
> _______________________________________________
> dhcp-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/dhcp-users

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: strange behavior of shared network

Milan Kovac
In reply to this post by Simon Hobson
Hi Guys,

so the problem was:

In subnet which is only for static clients, can`t be defined range.

Now everything works correctly, but strange is, that  it worked
correctly 2 years, and when I added the last 11th subnet, problem was there.

Many thanks for cooperation

Milan



Dňa 4. 10. 2019 o 21:42 Simon Hobson napísal(a):

> Sten Carlsen <[hidden email]> wrote:
>
>> Looking at the data you give, I see no conflict. Can you be more specific about the problem?
> You can't see it when it's been pointed out ?
>
>>>>> 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;
>                                              ^^^^^^^^^^^^^^
>
> Hosts with fixed addresses that are within a dynamic range. Recipe for problems.
>
> _______________________________________________
> dhcp-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: strange behavior of shared network

Simon Hobson
Milan Kovac <[hidden email]> wrote:
>Hi Guys,
>
>so the problem was:
>
>In subnet which is only for static clients, can`t be defined range.

You can have static and dynamic in one subnet - but the addresses cannot overlap.

>Now everything works correctly, but strange is, that  it worked
>correctly 2 years, and when I added the last 11th subnet, problem was
>there.

It can happen.
Did any other subnets have the same overlap between statuc & dynamic clients ? If not, then you wouldn't have triggered the issue before.
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: strange behavior of shared network

Milan Kovac
Yes, I know that ranges can`t overlap.

I have other subnets for static and dynamic cause static are public ip
addresses.

In any case it`s OK now.

Thanks again

Milan

Dňa 9. 10. 2019 o 13:54 Simon Hobson napísal(a):

> Milan Kovac <[hidden email]> wrote:
>> Hi Guys,
>>
>> so the problem was:
>>
>> In subnet which is only for static clients, can`t be defined range.
> You can have static and dynamic in one subnet - but the addresses cannot overlap.
>
>> Now everything works correctly, but strange is, that  it worked
>> correctly 2 years, and when I added the last 11th subnet, problem was
>> there.
> It can happen.
> Did any other subnets have the same overlap between statuc & dynamic clients ? If not, then you wouldn't have triggered the issue before.
> _______________________________________________
> dhcp-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users