DHCPD qui ne se lance pas...

Pouknouki · Le 02/12/2013, à 04:43

Salut à tous !
Sur mon ordinateur j'essaie d'installer un réseau WiFi avec hostapd et DHCPD, le problème c'est que DHCPD n'arrive pas à se lancer et que, donc, rien ne fonctionne
Au démarrage, on me dit :

[ ok ] Starting ISC DHCP server: dhcpd[....] Starting OpenBSD Secure Shell server: sshd
[FAIL] check syslog for diagnostics. ... failed!
 failed!
[FAIL] startpar: service(s) returned failure: isc-dhcp-server ... failed!

J'ai cherché beaucoup sur internet, sans aucune réponse à ce jour. Voici le contenu de divers fichiers :
/etc/network/interfaces :

auto lo

iface lo inet loopback
iface eth0 inet dhcp

#allow-hotplug wlan0
#iface wlan0 inet manual
#wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
#iface default inet dhcp

#auto br0
#iface br0 inet dhcp
#bridge_ports eth0 wlan0

iface wlan0 inet static
  address 192.168.42.1
  netmask 255.255.255.0

up iptables-restore < /etc/iptables.ipv4.nat

/etc/dhcp/dhcp.conf :

ddns-update-style none;
#
# Sample configuration file for ISC dhcpd for Debian
#
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
#ddns-update-style none;

# option definitions common to all supported networks...
#option domain-name "example.org";
#option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600;
max-lease-time 7200;

# 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.

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

#subnet 10.254.239.0 netmask 255.255.255.224 {
#  range 10.254.239.10 10.254.239.20;
#  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
#  range dynamic-bootp 10.254.239.40 10.254.239.60;
#  option broadcast-address 10.254.239.31;
#  option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
#  range 10.5.5.26 10.5.5.30;
#  option domain-name-servers ns1.internal.example.org;
#  option domain-name "internal.example.org";
#  option routers 10.5.5.1;
#  option broadcast-address 10.5.5.31;
#  default-lease-time 600;
#  max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements.   If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
#  hardware ethernet 0:0:c0:5d:bd:95;
#  filename "vmunix.passacaglia";
#  server-name "toccata.fugue.com";
#}

# Fixed IP addresses can also be specified for hosts.   These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
#  hardware ethernet 08:00:07:26:c0:a5;
#  fixed-address fantasia.fugue.com;
#}

# You can declare a class of clients and then do address allocation
# based on that.   The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

#class "foo" {
#  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}

#shared-network 224-29 {
#  subnet 10.17.224.0 netmask 255.255.255.0 {
#    option routers rtr-224.example.org;
#  }
#  subnet 10.0.29.0 netmask 255.255.255.0 {
#    option routers rtr-29.example.org;
#  }
#  pool {
#    allow members of "foo";
#    range 10.17.224.10 10.17.224.250;
#  }
#  pool {
#    deny members of "foo";
#    range 10.0.29.10 10.0.29.230;
#  }
#}


subnet 192.168.42.0 netmask 255.255.255.0 {
range 192.168.42.10 192.168.42.50;
option broadcast-address 192.168.42.255;
option routers 192.168.42.1;
default-lease-time 600;
max-lease-time 7200;
option domain-name "local";
option domain-name-servers 8.8.8.8, 8.8.4.4;
}

Et dans mon syslog, on me dit :

