|Cable connected to LAN ports on both routers. The only config mentioned that I am not seeing is somewhere to define the Default Gateway on the secondary router outside of the DHCP configuration.|
Within in the static LAN settings of your second router there should be a default gateway setting. If not, I'm very much surprised. It's not a huge deal mind you since the router's LAN interface itself does not need to go beyond the boundaries of the subnet.
Two additional things I now noticed:
- The secondary router has logs that states it is not getting a response to DHCP requests
That's odd because the router should not be requesting DHCP information. Likely that's the external (internet/WAN) interface on the router doing DHCP requests. Shut that off if you can. I suspect you'll have to change the external interface to "static" from "DHCP" in order to make that quit.
- I can ping the secondary router from the ping tool on the primary router admin interface but I cannot ping the secondary router from a host connected to the primary router
This is likely because the second router's firewall is set to not respond to ICMP (ping) requests. As long as clients connecting to the second router (wired or wireless) are getting proper TCP/IP settings from the DHCP server on the primary router, and are able to surf the internet, then all is well and you don't need to worry about it.
Shouldn't the DHCP range include the secondary router? Something like 192.168.254.1 to 192.168.254.200 or at least the secondary router's fixed IP should fall between the above parameters like 192.168.254.101 ?
Nope, you don't want the second router's IP within your DHCP scope. First off, who needs 200 available IP's in a home environment.........LOL
Second, you run the risk of a duplicate IP error if you include statically assigned IP's within the scope of your DHCP. For instance, if the statically assigned device is off, DHCP may give that IP to a DHCP client. Then, when you power up the statically assigned device, you get a dupe error and the statically assigned device can't communicate.
Typically one uses reservations or exclusions within DHCP for statically assigned IP's but it's been my experience, especially in the home or small business environments, that leaving a block of IP's not included in the scope amounts to the same thing and saves a tiny bit of admin time. Since most SOHO routers have a scope of 100 to 199 by default, you have 1-99 to use for static stuff so I always pick IP's for server's, my NAS, my printer, etc from that series of addresses.
It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.