Static lease IP dhcp within dynamic range pool

dhcpdhcp-serverfedora

I am using fedora 13.

I want to statically bind a MAC to IP. Now the problem is if the IP is within the range pool, it may get allocated to some other host also. For that I use a tweak, where I insert a entry in dhcpd.leases (although not recommended). Can anyone recommend a better solution. My requirement is, if I statically bind IP to a host then no matter what, it should be assigned to that host only. It is ok if I need to update the dhcp version, only problem is that I cannot update the fedora version, due to some reasons.

I referred this this link but has no solution to allow static binding of IP within the range pool.

Best Answer

Use a reservation as shown in Example 10.3. Static IP address using DHCP to fix the address to a particular MAC.

The reserved address is not allocated to any other host requesting an address.

Related Solutions

Cisco – How to combine static and dynamic DHCP leases on a Cisco router

You almost got it working ,

In your staticmap file just change the Type of '1' to : 'id' ,

static file :

*time* Sep 3 2012 11:10 AM
*version* 1
!IP address    Type    Hardware address     Lease expiration
10.0.0.8 /8     id       0100.301b.473d.d8       Infinite
10.0.0.28 /8    id       0184.8f69.b77b.dc       Infinite
*end*

And the config snippet :

!
ip dhcp pool StaticBindings
 origin file flash:static-bindings
 default-router 10.0.0.1
 dns-server 10.0.0.1
 netbios-name-server 10.0.0.1
!

Works like a charm. ( Cisco 3945E )

No internet after dhcp lease renews

"My best guess at the moment is a rogue wifi router in one of our dorm rooms on the 10.1.1.0/24 subnet with a bad gateway."

This happened in my office. The offending device turned out to be a rogue android device:

http://code.google.com/p/android/issues/detail?id=11236

If the android device gets the gateway's IP from another network via DHCP, it may join your network and start responding to ARP requests for the gateway IP with it's MAC. Your use of the common 10.1.1.0/24 network increases the probability of this rogue scenario.

I was able to check the ARP cache on an affected workstation on the network. There, I observed an ARP flux problem where the workstation would flip-flop between the correct MAC and a MAC address from some rogue device. When I looked up the suspicious MAC the workstation had for the gateway, it came back with a Samsung prefix. The astute user with the troubled workstation replied that he knew who had a Samsung device on our network. Turned out to be the CEO.

Best Answer

Related Solutions

Cisco – How to combine static and dynamic DHCP leases on a Cisco router

No internet after dhcp lease renews

Related Topic