problème DHCP

Support Debian
#1

Bonjour,

j’ai un problème pour configurer un dhcp sous debian squeeze. Je pense avoir tous correctement bien configuré, mais lorsque j’execute la commande /etc/init.d/isc-dhcp-server restart j’obtiens plusieurs failed je vais donc regarder les log et j’obtiens:

Dec 23 19:59:05 vtdebian03 dhcpd: No subnet declaration for eth0 (192.168.0.9). Dec 23 19:59:05 vtdebian03 dhcpd: ** Ignoring requests on eth0. If this is not what Dec 23 19:59:05 vtdebian03 dhcpd: you want, please write a subnet declaration Dec 23 19:59:05 vtdebian03 dhcpd: in your dhcpd.conf file for the network segment Dec 23 19:59:05 vtdebian03 dhcpd: to which interface eth0 is attached. ** Dec 23 19:59:05 vtdebian03 dhcpd: Dec 23 19:59:05 vtdebian03 dhcpd: Dec 23 19:59:05 vtdebian03 dhcpd: Not configured to listen on any interfaces!

je vais donc dans mon fichier /etc/default/isc-dhcp-server et je lui met bien comme paramètre INTERFACES= "eth0"

Mais sa ne fonctionne toujours pas. Merci de votre aide.

#2

Le message d’erreur paraît clair : aucune déclaration de sous-réseau dans le fichier de configuration ne correspond à l’adresse IP de l’interface eth0.
Contenu de dhcpd.conf et configuration IP d’eth0 ?

#3

Voici les configuration de mon interfaces:

[code]# This file describes the network interfaces available on your system

and how to activate them. For more information, see interfaces(5).

The loopback network interface

auto lo
iface lo inet loopback

The primary network interface

allow-hotplug eth0
iface eth0 inet dhcp[/code]

et maintenant le fichier dhcpd.conf:

[code]# 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.10.100.0 netmask 255.255.255.0 {

range 10.10.100.10. 10.10.100.100;

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.10.100.0 netmask 255.255.255.0 {
range 10.10.100.10 10.10.100.100;

option domain-name-servers ns1.internal.example.org;

option domain-name “internal.example.org”;

option routers 192.168.0.254;
option broadcast-address 10.10.100.255;
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;

}

#}
[/code]

#4

Hello

Deja un truc me turlupine : ton serveur dhcp est en dhcp… Essaye de le mettre en static.

Ensuite il faut que ton serveur DHCP soit dans les sous réseaux auxquels il distribue des adresses.

Tu peux nous montrer le resultat de : ifconfig

#5

Oui, faire tourner un serveur DHCP sur une interface configurée en DHCP (ce qui suppose qu’il y a déjà un autre serveur DHCP sur le réseau) c’est n’importe quoi.

Inutile de donner la sortie d’ifconfig, on connaît déjà l’adresse d’eth0 : 192.168.0.9 qui ne correspond pas au sous-réseau 10.10.100.0/24 défini dans dhcpd.conf.

#6

[code]# This file describes the network interfaces available on your system

and how to activate them. For more information, see interfaces(5).

The loopback network interface

auto lo
iface lo inet loopback

The primary network interface

allow-hotplug eth0
iface eth0 inet static
address 10.10.100.254
netmask 255.255.255.0
gateway 192.168.0.254
[/code]

Voici la configuration de mon interface

#7

Avec ça dhcpd devrait démarrer.
Par contre l’adresse de l’option gateway est incongrue car elle n’appartient pas au sous-réseau de l’interface et est donc injoignable.

#8

Oui, donc en effet, il faut que tu configures ton fichier .conf un minimum…

#9

essaye de désactiver l’option “serveur DHCP” du routeur de ta box.