Dec  2 02:33:22 raspberrypi dhcpd: Internet Systems Consortium DHCP Server 4.2.2
Dec  2 02:33:22 raspberrypi dhcpd: Copyright 2004-2011 Internet Systems Consortium.
Dec  2 02:33:22 raspberrypi dhcpd: All rights reserved.
Dec  2 02:33:22 raspberrypi dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Dec  2 02:33:22 raspberrypi dhcpd: Internet Systems Consortium DHCP Server 4.2.2
Dec  2 02:33:22 raspberrypi dhcpd: Copyright 2004-2011 Internet Systems Consortium.
Dec  2 02:33:22 raspberrypi dhcpd: All rights reserved.
Dec  2 02:33:22 raspberrypi dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Dec  2 02:33:22 raspberrypi dhcpd: Wrote 0 leases to leases file.
Dec  2 02:33:24 raspberrypi dhclient: Listening on LPF/eth0/b8:27:eb:88:cc:70
Dec  2 02:33:24 raspberrypi ifplugd(eth0)[1798]: client: Listening on LPF/eth0/b8:27:eb:88:cc:70
Dec  2 02:33:24 raspberrypi dhclient: Sending on   LPF/eth0/b8:27:eb:88:cc:70
Dec  2 02:33:24 raspberrypi dhclient: Sending on   Socket/fallback
Dec  2 02:33:24 raspberrypi ifplugd(eth0)[1798]: client: Sending on   LPF/eth0/b8:27:eb:88:cc:70
Dec  2 02:33:24 raspberrypi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Dec  2 02:33:24 raspberrypi ifplugd(eth0)[1798]: client: Sending on   Socket/fallback
Dec  2 02:33:24 raspberrypi ifplugd(eth0)[1798]: client: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Dec  2 02:33:24 raspberrypi dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Dec  2 02:33:24 raspberrypi ifplugd(eth0)[1798]: client: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Dec  2 02:33:24 raspberrypi dhclient: DHCPOFFER from 192.168.0.1
Dec  2 02:33:24 raspberrypi ifplugd(eth0)[1798]: client: DHCPOFFER from 192.168.0.1
Dec  2 02:33:24 raspberrypi dhclient: DHCPACK from 192.168.0.1
Dec  2 02:33:24 raspberrypi ifplugd(eth0)[1798]: client: DHCPACK from 192.168.0.1
Dec  2 02:33:25 raspberrypi dhcpd:
Dec  2 02:33:25 raspberrypi dhcpd: No subnet declaration for wlan0 (no IPv4 addresses).
Dec  2 02:33:25 raspberrypi dhcpd: ** Ignoring requests on wlan0.  If this is not what
Dec  2 02:33:25 raspberrypi dhcpd:    you want, please write a subnet declaration
Dec  2 02:33:25 raspberrypi dhcpd:    in your dhcpd.conf file for the network segment
Dec  2 02:33:25 raspberrypi dhcpd:    to which interface wlan0 is attached. **
Dec  2 02:33:25 raspberrypi dhcpd:
Dec  2 02:33:25 raspberrypi dhcpd:
Dec  2 02:33:25 raspberrypi dhcpd: Not configured to listen on any interfaces!

Quelqu'un aurait une idée ?
Merci !

bruno · Le 02/12/2013, à 10:50

Tu as peut-être une erreur de syntaxe dans ton fichier de configuration :

Dec  2 02:33:25 raspberrypi dhcpd: No subnet declaration for wlan0 (no IPv4 addresses)

Vérifie avec :

dhcpd -t

tes interfaces ne sont sans doute pas (ou mal) configurées :

Dec  2 02:33:25 raspberrypi dhcpd: Not configured to listen on any interfaces!

Vérifie le fichier /etc/default/isc-dhcp-server

Dernière modification par bruno (Le 02/12/2013, à 10:51)

Pouknouki · Le 02/12/2013, à 13:55

Salut
En ce qui concerne la commande, voici ce qu'elle a retourné :

Internet Systems Consortium DHCP Server 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Donc apparemment aucun message d'erreur...
Je ne pense pas que mon interfaces soit mal configuré, j'ai vérifié à plusieurs reprises après mes recherches sur Google à propos de ce problème

bruno · Le 02/12/2013, à 15:05

Dec  2 02:33:25 raspberrypi dhcpd: Not configured to listen on any interfaces!

Ton serveur dhcp n'est en écoute sur aucune interface !

Que contient le fichier /etc/default/dhcpcd (je suppose que tu es sous Debian vu qu'il s'agit d'un raspberrypi) ? En particulier la ligne INTERFACES=

Pouknouki · Le 03/12/2013, à 04:39

Bon... à force d'échecs je suis passé à dnsmasq qui semble mieux fonctionner

ddriss · Le 18/01/2014, à 08:05

Réponse à Bruno
Dec 2 02:33:25 raspberrypi dhcpd: Not configured to listen on any interfaces!
veut dire qu'il faut éditer l'interface sur laquelle ton serveur dhcp ecoutera pour satisfaire les requetes des clients
voici comment proceder:
root@port:~# ifconfig
eth1 Link encap:Ethernet HWaddr 00:1e:ec:3e:eb:c0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)

lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:65536 Metric:1
Packets reçus:403 erreurs:0 :0 overruns:0 frame:0
TX packets:403 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
Octets reçus:35326 (35.3 KB) Octets transmis:35326 (35.3 KB)

vmnet1 Link encap:Ethernet HWaddr 00:50:56:c0:00:01
inet adr:192.168.222.1 Bcast:192.168.222.255 Masque:255.255.255.0
adr inet6: fe80::250:56ff:fec0:1/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)

