So I re-installed my K3C as my main router. In addition, just to learn about it and be gratuitously fancy, I learned to set up my old DDWRT router working as an AP so that it would also work as a DHCP/DNS server within the same subnet. The two routers' DHCP's had different scopes though so it seemed to avoid any conflicts.
However, after 1 or 2 days, any client connecting to the K3C (wireless or wired) wouldn't get a valid DHCP IP address.
* setting up the client with a static IP would work great with the K3C.
* connecting to the AP would work great, the clients got IP addresses and could still access the internet or anything.
So it's almost like the DHCP was... tired? I had a max of 24 clients on the K3C's list, and the pool was about 75 big, so I don't think it would get filled up unless other IP's were getting reserved somehow. And I wasn't show how to see the DCHP leases in more detail.
A reboot fixed it. And I disabled my gratuitous second DHCP server, so we'll see how it works.
Yes DHCP is broadcast so the Phicomm will still see DHCP requests from clients (and be tempted to reply). I see the same behaviour as you do after a reboot. Try to enable DHCP again while it still confined in the /30. Set the DHCP pool to contain 1 IP only. And make this 1 ip the SAME ip as the LAN ip you gave the Phicomm's LAN int. This works for me. The Phicomm is still replying to every DHCP req. in my LAN but always with NACK's now (which is good) as the real DHCP server will then 'win'.
that's... interesting. And you've got it plugged into your router via a LAN (not WAN) port? Is there any problem setting the DHCP so it's set in the same subnet as the LAN. The clients that connect are happy getting their IPs from the real DHCP?
... In other news, I'm really disappointed that I don't know Chinese, because it looks like some Chinese boards are doing some really exciting things with the firmware.
http://www.right.com.cn/forum/thread-250546-1-1.html
http://www.right.com.cn/forum/thread-304861-1-1.html
http://right.com.cn/forum/thread-266825-1-1.html
it looks like they've gotten openwrt up and running, Asus-Merlin up and running (faux Blue Cave) and even the Intel SDK running. Google translate isn't really up to the task of walking me through this, and some versions are meant for a version with 512MB ram instead of 256MB.
Oh, but one of the pasted bootlogs does show the CPUs identifying as 800mhz. So at least we know that