We have had a product out for several years and not had any issues with DHCP. After doing a recent firmware update we had reports of units not initializing on Belkin routers.
I confirmed the problem using DC 10.72A, RCM5760 module and a Belkin N300 (F9K1002V5). It works on a slightly older Belkin N150 (F91009V2).
The sample program dhcp.c shipped with DC also fails, output below:
========= DHCP.C =========
Enter the following keystrokes:
0-9 toggle specified interface up/down
p ping a host
P ping the same host again
w do a HTTP HEAD request to specified host
W HTTP HEAD from the same host again
t print the interface, router, ARP and DNS server tables
r add a router entry
R delete a router entry
n add a nameserver (DNS) entry
N delete a nameserver entry
f flush an ARP table entry
i set new IP address and netmask
Interface 0 is qualified for DHCP.
Starting network (DHCP timeout 8 seconds)...
Done sock_init()
opt_callback: got option 15, length 7 on i/f 0
opt_callback: got option 0, length 128 on i/f 0
Interface # 0 is now UP
Network Parameters:
My IP Address = 0A0A0602
Netmask = FFFFFF00
DHCP fell back to defaults
Interface table:
# IP addr. Mask Up Lnk Type MTU Flags Peer/router
--
--- --- ---- ----
0 10.10.6.2 255.255.255.0 yes yes eth 1500 *D 10.0.0.1
Router table:
# Flags Address i/f Net/preference Mask/exp(sec)
--
---
0 D 10.0.0.1 0 0 0
ARP cache:
# v i ip eth ru flags
-- -- -
--
0 1 0 10.0.0.1 00:00:00:00:00:00 0 Query GW Hop
Nameserver list:
IP: 0A000001 flags: 0120
= = = = = = = = = = = = = = =
This doesn't fail when DC 10.64 is used. Does anyone have any insight into this issue? I'd rather not revert back to 10.64. I am wondering if Belkin have changed something on their side?