vmnet2 Link encap:Ethernet HWaddr 00:50:56:c0:00:02
inet adr:172.16.154.1 Bcast:172.16.154.255 Masque:255.255.255.0
adr inet6: fe80::250:56ff:fec0:2/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:c0:00:08
inet adr:192.168.131.1 Bcast:192.168.131.255 Masque:255.255.255.0
adr inet6: fe80::250:56ff:fec0:8/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr 00:16:ea:be:dd:94
inet adr:192.168.0.26 Bcast:192.168.0.255 Masque:255.255.255.0
adr inet6: 2a01:e35:398b:9a0:216:eaff:febe:dd94/64 Scope:Global
adr inet6: fe80::216:eaff:febe:dd94/64 Scope:Lien
adr inet6: 2a01:e35:398b:9a0:3459:62c7:b22a:5742/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:68319 erreurs:0 :0 overruns:0 frame:0
TX packets:43581 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
Octets reçus:87306937 (87.3 MB) Octets transmis:6347876 (6.3 MB)

root@port:~#
ici j'ai plusieurs cartes qui sont wlan0 vmnet8 vmnet2 vmnet1 lo eth1

il faut faire la commande suivante :

gedit /etc/default/isc-dhcp-server

# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/isc-dhcp-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACES="wlan0 " <==== c'est ici qu'il faut indiquer l'interface d’écoute !!!

et redémarrer ton serveur :

root@port:~# service isc-dhcp-server restart
isc-dhcp-server stop/waiting

Pouknouki · Le 18/01/2014, à 09:13

Bravo du déterrage !
En tout cas je ne testerai pas votre solution puisque dnsmasq fonctionne...

structure · Le 22/04/2018, à 00:27

bonsoir,

J'ai récupéré un petit PC Eee PC (Atom 32 bits) et j'ai installé une distribution Lubuntu pour transformer ce PC en un serveur de réseau.

Le premier service que j'aimerais mettre en route est un serveur DHCP.

Je reprends depuis l'installation de Lubuntu :

sudo apt-get upgrade

sudo apt-get install net-tools

sudo apt-get install isc-dhcp-server

service --status-all

...
[ + ] network-manager
...
[ - ] isc-dhcp-server
...

sudo nano /etc/hosts

127.0.0.1 localhost
127.0.1.1 server-01

sudo nano /etc/networks

default 0.0.0.0
loopback 127.0.0.0
link-local 169.254.0.0

sudo nano /etc/network/interfaces

auto lo
iface lo inet loopback

auto enp3s0
iface enp3s0 inet static
      address 192.168.1.1
      netmask 255.255.255.0
      gateway 192.168.1.254

sudo nano /etc/default/isc-dhcp-server

INTERFACES="enp3s0"

sudo nano /etc/dhcp/dhcpd.conf

log-facility local7;

ddns-update-style none;
default-lease-time 600;
max-lease-time 7200;

authoritative;

option broadcast-address 192.168.1.255;
option routers 192.168.1.254;
option domain-name-servers 192.168.1.1;
option netbios-name-servers 192.168.1.1;
option domain-name "csa-fkb.fr";

subnet 192.168.1.0 netmask 255.255.255.0
{
     range 192.168.1.11 192.168.1.100;
}

sudo service network-manager restart
sudo service isc-dhcp-server restart

et... le service isc-dhcp-server ne démarre pas

je tape :

sudo ifconfig enp3s0 192.168.1.1
sudo service network-manager restart
sudo service isc-dhcp-server restart

et... le service isc-dhcp-server démarre !

Seulement voilà si le serveur s'éteint et redémarre, le service isc-dhcp-server ne démarre pas !!!

Pour informations :

