NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
white_noise
Aug 23, 2021Aspirant
Switch configuration advice
Hello community
I am really struggling with this one and have tried quite a few things before posting here. I am hoping someone in the community can lend some advice.
We have a Netgear M4300-24XF switch which is connected to 2 ESXi servers, to 1 NAS device and finally to Sophos XGS 3100.
The switch is operating on all ports untagged VLAN 1 on VLAN Management IP address 10.10.50.253 and has its default gateway set to 10.10.50.254 which is the Sophos XGS device (connected on port 21)
Our devices are set to use gateway 10.10.50.253 so that traffic flows through the switch and is then forwarded to Sophos XGS at 10.10.50.254.
The current issue is that no traffic is flowing through to the Sophox XGS, devices that have the gateway 10.10.50.253 are unable to ping each other. I have seen somewhere that in order for the traffic to route to the device on port 21, I would need to assign an IP address to this port. Is this correct or should the setup just work as it currently is?
Kind regards
2 Replies
Welcome to the Netgear Community!
Can't see any representation in the network layout for the 10.10.50.x/? subnet to the gateway - just a public IP there. While looking at the topology, we see IP addresses on what appears to be a link, not on an adapter or interface or device.
Further on, public and private IPv4 addresses on the same flat network rep the VLAN 50? Shudder....
More? Appears you expect the M4300 do _routing_ (you name it forward - thre is no such thing in IPv4, at least not in this context) within the same private 10.10.50.x/? subnet. Any routing, any router requires two different IPv4 subnets ... otherwise the can't know to which path, to which interface sending the packets to.
Ping on the local network with the private 10.10.50.x/?, on the same broadcast domain, on the vary same IPv4 subnet? This happens direct in L2, the default gateway isn't in the play at all. Something must be really configured beyond mess on this small network....
Other things looking strange to me are the 103.157.68.x/? addresses are sometimes going to the VLAN 1, sometimes associated with the VLAN 50. Is this /24 network subnetted any further?
What is the idea if having two links to the QNAP with one IP address on each adapter?
Are these two VLAN 1 and 50 run both tagged on all connections, or sometimes also untagged? If ports are untagged, is the PVID set accordingly?
Lots of questions, but I hope this gives some ideas where to start. I would suggest a piece of paper and a pencil.
Regards,
-Kurt
- white_noiseAspirant
Thanks for your reply. I have updated the network and the topology to have the devices in VLAN1 on 10.10.51.0/24 and interface 1 as 10.10.50.253
Devices are able to get to the switch, the ARP table all looks good and shows the local vms. These vms arent able to ping to the gateway 10.10.50.254 however. I cannot ping the 10.10.50.254 from the switch either.
Routes are shown below. What am I doing wrong in the config? Any help is greatly appreciated.
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 1/0/1 10.10.50.254 253 0 10.10.50.0 255.255.255.0 Local Connected 1/0/1 10.10.50.253 0 0 10.10.51.0 255.255.255.0 Local Connected vlan 1 10.10.51.253 0 0
Related Content
NETGEAR Academy

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