M4300 routing table Next Hop is Mgmt IP

Hi Rich7475​ ,

You shouldn't apologize for a "dumb" question, if you are stumped it means that it might be useful for other members of the community here.

If 10.0.10.1 is a router (firewall gateway), can you connect to its interface and use the troubleshooting section of its GUI to try to ping 10.0.10.1 from there? What you have described in your M4300 configuration is correct for 10.0.10.0/24 management VLAN 10 and its gateway, so you need to verify that gateway on the other side. Because if it was down or if 10.0.10.0/24 was not existing on it, then the routing table in the M4300 wouldn't show it. Reversely, if the default gateway was accessible and working, the routing table of the M4300 should show one default route like 0.0.0.0/0 [253/0] via 10.0.10.1... It is normal that the next hop is 10.0.10.252 for that subnet, this is your VLAN 10 routing interface - the default route should be there for 0.0.0.0 instead. But for that it needs to be up?

Please test your 10.0.10.1, as it looks like there is a communication issue (maybe L1 cabling issue?) between your M4300 and this gateway. If no communication between the two, then the link must be assessed, including the port configuration (VLAN PVID etc.)

Last, when you will have figured out, don't forget to enter the opposite static routes in your 10.0.10.1 gateway for your other VLANs - if only untagged 10.0.10.0/24 in the gateway. There's no need of any static route in your gateway for 10.0.10.0/24 if it has an interface for it, but for your other VLANs you need their subnets and the indication of their downstream 10.0.10.252 gateway for each of them, each time in your gateway (static routes section).

If you can't figure it out, it will be difficult to ask you to post the tech-support file here on this forum, you should open a case at our technical support if this is an IT installation, or send an email at mailto:ProAVDesign@netgear.com if this is an AV installation.

I hope it helps, Laurent