Instalação DHCP server

Generating /etc/default/isc-dhcp-server...

insserv: warning: script 'S20debian.noip2.sh' missing LSB tags and overrides

insserv: warning: script 'S20noip' missing LSB tags and overrides

insserv: warning: script 'debian.noip2.sh' missing LSB tags and overrides

Starting ISC DHCP server: dhcpdcheck syslog for diagnostics. ... failed!

 failed!

invoke-rc.d: initscript isc-dhcp-server, action "start" failed.

Configurando dhcp3-server (4.1.1-P1-15+squeeze3) ... 

#! /bin/sh



# /etc/init.d/noip2.sh







# Supplied by no-ip.com



# Modified for Debian GNU/Linux by Eivind L. Rygge <eivind@rygge.org>



# corrected 1-17-2004 by Alex Docauer <alex@docauer.net>







# . /etc/rc.d/init.d/functions  # uncomment/modify for your killproc







DAEMON=/usr/local/bin/noip2



NAME=noip2







test -x $DAEMON || exit 0







case "$1" in



    start)



    echo -n "Starting dynamic address update: "



    start-stop-daemon --start --exec $DAEMON



    echo "noip2."



    ;;



    stop)



    echo -n "Shutting down dynamic address update:"



    start-stop-daemon --stop --oknodo --retry 30 --exec $DAEMON



    echo "noip2."



    ;;







    restart)



    echo -n "Restarting dynamic address update: "



    start-stop-daemon --stop --oknodo --retry 30 --exec $DAEMON



    start-stop-daemon --start --exec $DAEMON



    echo "noip2."



    ;;







       *)



    echo "Usage: $0 {start|stop|restart}"



    exit 1



esac



exit 0 

#! /bin/sh



# /etc/init.d/noip2.sh







# Supplied by no-ip.com



# Modified for Debian GNU/Linux by Eivind L. Rygge <eivind@rygge.org>



# corrected 1-17-2004 by Alex Docauer <alex@docauer.net>







# . /etc/rc.d/init.d/functions  # uncomment/modify for your killproc







DAEMON=/usr/local/bin/noip2



NAME=noip2







test -x $DAEMON || exit 0







case "$1" in



    start)



    echo -n "Starting dynamic address update: "



    start-stop-daemon --start --exec $DAEMON



    echo "noip2."



    ;;



    stop)



    echo -n "Shutting down dynamic address update:"



    start-stop-daemon --stop --oknodo --retry 30 --exec $DAEMON



    echo "noip2."



    ;;







    restart)



    echo -n "Restarting dynamic address update: "



    start-stop-daemon --stop --oknodo --retry 30 --exec $DAEMON



    start-stop-daemon --start --exec $DAEMON



    echo "noip2."



    ;;







                                *)



    echo "Usage: $0 {start|stop|restart}"



    exit 1



esac



exit 0 

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



#  }



#} 

Nov 10 13:26:04 debian dhcpd: No subnet declaration for eth1 (no IPv4 addresses).

Nov 10 13:26:04 debian dhcpd: ** Ignoring requests on eth1.  If this is not what

Nov 10 13:26:04 debian dhcpd:    you want, please write a subnet declaration

Nov 10 13:26:04 debian dhcpd:    in your dhcpd.conf file for the network segment

Nov 10 13:26:04 debian dhcpd:    to which interface eth1 is attached. **

Nov 10 13:26:04 debian dhcpd:

Nov 10 13:26:04 debian dhcpd:

Nov 10 13:26:04 debian dhcpd: Not configured to listen on any interfaces! 

    subnet 192.168.0.0 netmask 255.255.255.0 {

    option routers 192.168.0.254;

    option subnet-mask 255.255.255.0;

    option domain-name-servers 8.8.4.4,8.8.8.8;

    option time-offset -10800;

    authoritative;

    next-server 192.168.0.254;

    range 192.168.0.15 192.168.0.99;

    }