Hi @MyDecoAtHome 

Thanks for posting in our business forum.

It should not happen if you follow the guide and set up the VLAN interface.

First, traffic between the VLAN interfaces is not blocked. Unless you have set up any kind of ACL.

From a regular computer, you should be able to ping the other VLAN interface's gateway IP.

You also should check what that IP is.

As you wrote:

MyDecoAtHome wrote

But I can't get a ping through from e.g. 192.168.2.100 -> 192.168.178.1 (which is a device on the 192.168.178.0 Network). Also accessing the devices via http does not work.

It is a device. So, you should also check its firewall.

There is nothing wrong with the router based on your previous paragraph on ping.

Hi @MyDecoAtHome 

Thanks for posting in our business forum.

MyDecoAtHome wrote

  @Clive_A 

 

Hi Clive_A,

 

thanks for your quick reply. 

 

When I'm connected to the 192.168.178.0 network (e.g. plug in my PC to the unmanaged switch connected to the er605) I can access the 192.168.178.1's Web interface ok. This is also a router (Fritzbox) and it does not have any firewall set up. It has been factory rest to eliminate blocking reasons.

Therefor I think the traffic from LAN1 (192.168.1.0) the LAN2 (192.168.178.0) is block in some way on the er605. 

Actually I don't know why.

I have not set up any blocking ACL.

 

Any further Ideas? 

 

Thanks and kind regards 

C.

If you can sort yourself out, LAN1 192.168.1.0?

You probably should draw a diagram now as you already get yourself confused.

That's WAN on the Omada router. And you name 192.168.2.0 as LAN1.

There is nothing wrong with this if you tell me 1.0 cannot access 178.0. That's NAT issue. Not VLAN or routing issue.