isc-dhcp-server (4.3.4-1) en Stretch con problemas

4 envíos / 0 nuevos
Último envío
#1 Sáb, 23/04/2016 - 19:01
EtHome
Imagen de EtHome
Desconectado/a
se unió: 09/04/16

isc-dhcp-server (4.3.4-1) en Stretch con problemas

Estado: 
[ACTIVO]

Buenas Noches a todos, les traigo una nueva duda a todos, anoche en una locura decidi pasar el server de casa de 8.4 a la furuta version 9.

Me encontre con muchos cambios entre ellos abandonar la rama 3.1* del kernel linux para arrancar con 4.5*

isc-dhcp-server incormpora dhcpd6.conf para redes IPv6 y si el mismo fichero no arranca.

Lo raro aqui es que la configuracion vieja deberia funcionar en IPV4 segun tngo entendido, es mas al arrancarlo nos da todo OK y el status nos da OK, pero no atiende ninguna peticion, alguien tiene idea que puede ser??

Config dhcp.conf 

root@Server-Home:/home/cbacigalupo# cat /etc/dhcp/dhcpd.conf
ddns-update-style none;
shared-network Lan01 {
        subnet 192.168.90.0 netmask 255.255.255.0 {
        option routers 192.168.90.1;
        option subnet-mask 255.255.255.0;
        option broadcast-address 192.168.90.255;
        option domain-name "server-home.cabgroupsrl.com.ar";
        option domain-name-servers 192.168.90.1, 8.8.4.4, 8.8.8.8, 208.67.222.222;
        option netbios-name-servers 192.168.90.1;
        option netbios-node-type 8;
        option ntp-servers 192.168.90.1, 200.23.51.205, 132.248.81.29, 148.234.7.30;
        option interface-mtu 1492;
        range 192.168.90.50 192.168.90.100;
        default-lease-time 600;
        max-lease-time 7200;
        ddns-updates on;
        authoritative;
        do-forward-updates on;
        }
######################################################################################
###########################Equipos del Local 1.2 al 1.10####################
        host Ip-tel-01 {
                option host-name "ip-tel-01.server-home.cabgroupsrl.com.ar";
                hardware ethernet  00:0E:08:E5:38:ED;
                fixed-address 192.168.90.2;
                }

        host Santiago-PC {
                option host-name "santiago-pc.server-home.cabgroupsrl.com.ar";
                hardware ethernet  BC:5F:F4:D0:6C:40;
                fixed-address 192.168.90.3;
                }

        host Leonel-PC {
                option host-name "leonel-pc.server-home.cabgroupsrl.com.ar";
                hardware ethernet  74:D4:35:F5:45:6C;
                fixed-address 192.168.90.4;
                }

        host Nexus-5 {
                option host-name "nexus5-carlos.server-home.cabgroupsrl.com.ar";
                hardware ethernet  34:FC:EF:B5:E1:89;
                fixed-address 192.168.90.5;
                }

        host Notebook-Carlos {
                option host-name "notebook-carlos.server-home.cabgroupsrl.com.ar";
                hardware ethernet  78:E4:00:56:28:B5;
                fixed-address 192.168.90.6;
                }

        host Netbook-Leo {
                option host-name "netbook-Leo.server-home.cabgroupsrl.com.ar";
                hardware ethernet  20:16:D8:8C:EB:50;
                fixed-address 192.168.90.7;
                }

        host Moto-GII {
                option host-name "moto-gII-leo.server-home.cabgroupsrl.com.ar";
                hardware ethernet  1C:56:FE:C6:4C:52;
                fixed-address 192.168.90.8;
                }

        host AP-Casa {
                option host-name "AP-Casa.server-home.cabgroupsrl.com.ar";
#               hardware ethernet  00:18:E7:02:48:90;
                hardware ethernet  E8:DE:27:82:2c:4A;
                fixed-address 192.168.90.9;
                }

        host Francisco {
                option host-name "francisco.server-home.cabgroupsrl.com.ar";
                hardware ethernet  D0:50:99:54:B3:CE;
                fixed-address 192.168.90.10;
                }

        host Notebook-Mama {
                option host-name "Note-mama.server-home.cabgroupsrl.com.ar";
                hardware ethernet  00:25:D3:0B:EE:17;
                fixed-address 192.168.90.11;
                }

        host Celu-Mama {
                option host-name "celu-mama.server-home.cabgroupsrl.com.ar";
                hardware ethernet  00:02:66:5E:FC:01;
                fixed-address 192.168.90.12;
                }

        host Netbook-Leo-II {
                option host-name "netbook-Leo-II.server-home.cabgroupsrl.com.ar";
                hardware ethernet  20:16:D8:C8:E7:1E;
                fixed-address 192.168.90.13;
                }

}
######################################################################################

 

