We have a Comcast Netgear 3000DCR on premises.
Configuration on the LAN side is 192.168.1.1 with mask=255.255.255.0
We also have a block of 13 IPs provided by Comcast for servers in the DMZ.
Our LAN static range is 192.168.1.1 - 192.168.1.63. We dont use the Netgear for DHCP or DNS instead we have a Server 2008R2 machine doing both DHCP and DNS and is itself is static at 192.168.1.6x
DHCP is serves addresses from 192.168.1.64 - 192.168.1.254. Servers in the DMZ and workstations in the LAN (192.168.1.x) are working correctly.
However, due to the mobile devices that come/go, we are running out of scope on the 192.168.1.x subnet and so to add another subnet onto the network and purchased a Cisco RV180.
I configured the WAN port on the Cisco as 192.168.1.3
I configured the LAN port on the Cisco as 10.3.0.1
I added a static route on the Netgear as follows:
Destination = 10.3.0.0, Mask = 255.255.0.0, Gateway = 192.168.1.3
From within the Comcast Netgear:
I can ping and traceroute 192.168.1.3...but..I cannot traceroute to 10.3.0.1
From within the Cisco:
I can ping and traceroute 192.168.1.1 and the DNS server at 192.168.1.6x...but I cannot traceroute to 188.8.131.52 (which is the Comcast DNS).
I've checked the (confusing) box which says "Disable firwall for true IP static only"
Either a firewall in the Netgear is blocking traffic or the static route configured in the Netgear is not working for some reason.
Any help appreciated.
FWIW, I paid the extra $180 for a "one time solve" ticket with Premium Support and the experience has been beyond frustrating as those guys seems to know less about IP routing and this equipment than I do. I thought I had it all working and then they "factory defaulted" the Netgear some 3 times in the middle of the working day, due to their error, blowing away all my config each time.
What is the config on the Cisco router ? Did you set a default gateway for it (to 192.168.1.1) ? Also as you're adding a new subnet , the Netgear needs to NAT that subnet or the 10.3.0.0/16 ip range will not be able to reach the outside world (internet).
I don't have a Netgear so I can't realy help you more than this but at least checked these few things.
Thanks for the reply but...the Cisco WAN port is configured as: Static IP 192.168.1.3 and Default gateway 192.168.1.1
From within the Cisco, I can ping and traceroute to 192.168.1.1 and indeed any device in the 192.168.1.x range, just cannot get beyond that and back (eg to 184.108.40.206)
I assume the 10.3.0.0/16 range will be NATed by the Netgear, same as always; dont see any reason why not.
FWIW - I had this working before the factory reset imposed by "Premium Support"
So all the machine in the 192.168.1.0/24 subnet can access (ping) the machines in the 10.3.0.0/16 subnet (and the other way around) ?
If not, then the issue is on the Cisco, if yes then there is definitelly an issue on the Netgear static routing and natting.
I don't use my comcast gateway as a router (I have a cisco 2801 behind it and all NAT is disable as well as the firewall ("fir true static routing") on my SMC gateway. But as the interface are the same I'll do my best to help you.
If you could give us a few screen grab of the Netgear config (blank out any personal/private info ) that could help.
I have a LyncSys E2000...pretty much the same problem. My configuration worked until the Comcast guy came today and switched out my router. The configuration is my Cable Modem is 10.1.10.1, with a WAN IP for DHCP and static. I use port 4, with a connection to the E2000 Internet Port. I set up the WAN of the E2000 to be 10.1.10.2, gateway of .1, and the internal network to the WiFi as 192.168.1.0, 255.255.255.0.
In the Comcast Business Gateway, the device that hosts the 10.1.10.1 gateway, I configure a static route to identify the 192.168.1.0 network and the gateway to this network is 10.1.10.2.
This configuration used to work and now it it no longer works with this new devivce thy added today. I assume they have some sort of firewall restriction that only allows 10.1.10.0 addresses and the the other addresses are not allowed.
My guess is the Comcast gateway is only doing NAT (Masquerading) for the 10.1.10.0/24 subnet and not fot the other subnet you might be routing to internaly.
You might want to try changing the netmasl for the 10.1.10.0 subnet for a /23 (netmask would be 255.255.254.0) and then add a static route to 10.1.11.0/24 via your internal router and use 10.1.11.0/24 instead of 192.168.x.y for the subnet for your dynamic devices.
Wih this the whole /23 would be natted by the comcast gateway and you would have a more specific route to a /24 for your device routed via your internal router.
This would work with normal networking equipment (Cisco, Juniper, Arista, Quanta ....) , not sure about the Comcast "business" gateway but you could try.