Few Important Question and Answer – DHCP-(Part-2)

1

Question and Answer – DHCP

dhcpsolution

Dear Viewers,

Today we are discuss some important question and answer dynamic host configuration protocol purpose second part. Previously we are post first part .

PART-1

Q:01:- How do I compile/install DHCP?

Compiling the distribution is easy. (These directions are also in the README file which comes in the package). (Replace VERSION in the following instructions with the version of the code that you downloaded).

Uncompress and un-tar file:

%gunzip dhcp-VERSION.tar.gz

%

%tar xf dhcp-VERSION.tar

%

%cd dhcp-VERSION

Run configure:

%./configure

Complete and Install:

#make

#make install

Q:02:- Should I use a shared-network clause?

Probably not.

There is a lot of confusion about when to use the shared-network statement. The only time to use the shared-network statement is when you have 2 or more different IP subnes that share the same wire (some network floks call this one broadcast domain).

If you have one subnet on a network.Just use a single subnet {} clause to describe it.

Here is an example of the correct use of the shared-network clause:

Shared-network Inside {

Subnet 10.10.10.0 netmask 255.255.255.0 {

Range 10.10.10.128 10.10.10.254;

Option routers  10.10.10.1;

}

Subnet 192.168.2.0 netmask 255.255.255.0 {

Range 192.168.2.10 192.168.2 254;

Option routers 192.168.2.1;

}

}

This is a simple network, where the 10.10.10.0 and 192.168.2.0 networks both share the same wire. You might do this where you need more IP addresses than are available on the original network. It might be necessary to add a new network in order to support all the hosts.

Q:03:- What does “No subnet declaration for eth0” mean?

In order for the DHCP server to do its job, it needs to have an accurate description of what the network looks like. When the server starts up, it looks for all network interfaces which are up and are broadcast-type interfaces. If the server finds an interface for which there is no subnet declaration, it complaints. With versions later than 3.0b2, the server will complain, and continue on with normal operation, ignoring DHCP requests from the undefined networks.

Each interface on the server should have a subnet declaration. Having a subnet declaration does not necessarily mean that you need to serve DHCP on that interface. The declaration can be as simple as:

Subnet 192.168.1.0 netmask 255.255.255.0 {

Not authoritative;

}

This will configure the server with no information about the subnet to distribute, therefore the server will not respond with addresses on that net.

                                                                     (Continue)——————— Thanks Everyone

Share.

About Author

TN365

1 Comment

Leave A Reply

Powered by themekiller.com