× NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Orbi WiFi 7 RBE973
Reply

Re: M4300 Inter-VLAN routing

M4300 Inter-VLAN routing

Hi there,

I've been trying to setup a M4300-8X8F with inter-vlan routing for hours now to no avail. I'm running the latest firmware (12.0.4.8) and have followed all the instructions found in the User Guide, inter-VLAN routing guide, countless forum entries via Google, etc. but cannot figure out what I am doing wrong.

 

My setup for the time being is fairly basic:

 

network1.jpg

 

I have 3 VLAN's configured on my M4300:

* VLAN 10 (Also Management VLAN): 10.0.10.0 /24

* VLAN 200: 192.168.10.0 /24

* VLAN 1000 (Pathway to Internet via my firewall/NAT gateway): 192.168.50.0 /24

 

What I want to achieve is inter-VLAN routing so that all can access the internet.

 

Now I've followed the instructions of all the guides which pretty much say the same thing - I have added the routable VLAN's and assigned them SVI's, I've designated two untagged ports (and set their PVID's correctly) for my two PC's and I've created another untagged port for the link to my NAT gateway.

 

I've added the static routes to the NAT gateway so it is aware of the SVI's on the M4300, and I've also configured a default route on the M4300 so the next hop of 0.0.0.0 is 192.168.50.1 (the gateway).  Also note that there are no ACL's configured at this point.

 

With that all said, I have plugged everything in a static assigned IP addresses to the PC's but am having some weird issues:

1. On the M4300 I can use the in-built ping utility and can ping 192.168.50.1, 192.168.10.5 and 10.0.10.5 successfully.

2. On PC1, I can ping 10.0.10.254 and 192.168.10.254 successfully.

3. On PC2, I can ping 192.168.10.254 and 10.0.10.254 successfully.

4. On PC1, I can ping 192.168.50.254 successfully.
5. On PC2, I cannot ping 192.168.50.254.

6. On PC1, I can ping 192.168.10.5 successfully.
7. On PC2, I can ping 10.0.10.5 successfully.
8. On both PC1 and PC2, I cannot ping 192.168.50.1.

So basically where that leaves me is inter-VLAN routing is sort of working, but I cannot ping half the network, and more importantly - I cannot ping the gateway from any VLAN and therefore cannot get internet working on any of the PC's.

Some further information:
* PC1 is running Windows 10.
* PC2 is running OSX (Macbook).
* Both PC's have their firewalls turned off.

* Global Routing and IP Routing is turned on in the M4300.

* Static Routes for both VLAN subnets have been added to the gateway.
* I have tried turning everything off and on again, as well as restoring factory defaults and setting it all up again.

 

Now I know I could pipe all the VLAN's up to the gateway and perform inter-VLAN routing on the gateway instead of the M4300, but due to the network design and workloads of this network (in production enviroment), I really need to be able to do all inter-VLAN routing on the M4300. So this is not a viable work-around solution.

Any help would be much appreciated. I am at a loss as to what might be happening at the moment.

Message 1 of 4

Accepted Solutions
TheEther
Guru

Re: M4300 Inter-VLAN routing

I can't see the picture (it takes a while for the moderators to approve it for display).

 

It's kinda hard to tell where the IP addresses are assigned.  I'm guessing that 192.168.50.254 is assigned to the M4300?  If yes, then are the static routes for the VLAN subnets pointing to 192.168.50.254?

View solution in original post

Message 2 of 4

All Replies
TheEther
Guru

Re: M4300 Inter-VLAN routing

I can't see the picture (it takes a while for the moderators to approve it for display).

 

It's kinda hard to tell where the IP addresses are assigned.  I'm guessing that 192.168.50.254 is assigned to the M4300?  If yes, then are the static routes for the VLAN subnets pointing to 192.168.50.254?

Message 2 of 4
Retired_Member
Not applicable

Re: M4300 Inter-VLAN routing

Hi @logicallysynced,

 

Welcome to the community!

Could you please do more test as below for further analysis:

1. From Firewall, check if ping 10.0.10.254/192.168.10.254 success?

2. Run CLI command 'show ip interface brief' on switch

3. Run CLI command 'show ip route' on switch

4. It's better if you can provide the tech-support file of the switch 

How do I send tech-support files from my Managed Switch to NETGEAR community moderators?

http://kb.netgear.com/app/answers/detail/a_id/31439


Hope it helps!

Regards,

EricZ
NETGEAR employee

Message 3 of 4

Re: M4300 Inter-VLAN routing

Ah this was the problem, the default gateway was set to the VLAN SVI and not the gateway VLAN's SVI. Thanks so much!!

Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 9409 views
  • 2 kudos
  • 3 in conversation
Announcements