cat /etc/*-release

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.10
DISTRIB_CODENAME=artful
DISTRIB_DESCRIPTION="Ubuntu 17.10"
NAME="Ubuntu"
VERSION="17.10 (Artful Aardvark)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 17.10"
VERSION_ID="17.10"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=artful
UBUNTU_CODENAME=artful

dans une autre console :

tail -f /var/log/syslog

Dernière modification par structure (Le 22/04/2018, à 00:36)

bruno · Le 22/04/2018, à 08:04

Bonjour,

Si tu utilises le service réseau « classique », c.-à-d. une configuration via /etc/network/interfaces, il vaut mieux désactiver NetworkManager :

sudo systemctl stop NetworkManager
sudo systemctl disable NetworkManager

structure · Le 22/04/2018, à 17:53

Merci Bruno,

Et si je préfère utiliser NetworkManager... Je vais partir sur une autre stratégie.

structure · Le 22/04/2018, à 21:34

Un grand merci à Bruno de m'avoir mis sur la piste, ce qui suit est quasiment un tutoriel :

- Installation de Lubuntu en bootant sur une carte SD flashée avec une maquette iso en utilisant etcher (https://etcher.io/).

sudo apt-get upgrade

sudo apt-get install net-tools

sudo apt-get install isc-dhcp-server

service --status-all

...
[ + ] network-manager
...
[ - ] isc-dhcp-server
...

sudo nano /etc/hosts

127.0.0.1 localhost
127.0.1.1 server-01

sudo nano /etc/networks

default 0.0.0.0
loopback 127.0.0.0
link-local 169.254.0.0

sudo nano /etc/network/interfaces

auto lo
iface lo inet loopback

sudo nano /etc/NetworkManager/system-connections/Connexion_Filaire

[connection]
id=Connexion_Filaire
uuid=0f1c831f-bec5-34d6-8f35-58b0160bbf4e
type=ethernet
autoconnect-priority=-999
interface-name=enp3s0
permissions=
timestamp=1524422684

[ethernet]
mac-address=00:24:8C:D3:94:77
mac-address-blacklist=

[ipv4]
address1=192.168.1.1/24,192.168.1.254
dns-search=
method=manual

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ip6-privacy=0
method=auto

sudo nano /etc/NetworkManager/system-connections/NOKIA_Lumia_735_NTI

[connection]
id=NOKIA_Lumia_735_NTI
uuid=501dce03-7655-44f6-b601-61f98f6087b3
type=wifi
interface-name=wlp2s0
permissions=
timestamp=1524425267

[wifi]
mac-address=00:15:AF:DC:91:06
mac-address-blacklist=
mode=infrastructure
seen-bssids=D0:92:9E:7F:5D:7E;
ssid=NOKIA Lumia 735 NTI

[wifi-security]
key-mgmt=wpa-psk
psk=motdepasse

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ip6-privacy=0
method=auto

sudo nano /etc/default/isc-dhcp-server

INTERFACES="enp3s0"

sudo nano /etc/dhcp/dhcpd.conf

log-facility local7;

ddns-update-style none;
default-lease-time 600;
max-lease-time 7200;

authoritative;

option broadcast-address 192.168.1.255;
option routers 192.168.1.254;
option domain-name-servers 192.168.1.1;
option netbios-name-servers 192.168.1.1;
option domain-name "csa-fkb.fr";

subnet 192.168.1.0 netmask 255.255.255.0
{
     range 192.168.1.11 192.168.1.100;
}

sudo service network-manager restart
sudo service isc-dhcp-server restart

je teste...

J'ai éteins le server et, je l'ai juste rallumé, sans me logger. Et ça marche !

Ci-dessous des commandes qui m'on été utilies :

Dans un terminal dédié à cet usage :

tail -f /var/log/syslog

Dans un autre terminal les commandes utiles à la construction de ma configuration :

service --status-all (liste des services installés)
cat /etc/*-release (description de la distribution linux installée)

Suppléments :

Mon serveur DHCP doit pouvoir partager sa connexion Internet avec les PC reliés au LAN.

sudo nano /etc/NetworkManager/system-connections/NOKIA_Lumia_735_NTI

[connection]
id=NOKIA_Lumia_735_NTI
uuid=501dce03-7655-44f6-b601-61f98f6087b3
type=wifi
interface-name=wlp2s0
permissions=
timestamp=1527515097

[wifi]
mac-address=00:15:AF:DC:91:06
mac-address-blacklist=
mode=adhoc
seen-bssids=D0:92:9E:7F:5D:7E;
ssid=NOKIA Lumia 735 NTI

[wifi-security]
group=ccmp;
key-mgmt=wpa-psk
pairwise=ccmp;
proto=rsn;
psk=

[ipv4]
dns-search=
method=shared

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ip6-privacy=0
method=ignore

Dernière modification par Nuliel (Le 02/12/2018, à 12:35)

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 02/12/2013, à 04:43

DHCPD qui ne se lance pas...

#2 Le 02/12/2013, à 10:50

Re : DHCPD qui ne se lance pas...

#3 Le 02/12/2013, à 13:55

Re : DHCPD qui ne se lance pas...

#4 Le 02/12/2013, à 15:05

Re : DHCPD qui ne se lance pas...

#5 Le 03/12/2013, à 04:39

Re : DHCPD qui ne se lance pas...

#6 Le 18/01/2014, à 08:05

Re : DHCPD qui ne se lance pas...

#7 Le 18/01/2014, à 09:13

Re : DHCPD qui ne se lance pas...

#8 Le 22/04/2018, à 00:27

Re : DHCPD qui ne se lance pas...

#9 Le 22/04/2018, à 08:04

Re : DHCPD qui ne se lance pas...

#10 Le 22/04/2018, à 17:53

Re : DHCPD qui ne se lance pas...

#11 Le 22/04/2018, à 21:34

Re : DHCPD qui ne se lance pas...

Pied de page des forums