0 MEMBUAT DHCP SERVER

Salam sejahtra buat para pembaca. Materi postingan saya kali ini yaitu Membuat DHCP SERVER Dimana :
FUNGSI: untuk memberikan dan mengatur ip client secara otomatis

Langsung saja….

Langkah-langkah konfigurasi DHCP Server

1. Konfigurasi IP Address untuk SERVER
#vim /etc/network/interface auto lo
iface lo inet loopback


# The primary network interface allow-hotplug eth1
iface eth1 inet static address 192.168.2.29

netmask 255.255.255.128

network 192.168.2.0

broadcast 192.168.2.127

gateway 192.168.2.1
# dns-* options are implemented by the resolvconf package, if installed dns-nameservers 202.134.0.155
dns-search smkn1-sdk.sch.id
Simpan :wq
restart networknya : /etc/init.d/networking restart
Cek IP
debian:~# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:24:01:31:24:48
inet addr:192.168.2.29

Bcast:192.168.2.127

Mask:255.255.255.128

inet6 addr: fe80::224:1ff:fe31:2448/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:595 errors:0 dropped:0 overruns:0 frame:0
TX packets:346 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:422290 (412.3 KiB) TX bytes:56330 (55.0 KiB) Interrupt:225 Base address:0xce00

2. Mencari paket program, lakukan dengan perintah berikut
Sebelum mencari paket pastikan sources list ada sudah ter setting yaitu dengan cara
#vim /etc/apt/sources.list
Tambahkan deb ftp://118.98.171.229/debian etch main contrib non-free
Tekan esc :wq
Setelah itu lakukan pencarian packet dengan perintah

# apt-cache search dhcp
dhcp - DHCP server for automatic IP address assignment dhcp-client - DHCP Client
dhcp-helper - A DHCP relay agent dhcp-relay - DHCP Relay

dhcp3-client - DHCP Client
dhcp3-common - Common files used by all the dhcp3* packagesdhcp3-dev - API for accessing and modifying the DHCP server and client state
dhcp3-relay - DHCP Relay
dhcp3-server - DHCP server for automatic IP address assignment dhcpcd - DHCP client for automatically configuring IPv4 net--More--

Menginstall Paket DHCP
debian:~# apt-get install dhcp3-server
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
dhcp3-server
0 upgraded, 1 newly installed, 0 to remove and 0 not upgrad ed. Need to get 292kB of archives.
After unpacking 836kB of additional disk space will be used . WARNING: The following packages cannot be authenticated! dhcp3-server
Install these packages without verification [y/N]? y
Get:1 ftp://118.98.171.229 etch/main dhcp3-server 3.0.4-13 [292kB] Fetched 292kB in 0s (2932kB/s)
Preconfiguring packages ...
Selecting previously deselected package dhcp3-server.
(Reading database ... 62133 files and directories currently installed.) Unpacking dhcp3-server (from .../dhcp3-server_3.0.4-13_i386 .deb) ... Setting up dhcp3-server (3.0.4-13) ...
Generating /etc/default/dhcp3-server...
Starting DHCP server: dhcpd3 failed to start - check syslog for diagnostics. invoke-rc.d: initscript dhcp3-server, action "start" failed .



3. Konfigurasi SERVER DHCP
a. Kopi dulu konfigurasi asli dhcp
debian:~# cp /etc/dhcp3/dhcpd.conf /etc/dhcp3/dhcpd.conf.ASLI
b. Edit file dhcpd.conf
debian:~# vim /etc/dhcp3/dhcpd.conf
# 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 "smkn1-sdk.sch.id";
option domain-name-servers 202.134.1.10, 202.134.0.155;

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 192.168.2.0 netmask 255.255.255.128 {
range 192.168.2.1 192.168.2.5;
option routers 192.168.2.1;
}

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

simpan : esc wq

c. edit file /etc/default/dhcp3-server
debian:~# vim /etc/default/dhcp3-server
# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/dhcp3-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1". INTERFACES="eth1"
~
simpan : esc wq

4. Restrat dhcp server
debian:~# /etc/init.d/dhcp3-server restart

5. Menguji DHCP SERVER
Pakai komputer client: Pada komputer client diset pemberian ip addressnya pakai dhcp. Kemudian restart network komputer client

Kalau dapat ip address sesuai dengan network server ==> DHCP server nya sukses…

Selamat mencoba….