Pages : 1
#1 Le 18/01/2007, à 10:26
- stagiaire désespérée
new prob
bon, bah j'ai un autre prob
lorsque je fais cette commande : /etc/init.d/dhcp3-server start
il me répond ca :
* dhcpd self-test...
...fail!
Internet Systems Consortium DHCP Server V3.0.2
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
/etc/dhcp3/dhcpd.conf line 51: Expecting netmask
subnet 192.168.1.0 255.
^
Configuration file errors encountered -- exiting
J'ai été voir dans le fichier pourtant ca à l'air bon.....
#2 Le 18/01/2007, à 10:33
- KnarNantais
Re : new prob
Bonjour,
quel est le contenu de ton fichier dhcpd.conf?
------------------------------------------------------------------
Kubuntu 11.10 64 bits - KDE 4.7.1 - Fixe Montage perso - Core2 Duo E8400 - P5Q Deluxe + 4Go - Nvidia Gforce 8400 GS - 2x500 Go
"" 11.10 64 bits - Portable : ASUS K72JT-TY185V core i3 380M + 4 Go - AMD Radeon HD 6370M - 500 Go
Hors ligne
#3 Le 18/01/2007, à 10:38
- stagiaire désespérée
Re : new prob
#
# Sample configuration file for ISC dhcpd for Debian
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#
# 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 192.168.1.0 255.255.255.0 {
range 192.168.1.20 192.168.1.100;
option domain-name-servers 192.168.1.1;
#option domain-name "internal.example.org";
option routers 192.168.1.1;
option broadcast-address 192.168.1.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 Serveur {
hardware ethernet 00:10:DC:CA:F0:64;
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;
# }
#}
Voila ^^
#4 Le 18/01/2007, à 11:08
- stagiaire désespérée
Re : new prob
ouiiinnnnn
Je comprend rien moaaa a linux.....
helllpppp
#5 Le 18/01/2007, à 11:21
- stagiaire désespérée
Re : new prob
J'ai trouvé, il me manquait juste un mot
#6 Le 18/01/2007, à 11:26
- KnarNantais
Re : new prob
Eh oui, il manquait netmask.
Envolé le désepoir? ...
jusqu'au prochain os?
Bon courage
------------------------------------------------------------------
Kubuntu 11.10 64 bits - KDE 4.7.1 - Fixe Montage perso - Core2 Duo E8400 - P5Q Deluxe + 4Go - Nvidia Gforce 8400 GS - 2x500 Go
"" 11.10 64 bits - Portable : ASUS K72JT-TY185V core i3 380M + 4 Go - AMD Radeon HD 6370M - 500 Go
Hors ligne
Pages : 1