Sorry, that is simply not true. We have a similar set up at home and use both DHCP and static addresses from the same address block. It works fine. Some PC get their addresses from the DHCP server (software in the Linksys router), others use assigned static IPs.
We don't do it, but the device can be configured to only allocate DHCP IPs from a small range of numbers. Unless you have a giant LAN that is using almost all the addresses, this is not a problem.
Since the poster indicated that they have a small LAN, simply assign a static IP outside of the 'normal' range of DHCP allocations.
And, if I'm not mistaken, ARP should make this moot in many DHCP servers; i.e. a good DHCP server should check its ARP cache before assiging an IP to check to see if it is in use on the segment.
For example, here is a quote from:
http://www.networkpenetration.com/dhcp_flaws.html
Quote:
|
Some DHCP servers issue ARP requests or ICMP pings to detect for IP addresses that may be reclaimed by the server. This is done as operating systems / interfaces do not release there assigned IP address when shutdown. Basic testing of the denial of service code successfully defeat the ARP method of reclaiming IP addresses (ICMP method was not tested) as the number and speed of requests for IP addresses was significantly higher than the number of ARP requests issued by the DHCP server (when running multiple copies of the source code in a script). The source code could be extended to sniff for ARP requests / ICMP ping requests and reply accordingly thus defeating the servers method of reclaiming addresses.
|
OBTW: if you are operating your own small private LAN, you don't need to be worried about the hypothetical DHCP vulnerability above.
