Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

Pages : 1

Discussion fermée

#1 Le 07/06/2016, à 15:15

Coppan

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

Bonjour!

Je galère depuis plusieurs jours à transformer mon RPi en routeur sécurisé:

en effet je n'arrive pas à faire démarrer isc-dhcp-server avec la ligne de commande sudo service isc-dhcp-server start qui me répond

Job for isc-dhcp-server.service failed.

systemctl status isc-dhcp-server.service me renvoit: 

:~ $ systemctl status isc-dhcp-server.service
● isc-dhcp-server.service - LSB: DHCP server
   Loaded: loaded (/etc/init.d/isc-dhcp-server)
   Active: failed (Result: exit-code) since Tue 2016-06-07 14:59:39 CEST; 11s ago
  Process: 1464 ExecStart=/etc/init.d/isc-dhcp-server start (code=exited, status=1/FAILURE)

et journalctl -xn n'a pas grand chose à dire

-- Logs begin at Tue 2016-06-07 00:17:01 CEST, end at Tue 2016-06-07 15:01:02 CEST. --
Jun 07 14:59:39 raspberrypi isc-dhcp-server[1464]: ^
Jun 07 14:59:39 raspberrypi isc-dhcp-server[1464]: Configuration file errors encountered -- exiting
Jun 07 14:59:39 raspberrypi isc-dhcp-server[1464]: If you think you have received this message due to a bug rather
Jun 07 14:59:39 raspberrypi isc-dhcp-server[1464]: than a configuration issue please read the section on submitting
Jun 07 14:59:39 raspberrypi isc-dhcp-server[1464]: bugs on either our web page at www.isc.org or in the README file
Jun 07 14:59:39 raspberrypi isc-dhcp-server[1464]: before submitting a bug.  These pages explain the proper
Jun 07 14:59:39 raspberrypi isc-dhcp-server[1464]: process and the information we find helpful for debugging..
Jun 07 14:59:39 raspberrypi isc-dhcp-server[1464]: exiting.
Jun 07 15:01:02 raspberrypi sudo[1482]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -xn
Jun 07 15:01:02 raspberrypi sudo[1482]: pam_unix(sudo:session): session opened for user root by pi(uid=0)

Je suis alors aller voir du côté de /etc/dhcp/dhcpd.conf, le fichier contenant les informations pour dhcpd qui permet à mon RPi d'agir spécifiquement comme un routeur...

j'ai donc 

:~ $ sudo cat /etc/dhcp/dhcpd.conf
#
# 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; #impede DHCP server to receive DNS informations from its clients

# 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; # the DHCP server has to send DHCPNAK messages to misconfigurated clients. it allows them to get an IP adress without waiting for the end of the lend

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

#added
subnet 192.168.42.33 netmask 255.255.255.0{ 
	range 192.168.42.10 192.168.42.50; 
	option broadcast-adress 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;
}

Sachant que mon adresse ip me donne:

:~ $ ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:c7:c5:66 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.33/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::c0f2:6df7:e27f:78c4/64 scope link 
       valid_lft forever preferred_lft forever

Je suis allé voir ensuite le fichier nécessaire pour configurer mon interface réseau:

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

auto lo
iface lo inet loopback

iface eth0 inet manual

allow-hotplug wlan0
iface wlan0 inet static
adress 192.168.42.1
netmask 255.255.255.0

iface wlan0 inet dhcp
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1
iface wlan1 inet manual
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

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

Je me demande si l'erreur n'est pas là dedans... adress 192.168.42.1

Ainsi que le fichier ifplugd

# This file may be changed either manually or by running dpkg-reconfigure.
#
# N.B.: dpkg-reconfigure deletes everything from this file except for
# the assignments to variables INTERFACES, HOTPLUG_INTERFACES, ARGS and
# SUSPEND_ACTION.  When run it uses the current values of those variables
# as their default values, thus preserving the administrator's changes.
#
# This file is sourced by both the init script /etc/init.d/ifplugd and
# the udev script /lib/udev/ifplugd.agent to give default values.
# The init script starts ifplugd for all interfaces listed in
# INTERFACES, and the udev script starts ifplugd for all interfaces
# listed in HOTPLUG_INTERFACES. The special value all starts one
# ifplugd for all interfaces being present.
INTERFACES="all"
HOTPLUG_INTERFACES="all"
ARGS="-q -f -u0 -d10 -w -I"
SUSPEND_ACTION="stop"

Mais je n'ai plus aucune idée pour savoir comment faire tourner isc-dhcp-server et transformer mon RPi en routeur...
Pouvez-vous m'aider?

Modération : La question a aussi été posée ici : https://forum.ubuntu-fr.org/viewtopic.p … #p21533943 . Donc celle ci est fermée.

Dernière modification par Ayral (Le 07/06/2016, à 15:30)

Inspiron15
3000 series
Ubuntu 16.04
Dual-boot avec Windows 10

Hors ligne

Pages : 1

Discussion fermée