3 weeks ago
I just purchased 3 ZenWiFi ET9 and set them up in a mesh configuration using ethernet cables as a backhaul.
I have mostly wireless devices on the network, with a handful of wired devices, in particular a NAS and Camera system. When using a PC (wired via ethernet - tried 2, a Dell Desktop and MS Surface Pro) I can't access the NAS or Cameras but can via the Suface Pro with a wireless connect and my phone. I can ping the router, but pinging either the camera or NAS returns an error. I have dumped the ARP table, reset the Network to no avail. It worked briefly once and I can surf the internet from the wired devices with no issues - which is how I am posting this chat.
Pinging 192.168.50.73 with 32 bytes of data:
Reply from 192.168.50.234: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.50.73:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
I tried contacting support, they told me to open an RMA to return the products as defective.
Any ideas?
Solved! Go to Solution.
Monday
I just ran into this on a brand new ET9. Devices couldn't ping each other between ethernet ports but each device was fully accessible from wireless and also ethernet on a different node. I confirmed that ICMP packets were making it to the destination (try tcpdump -i interface icmp) but the response didn't get back to the first device. I was using LAN ports 2 & 3 at the time. When I moved the device from port 3 to port 1, it all started working. Bonding/Link Aggregation is turned off but maybe there's a bug with that setting.
Tuesday - last edited Tuesday
That's what I am seeing as well. I saw in a cross post that hanging a switch/hub off the ET9 and plugging your ethernet devices into that also solves the problem. Again, I am hoping this makes the bug fix list.
It almost seems like the LAN ports are getting "segmented" or isolated from each other.
I put a packet sniffer on and could not see any ICMP traffic between my 2 devices when failing.