In my home lab environment, I use a server to manage DHCP, DNS, WINS, and other such services - a common occurrence amongst folks in the technology field who use their home environment for continuous learning. My router serves as a gateway to the Internet as well as a reasonably priced firewall and I typically use WiFi AP's to manage wireless connectivity to my LAN (currently DWL-G700AP /w MAC filtering, WPA2). This configuration has worked quite well until recently, where my DGL-4100 is exhibiting common signs of hardware failure ... and the reason why I'm looking at the DIR-857 as a reasonable cost alternative.
In early D-Link routing products, router functionality such as MAC filtering was not dependent on DHCP being enabled. Although a significant number of folks may use the built-in router DHCP sevice daemon, not all do. Challenges that seem to continously plague D-Link are:
- Lack of clear (detailed) documentation
- Quality control
- Less than satisfactory implementation of standards/features/functionality
I've been using D-Link products since the DI-704, have recommended various models over the years to my clients, and have deployed, configured, and managed home office, soho, and enterprise class D-Link devices. I have additionally deployed various other networking devices from various other OEM's and can assure you that disabling DHCP shouldn't cripple device functionality.
In the interest of keeping a certain level of decorum; it would appear that our philosophies - and those of D-Link whom you represent - of networking device operation no longer appear to be aligned.
Regards,