Inter VLAN communication not working

Hello,
I have the following setup:
Gateway: ER605 V2
Switch: SG2008
AP: EAP653
I am using the Omada Essentials Cloud Controller (the free verion)
I have two LAN interfaces set as following:
Wired LAN (Default): 192.168.55.1/24
Wireless LAN: 192.168.56.1/24
All the devices (gateway, switch, ap) are in the Default VLAN (Wired LAN).
I have a Wifi network configured in the Wireless LAN.
2 Windows clients: one connected on Wifi (Wireless LAN) 192.168.56.100 and the other one connected on Wired LAN 192.168.55.100.
I want to be able to ping and access each other but it's not working.
When I am pinging from 192.168.55.100 (Wired LAN) to 192.168.56.100 (Wireless LAN) I am receiving: Request Timed Out.
When I am pinging from 192.168.56.100 (Wireless LAN) to 192.168.55.100 (Wired LAN) I am receiving: Destination host unreachable.
When I am pinging the Gateway from each Wired LAN or Wireless LAN, it's working. From Wired LAN I am able to ping 192.168.56.1 and from Wireless LAN I am able to ping 192.168.55.1
I have tryed creating custom port profiles, using tags. I tryied using ACLs to allow the traffic. I have tryed with different versions of Omada Software controller also. I have downgraded the ER605 V2 firwmare to a couple older versions. Without success...
What am I doing wrong?
Thank you in advance!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content

Thanks for posting in our business forum.
When you are able to ping the gateway, it is no longer an issue with the router.
Not necessary to downgrade and try the rest of the other things. You should focus on the computers. Notoriously, the Windows firewall blocks unknown source ICMP. You should check your firewall settings.
Some steps that share the fix on the firewall:
Or try the guide on the MS forum or the solution on disabling the firewall.
- Copy Link
- Report Inappropriate Content
Ok, so it looks like one of my USB-C to Ethernet adapters was literally messing with me... I have changed the adapter and now I am able to ping and access everything where I want from where I want. Sorry for bothering with no reason, this problem consumed all my weekend and it was because of a bad adapter.
@Clive_A thank you lots for your support!
- Copy Link
- Report Inappropriate Content

Thanks for posting in our business forum.
When you are able to ping the gateway, it is no longer an issue with the router.
Not necessary to downgrade and try the rest of the other things. You should focus on the computers. Notoriously, the Windows firewall blocks unknown source ICMP. You should check your firewall settings.
Some steps that share the fix on the firewall:
Or try the guide on the MS forum or the solution on disabling the firewall.
- Copy Link
- Report Inappropriate Content
Hello @Clive_A,
Thank you for your reply! I didn't taught about this.
Indeed when I am turning off the firewall on both Windows machines I am able to ping from 192.168.55.100 (Wired LAN) to 192.168.56.100 (Wireless LAN). But, when I am pinging from 192.168.56.100 (Wireless LAN) to 192.168.55.100 (Wired LAN) I am still receiving "Destination host unreachable".
Could you also help me with this?
Regards!
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
FairAssistance wrote
Hello @Clive_A,
Thank you for your reply! I didn't taught about this.
Indeed when I am turning off the firewall on both Windows machines I am able to ping from 192.168.55.100 (Wired LAN) to 192.168.56.100 (Wireless LAN). But, when I am pinging from 192.168.56.100 (Wireless LAN) to 192.168.55.100 (Wired LAN) I am still receiving "Destination host unreachable".
Could you also help me with this?
Regards!
Both computers need to allow the unknown ICMP to pass. Samewise to the rest of Windows PCs in the network if you need them to work like that.
- Copy Link
- Report Inappropriate Content
Clive_A wrote
Thanks for posting in our business forum.
FairAssistance wrote
Hello @Clive_A,
Thank you for your reply! I didn't taught about this.
Indeed when I am turning off the firewall on both Windows machines I am able to ping from 192.168.55.100 (Wired LAN) to 192.168.56.100 (Wireless LAN). But, when I am pinging from 192.168.56.100 (Wireless LAN) to 192.168.55.100 (Wired LAN) I am still receiving "Destination host unreachable".
Could you also help me with this?
Regards!
Both computers need to allow the unknown ICMP to pass. Samewise to the rest of Windows PCs in the network if you need them to work like that.
I have turned off Firewall on both Windows machines, but the one connected on the Wireless LAN it's still returning "Destination host unreachable" when pinging the one from the Wired LAN. Also, for test purposes I shared a folder on the Wired LAN machine and I's not accessible from the Wireless LAN machine.
- Copy Link
- Report Inappropriate Content
FairAssistance wrote
Clive_A wrote
Thanks for posting in our business forum.
FairAssistance wrote
Hello @Clive_A,
Thank you for your reply! I didn't taught about this.
Indeed when I am turning off the firewall on both Windows machines I am able to ping from 192.168.55.100 (Wired LAN) to 192.168.56.100 (Wireless LAN). But, when I am pinging from 192.168.56.100 (Wireless LAN) to 192.168.55.100 (Wired LAN) I am still receiving "Destination host unreachable".
Could you also help me with this?
Regards!
Both computers need to allow the unknown ICMP to pass. Samewise to the rest of Windows PCs in the network if you need them to work like that.
I have turned off Firewall on both Windows machines, but the one connected on the Wireless LAN it's still returning "Destination host unreachable" when pinging the one from the Wired LAN. Also, for test purposes I shared a folder on the Wired LAN machine and I's not accessible from the Wireless LAN machine.
I did some investigations using the Omada Network Tools. When I am trying to Ping the Windows device connected on Wired LAN from the Gateway I am receiving "Request timed out!". I have connected the Windows machine directly in one of the ER605 LAN ports and nothing changes. All gateway's LAN ports are configured to Wired LAN (Default) PVID.
I have also reset the configurations and left the default values, adopted only the gateway. Still not able to Ping from the Gateway the first device that is connected directly to it.
I have 2 Windows devices wired to the ER605 which has now the IP address 192.168.0.1/24. Both Windows devices have Firewall turned off.
Device 1 IP address: 192.168.0.100
Device 2 IP address: 192.168.0.101
When I am pinging from 192.168.0.100 to 192.168.0.101 it works. But, when I am pinging from 192.168.0.101 to 192.168.0.100 I receive "Destination host unreachable".
Everything else works perfect, internet connection ping to gateway 192.168.0.1 from both. Didn't changed anything on the default configuration.
The stranger thing is that when I am using the Omada Network tools to ping 192.168.0.101 from the gateway it works, but not for the other device with IP address: 192.168.0.100.
I have replaced the 2nd Windows device with a MacOS device which now hast the 192.168.0.102 IP address. Still not able to ping the 192.168.0.100 from the Mac OS device. I am receiving "Destination host unreachable". From the Omada Network tools I am able to ping the MacOS device.
- Copy Link
- Report Inappropriate Content
Ok, so it looks like one of my USB-C to Ethernet adapters was literally messing with me... I have changed the adapter and now I am able to ping and access everything where I want from where I want. Sorry for bothering with no reason, this problem consumed all my weekend and it was because of a bad adapter.
@Clive_A thank you lots for your support!
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 196
Replies: 6
Voters 0
No one has voted for it yet.