I just upgraded to an Asus RT-N66U and installed Shibby's v136 release (tomato-RT-N66U_RT-AC6x--136-AIO-64K). Everything is mostly working great, except DHCP. I have always used a Windows DHCP server and it works fine. Previously I had an Asus RT-N12 with v121 release (tomato-K26-1.28.RT-N5x-MIPSR2-121-Max). DHCP is disabled on the router and all wired clients work fine. The wireless clients are no longer able to renew the DHCP lease after the upgrade in routers/firmware. If I enable DHCP on the router (in addition to the Windows DHCP server - but with a different range) all the wireless devices seem to work fine. Though they mostly get their DHCP address from the original Windows server, presumably just depending on which server replies first. I have not tried to trace packets on the lan but it certainly appears that the DHCP requests from the wireless lans are not propagating to the wired lan in able to obtain an address. Enabling the internal router DHCP then allows this, in addition to also providing addresses. Has anyone else experienced anything like this? Any suggestions on what to try or how to debug it farther? I plan to try installing v121 on this router to see if it solves the problem. At the new location for the RT-N12 I am using the internal DHCP, so it has no problems with v136. Thanks.