Config dhcpd6.conf

root@Server-Home:/home/cbacigalupo# cat /etc/dhcp/dhcpd6.conf
default-lease-time 600;
max-lease-time 7200;
log-facility local7;
subnet6 2001:db8:0:1::/64 {
        # Range for clients
        range6 2001:db8:0:1::129 2001:db8:0:1::254;

        # Range for clients requesting a temporary address
        range6 2001:db8:0:1::/64 temporary;

        # Additional options
        option dhcp6.name-servers fec0:0:0:1::1;
        option dhcp6.domain-search "domain.example";

        # Prefix range for delegation to sub-routers
        prefix6 2001:db8:0:100:: 2001:db8:0:f00:: /56;

        # Example for a fixed host address
        host specialclient {
                host-identifier option dhcp6.client-id 00:01:00:01:4a:1f:ba:e3:60:b9:1f:01:23:45;
                fixed-address6 2001:db8:0:1::127;
                }
}
root@Server-Home:/home/cbacigalupo#

 

Tcpdump de las peticiones

 

root@Server-Home:/home/cbacigalupo# tcpdump -n -i eth0 port bootps or port bootpc
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
18:25:40.138084 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314
18:25:42.164991 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314
18:25:47.169923 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314
18:25:55.941009 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314
18:26:10.679760 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314
18:26:34.456628 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314
18:26:39.480977 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314
18:26:43.333180 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314
18:26:51.593936 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314
18:27:06.122539 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314
18:27:13.598821 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 34:fc:ef:b5:e1:89, length 314

 

Servicio que informa estar corriendo, pero sin atender

root@Server-Home:/home/cbacigalupo# /etc/init.d/isc-dhcp-server status
● isc-dhcp-server.service - LSB: DHCP server
   Loaded: loaded (/etc/init.d/isc-dhcp-server; bad; vendor preset: enabled)
   Active: active (exited) since sáb 2016-04-23 18:39:31 ART; 20min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 19352 ExecStop=/etc/init.d/isc-dhcp-server stop (code=exited, status=0/SUCCESS)
  Process: 19365 ExecStart=/etc/init.d/isc-dhcp-server start (code=exited, status=0/SUCCESS)

abr 23 18:39:31 Server-Home systemd[1]: Starting LSB: DHCP server...
abr 23 18:39:31 Server-Home systemd[1]: Started LSB: DHCP server.
root@Server-Home:/home/cbacigalupo#

 

 

Alguien tiene idea de que puede estar ocurriendo???

Sáb, 23/04/2016 - 22:23
DenJohX
Imagen de DenJohX
Desconectado/a
colaborador
se unió: 22/04/16

El servicio parece haberse cerrado (exited). Revisa los logs de sistema para ver algún mensaje de error.

Reinicia el servicio y mira si suelta algo en syslog o dmesg.

:wq

Dom, 24/04/2016 - 10:50 (Responder a #2)
EtHome
Imagen de EtHome
Desconectado/a
se unió: 09/04/16

Si eso lo habia visto pero el reinicio da OK y no reporta nada en ningun lado

 

Dom, 24/04/2016 - 10:52
EtHome
Imagen de EtHome
Desconectado/a
se unió: 09/04/16

También lo puedo atribuir a que este server viene de Debian 7 de su version Testing a Debian 8 y ahora a Debian 9 testing, voy a hacer una instalación limpia esta tarde con el CD de Testing Alplha 5 esta tarde y les cuento