NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Can't get extra networks to route through to the Internet
Hi,
Not sure what I'm missing here, however, I can't get two networks to route through this router to the Internet.
The existing LAN network already on the router works. Originally 192.168.0.0/24
The router delivers DHCP and routes all connected devices, cabled or wifi - no problem.
Now I want to add two extra networks. 192.168.10.0/25 and 192.168.20.0/29
Just the start there are a few more to come.
But (!) I can ping the Netgear BB router LAN interface but get no further.
I've added the relevant static routes with the gateway on the same LAN as the Netgear BB router LAN interface. So I know my config is routing to the Netgear.
The Netgear doesn't seem to want to translate the new networks out onto the Internet for some reason.
Potentially missing a setting.
Any advice?
Thanks in advance.
I'm going to assume that everyone has read my reply and run for the hills.
I'm also going to assume that the Netgear Nighthawk that I have will only NAT the network specified in the LAN settings. Therefore not a full router but a cut down version of a routing function. Understandably ideal for home use. Not what I need.
This appears to be the logical conclusion based on the results earlier.
If I'm wrong please let me know. Otherwise this may help someone in the future.
In the meantime I'm going to set up NAT on the router south of the Netgear Nighthawk. Messy - not ideal - but I need to get a move on with what I'm doing.
5 Replies
> Not sure what I'm missing here, [...]
For a start: a clear description of your equipment, and how it's all
connected and configured.> The existing LAN network already on the router works.
What is your (unspecified) "the router"? Firmware version?
Connected to what?> Originally 192.168.0.0/24
"Originally"? What is it now?
> [...] Now I want to add two extra networks. 192.168.10.0/25 and
> 192.168.20.0/29 [...]
Normally, I'd ask why, but let's imagine that you have some good
reason, and start with the basics. What, exactly, does "add a network"
mean to you? Are you adding another router to the LAN of your
(unspecified) "the router", or what? (And what might that other router
be?)> But (!) I can ping the Netgear BB router LAN interface but get no
> further."BB"? What, exactly, does "the Netgear BB router" mean to you?
"ping" from where? This might be easier to follow if you showed an
actual "ping" command with its actual output (and the IP address of the
computer where that command is run), rather than interpreting your
(invisible) results for your audience.> I've added the relevant static routes with the gateway on the same LAN
> as the Netgear BB router LAN interface. [...]
What, exactly, are these "relevant static routes", and where,
exactly, did you specify them? Again, actual facts would be more
helpful than your assurance that you did the right thing. (Especially
when whatever you did didn't work.)> [...] So I know my config is routing to the Netgear. [...]
You're way ahead of me. I still know approximately nothing about
what you've done, or what's routing what, whence or whither.> The Netgear doesn't seem to want to translate the new networks out
> onto the Internet for some reason.Again, actual facts would be more helpful than your analysis of the
apparent intentions of your (unspecified) hardware devices.> Potentially missing a setting.
Sure. Something. Someplace.
> Any advice?Generally, a useful problem description says what you did, and what
happened when you did it. As usual, showing actual actions (commands)
with their actual results (error messages, LED indicators, ...) can be
more helpful than vague descriptions or interpretations.If you're cascading routers, then you might want to add a static
route on the outer router, so that it sends messages with an
inner-subnet destination to the inner router (gateway), instead of to
your ISP, which is where it would normally send any such
foreign-destination message.Wow - OK
Device -->Netgear D7000v or Broadband Router (BB for short maybe?)
Outside Interface IP --> DHCP Provided by ISP
Inside Interface IP on Netgear D7000v or Broadband Router -->192.168.0.1
DHCP to Internal Network provided by Netgear D7000v or Broadband Router --> 192.168.0.2 to 250 on a 24 bit subnet mask
Additional Static Routes added to Netgear D7000v or Broadband Router -->192.168.10.0/25 and 192.168.20.0/29
Layer 1 is irrelevant. All using RJ45 Copper cables
ARP tables in each device clearly show the full MAC of each connected device so Layer 2 isn't an issue
PING checklist
Source
Destination
Successful
Device with IP of 192.168.0.14 directly connected to Netgear D7000v or Broadband Router
8.8.8.8
Yes
Outside Interface of Cisco 1921 router 192.168.0.251
8.8.8.8
Yes
Arista switch with SVI IP address of 192.168.10.127
8.8.8.8
No
Arista switch with SVI IP address of 192.168.10.127
192.168.0.1
Yes
This is to the Netgear D7000v2
Client attached to Arista switch with IP of 192.168.10.12
8.8.8.8
No
Client attached to Arista switch with IP of 192.168.10.12
192.168.0.1
Yes
Cisco switch with SVI IP address of 192.168.20.1
8.8.8.8
No
Cisco switch with SVI IP address of 192.168.20.1
192.168.0.1
Yes
Client attached to Cisco switch with IP of 192.168.20.6
8.8.8.8
No
Client attached to Cisco switch with IP of 192.168.20.6
192.168.0.1
Yes
Connection order
Final destination is:
Internet
router directly connected to the Internet
Netgear D7000v or Broadband Router
Internally connected to
Cisco 1941 router
which is connected on one interface to
Arista switch
and connected on the other interface
Cisco switch
Default routes
Netgear D7000v or Broadband Router
default to ISP
static route 192.168.10.0/25 Next hop 192.168.0.250
static route 192.168.20.0/29 Next hop 192.168.0.250
Cisco 1941
default route back to 192.1689.0.1
Routing table already populated with connected networks therefore further static network configuration not required at this time.
Arista switch
default route back to Cisco 1941
Cisco switch
default route back to Cisco 1941
Conclusion
The Netgear D7000v or Broadband Router is not translating the new networks.
Since there isn't a specific NAT option in the menu (outbound) then I can only assume PAT is being used. There does not appear to be a selection in the interface for PAT.
There is nowhere to configure the PAT pool or to interrogate the routing table on the Netgear D7000v or Broadband Router.
Is there a terminal / CLI interface that can be interrogated?
Sarcasm not required. An element of respect might be nice.
The level of detail you demanded (?!?!) bears absolutely no relevance to the question.
If you don't wish to help sort out what is wrong with the Netgear router then I sill simply accept your answer, close the question and open up another question for someone else to point out where I can find NAT / PAT within the Netgear D7000v or Broadband Router or alternatively, I will know that I purchased the wrong device.
I'm going to assume that everyone has read my reply and run for the hills.
I'm also going to assume that the Netgear Nighthawk that I have will only NAT the network specified in the LAN settings. Therefore not a full router but a cut down version of a routing function. Understandably ideal for home use. Not what I need.
This appears to be the logical conclusion based on the results earlier.
If I'm wrong please let me know. Otherwise this may help someone in the future.
In the meantime I'm going to set up NAT on the router south of the Netgear Nighthawk. Messy - not ideal - but I need to get a move on with what I'm doing.
I think that you should be contemplating Commercial Grade equipment.
Good Luck to you and your qwest.....
> Device -->Netgear D7000v or Broadband Router (BB for short maybe?)
"maybe?"? Don't you know what you meant? What is a "D7000v"?
D7000[v1]? D7000v2?> This is to the Netgear D7000v2
At last, an actual model number. Whew.
> Additional Static Routes added to Netgear D7000v [...]
Swell. What are those routes?
> static route 192.168.10.0/25 Next hop 192.168.0.250
> static route 192.168.20.0/29 Next hop 192.168.0.250What's at "192.168.0.250"? It deals with multiple subnets?
> The Netgear D7000v or Broadband Router is not translating the new
> networks.
I don't know what that means. "translating"?After that, you lost me completely. I've used static routes for
different subnets on my D7000[v1] with no particular trouble, but when I
did it I knew all the relevant IP addresses, and the actual route
specifications.> The level of detail you demanded (?!?!) bears absolutely no relevance
> to the question.If you believe that "I've added the relevant static routes" is an
adequate description of anything, then we might never agree on what's an
adequate description.> I'm going to assume that everyone has read my reply and run for the
> hills.
You can, of course, assume anything you wish. I tried to read it,
but I got lost in a blizzard of useless detail, and couldn't find the
information which I requested. One simple point: Rather than try to add
multiple subnets and routers at one time, I'd try to add one, and get
that to work (or not).> [...] I need to get a move on with what I'm doing.
Whatever that might be. I've lost interest in trying to help anyone
who clearly knows so much more than I about this stuff.
