Routing subnet traffic problems

[whsbuss]

I have Verizon FiOS and their ActionTec router. Currently I have an Asus RT-AC68U router set in AP mode connected as a subnet off the Actiontec router. I'm testing a Cisco router connected w/double NAT (need guest networking) on a different subnet.

Using my test Cisco E4200 router WAN->ActionTecLAN setup works well: any connected device on Cisco can connect to the Internet and NAS, printer, cameras on ActionTec subnet. What does not work is connection/pinging from ActionTec subnet to Cisco subnet.

Here's my config:
192.168.1.1 - ActionTec router
192.168.1.50 to 254 ActionTec DHCP range
192.168.1.33 static IP for WAN on Cisco, with 255.255.255.0 and gateway 192.168.1.1
192.168.100.1 Cisco LAN IP

I also set a static route in the ActionTec (Advanced->Routing->AddRoute) which is 192.168.100.0, 255.255.255.0, Gateway 192.168.1.33, Metric 0

With a PC connected to the ActionTec LAN pinging the IP for the Cisco WAN (192.168.1.33) never responds. And of course pinging 192.168.100.1 fails as well.

I think I need an additional static route on the ActionTec but not sure what is should be. The ping packets show a redirect to the 1.33 IP and then a Src and Dest with the correct IPs.

 

[abailey]

You mention double NAT. If you have NAT enabled on the Cisco you won't be able to ping the 192.168.100 network from the 192.168.1 network. Because of the nature of NAT you should be able to ping from the 192.168.100 network to the 192.168.1 network though.

 

[whsbuss]

You mention double NAT. If you have NAT enabled on the Cisco you won't be able to ping the 192.168.100 network from the 192.168.1 network. Because of the nature of NAT you should be able to ping from the 192.168.100 network to the 192.168.1 network though.

Yes that in fact works. I could live with my local devices (NAS, printer and cameras) on the ActionTec LAN since uPNP on the ActionTec allows remote access. And with the double NAT I can access the Internet and devices. But I do have a Windows PC which has to remain on the 1.x subnet and it would be nice to access the Cisco LAN.