Kamis, 04 Agustus 2011

Konfigurasi DHCP server di UBUNTU Server

Posted by tomy_stemsi on 06.26

onfigurasi DHCP server di UBUNTU Server

Caranya :

1.Login sebagai Super Administrator (sudo su)
2.Installa DHCP server dengan perintah :

# apt-get install dhcpd3-server -y
3. Backup file dhcp3-server dengan perintah :

# cp /etc/default/dhcp3-server /etc/default/dhcp3-server.backup
4.Konfigurasi file dhcp3-server dengan perintah : # pico /etc/default/dhcp3-server Temukan bagian ini dan isikan interaces yang dijadikan sebagai LAN.

INTERFACES=”eth1″
5. Konfigurasi file dhcpd.conf dengan perintah : pico /etc/dhcp3/dhcpd.conf

# Sample configuration file for ISC dhcpd for Debian

#

# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as

# configuration file instead of this file.

#

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

#Perhatikan bagian ini defaulnya tanpa tanda pagar.

# 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 192.168.1.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 netmask 255.255.255.0 {

#ip addres yang akan di sewakan oleh server

range 192.168.1.25 192.168.1.40;

#DNS server yang digunakan

option domain-name-servers 202.152.5.36;

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

option routers 192.168.1.20;

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

1.Jalan service dengan perintah :

# /etc/init.d/dhcp3-server start
2.Ujicoba dilakukan dengan mengoptainkan ip addres pada client.
3.Oke selamat mencoba.

0 komentar:

Posting Komentar

  • RSS
  • Delicious
  • Digg
  • Facebook
  • Twitter
  • Linkedin

Search Site