Hi  @weby112 

What's the previous version of the controller before this update?

To better understand the situation, please share with us the following info:

1. A screenshot of the controller's device list so we could know the products and their firmware you are using;

2. A screenshot of the VLAN settings;

3. A screenshot of the ACL settings;

4. More details about the situation, for example, when failed to access, you are trying access from which VLAN to which VLAN? what's the IP addresses of the involved clients? 

Hi  @Vincent-TP 

I have deleted all ACL rules and only created the one with the PV VLAN again with the same settings as before, but with the same result.

The screenshots of the settings are attached.

I am with my PC in the default VLAN (1) with the IP 10.0.0.97 and try to access the PV VLAN (22), the device has the IP 10.0.22.10 (photovoltaic inverter), the device is not accessible. However, as soon as I switch to VLAN 22 (10.0.22.11) with my PC, I can also reach the device with the IP 10.0.22.10, but I can no longer access the devices that are in the default network until I change the network back again.

Hi  @weby112 

Different VLAN Interfaces can communicate with each other by defualt. We don't need to configure extra ACL rules to achieve this.

Do you happen to configure any Gateway ACL to block it? 

Please delete all the ACL rules and test again.

 hi @Vincent-TP 

I already tried this before I redefined the ACL.
However, the problem persisted, which is why I also defined the ACL rule, as the communication was still not working.

hi  @Vincent-TP 

I have tried to delet the ACL Rouls, but the communiction will not work.

The other device is not reachable.

Hi  @weby112 

Thanks for the reply. This must be a config reason. 

To figure out which part is the reason, we need the config file of the controller to check all the configs.

I had created a support email for you to send the file, and the ID is TKID250747267.

If this is a concern for you, you may factory reset the controller and re-configure VLAN settings, see if the situation persists.

Note: before factory reset, make sure to backup the config file.

  @weby112 

One more question, do you remember the previous version of the controller before this update?

Hi  @Vincent-TP 

I have the Support File sendet to the support per Mail.

Sory, i dont know how was the previously version. 

I belive it was the Version 5.15.8.2

 Hi @Vincent-TP 

Since I run the controller in a Proxmox container and create a snapshot before every update, I have now gone back two versions (from 5.15.24.18 to 5.15.20.20) and am now on version 5.15.6.2, where it clearly worked before but no longer does.

In the meantime, the firmware of the ER605 has also been updated. Could this be the cause?

The ER605 had once received custom firmware from support due to an error.