Bonjour,
Depuis un moment, je rencontre quelque soucis sur mon réseau qui fonctionné bien.
Dans les paquets que j’ai installé il y a bind9 longtemps utilisé et isc-dhcp-server qui lui été simple au premières abord mais je crois que non.
mon réseau est simple
Ma bbox de Bouygues qui récupérer tout les connexion wifi (switch, xbox, playstation, android, portable (qubesOS et windobe), iphone,…) puis un switch qui géré l’ensemble de mes connexion Ethernet dont mon ordinateur sur windows (console de jeux que j’appellerais Wonsole), mon ordinateur de travaille (debian buster) et suivie d’un cpl qui va vers ma télé et le serveur(debian buster) qui lui comprends lecteur vidéo, serveur pxe pour installation en réseau,… et surtout le dns et le dhcp (seul et unique sur le réseau car désactivé sur la bbox).
Le problème c’est que depuis peu de temps, j’ai 1 soucis qui reviens. C’est l’incapacité que ma Wonsole de reçois l’ip que le dhcp doit lui attribué. Pourtant, quand je lui attribue une ip fixe avec la gateway et le dns du serveur. Tout fonction.
Mais les problème on continué car après avoir réglé les soucis que Wonsole le problème a sauté sur le portable Windows que j’ai. j’ai procédé au réglage identique a Wonsole mais rien n’y fait et même Wonsole a recommencé a ne plus fonctionné alors que je croyais les avoir réglés.
Et aujourd’hui le problème a empiré plus aucun des appareils ne peux ce connecté au réseau wifi et Ethernet cause de non attribution des ips . Et le serveur lui ne sort plus du tout.
J’ai remarqué ça depuis le début mon Wonsole ou je voulais installé une Debian via réseau a fonctionné un temps avec le serveur pxe. Mais ne fonctionné plus après malgré qu’en ouvrant un client tft sur une debian ou QubesOs fonctionné parfaitement.
Les fichiers config que j’ai modifié :
/etc/dhcp/dhcpd.conf
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
authoritative;
# option definitions common to all supported networks...
option domain-name "srv.world";
option domain-name-servers 192.168.1.1, 192.168.1.254;
ignore client-updates;
default-lease-time 600;
max-lease-time 7200;
# 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;
# 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.
host srv {
hardware ethernet 6c:3b:e5:39:9a:9c;
fixed-address 192.168.1.1;
}
host box {
hardware ethernet AC:3B:77:83:9E:AC;
fixed-address 192.168.1.254;
}
subnet 192.168.1.0 netmask 255.255.255.0 {
pool {
# option domain-name-servers 192.168.1.1;
range 192.168.1.100 192.168.1.200;
option routers 192.168.1.254;
# default-lease-time 21600;
# max-lease-time 36000;
}
# option broadcast-address 192.168.1.255;
# option subnet-mask 255.255.255.0;
# filename "pxelinux.0";
}
#group {
# next-server 192.168.1.1;
# host tftclient {
# filename "pxelinux.0";
# }
#}
# 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.example.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 movies {
# hardware ethernet 6c:3b:e5:39:9a:9c;
# fixed-address 192.168.1.2;
#}
# 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;
# }
#}
fichier /etc/default/isc-dhcp-server
# Defaults for isc-dhcp-server (sourced by /etc/init.d/isc-dhcp-server)
# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
DHCPDv4_CONF=/etc/dhcp/dhcpd.conf
#DHCPDv6_CONF=/etc/dhcp/dhcpd6.conf
# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
#DHCPDv4_PID=/var/run/dhcpd.pid
#DHCPDv6_PID=/var/run/dhcpd6.pid
# Additional options to start dhcpd with.
# Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
#OPTIONS=""
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACESv4="enp3s0"
#INTERFACESv6="enp3s0"
/etc/network/interface
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
/etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
auto enp3s0
iface enp3s0 inet static
address 192.168.1.1
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.254
up service isc-dhcp-server restart
). pardon… 
