NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
colinauger
Sep 17, 2018Aspirant
M4300-52G ProSAFE InterVLAN Routing
Hello,
I have a really simple setup here, a working stack with tree 4300 prosafe M4300-12X12F, M4300-52G and M4300-28G. each one with the last firmware 12.0.7.7
I have two vlan : vlan 30 (192.168.3.0/24) et vlan 40 (192.168.4.0/24). I follow this kb to create them https://kb.netgear.com/30818/How-to-configure-routing-VLANs-on-a-NETGEAR-managed-switch-with-shared-internet-access
I activate routing on each vlan #vlan routing 30 and #vlan routing 40
I activate routing for the switch (Config)#ip routing
In Learned Routes, i get :
Network Address | Subnet Mask | Protocol | Route Type | Next Hop Interface | Next Hop Address | Preference | Metric |
0.0.0.0 | 0.0.0.0 | Default | Static | vlan 30 | 192.168.3.1 | 1 | 0 |
192.168.3.0 | 255.255.255.0 | Local | Connected | vlan 30 | 192.168.3.254 | 0 | 0 |
192.168.4.0 | 255.255.255.0 | Local | Connected | vlan 40 | 192.168.4.254 | 0 | 0 |
I use my own dhcp server on each vlan with the right gateway, 192.168.3.254 for 192.168.3.0/24 subnet and 192.168.4.254 for 192.168.4.0/24 subnet.
And now, my problem:
from 192.168.3.0/24 subnet,
I ping the two gateways 192.168.3.254 and 192.168.4.256
I can ping a linux VM 192.168.4.22 but not another one with the same config on 192.168.4.10
from 192.168.4.0/24 subnet,
I ping the two gateways 192.168.3.254 and 192.168.4.256
but i can't ping anything else on 192.168.3.0/24, and not my internet gateway 192.168.3.1
I reconfigure 3 times the vlans now with the #clear config command before... I don't find what i doing wrong
Thanks for your help.
- Retired_MemberSep 21, 2018
Hi colinauger
Ok, I got your requirement.
Currently, you only face one problem:
when workstation on Vlan30, only can ping VM1, but cannot ping VM2;
but when workstation on Vlan40, both can ping VM1 and VM2, right?
Could you please double check as below step:
1. From VM1, check ping 192.168.4.254 and 192.168.3.254;
2. From VM2, check ping 192.168.4.254 and 192.168.3.254;
3 Replies
- Retired_Member
Hi colinauger
Welcome to the community!
Could you please share your network topology?
I just want to know:
1. VLAN30 IP address of switch.
2. VLAN40 IP address of switch.
3. As you say, DHCP Server(192.168.3.254 and 192.168.4.254) of VLAN30 and VLAN40 is working as Gateway role, right? If so, there is no necessary to enable routing VLAN on switch, just setup L2 VLAN is enough. As all Layer 3 packet will be forwarded by Gateway(DHCP Server).
Hope it helps!
Regards,
EricZ
NETGEAR employee- colinaugerAspirant
Hi EricZ,
Thx for your help! I certainly misanderstand key concept here.
this our network :
1. VLAN30 IP address of switch. = 192.168.3.254
2. VLAN40 IP address of switch. = 192.168.4.254
3. As you say, DHCP Server(192.168.3.254 and 192.168.4.254) of VLAN30 and VLAN40 is working as Gateway role, right? No, (see attached file) I use two dhcp server for each subnet but they are note the gateway of the subnet. I dont want to use them as gateway to avoid traffic bottleneck. On On vlan 30, it is the internet gateway, the switch default route.
from the workstation01, I ping vm1 (192.168.4.22) but not vm2 (192.168.4.21). Vm1 et vm2 are stricly identical. Of course, if i put a workstation on the vlan40, i can ping vm1 and vm2.
- Retired_Member
Hi colinauger
Ok, I got your requirement.
Currently, you only face one problem:
when workstation on Vlan30, only can ping VM1, but cannot ping VM2;
but when workstation on Vlan40, both can ping VM1 and VM2, right?
Could you please double check as below step:
1. From VM1, check ping 192.168.4.254 and 192.168.3.254;
2. From VM2, check ping 192.168.4.254 and 192.168.3.254;
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!