@Clive_A 

Uploaded this at 2 remote sites... that had 2.1.4, 2.2.2, and now on 2.1.5.

Everything seems to be work... so far!

  @ceejaybassist 

@SingletrackMind 

https://community.tp-link.com/en/business/forum/topic/634552

Clive commented on this beta dropped in that above thread. 

Hello,

I´m wondering too, what´s about ER605v2 2.2.2 and after that 2.1.5 version-difference .... but .....

Was not able to get Switch ACLs working over stateful Gateway ACL with blocking InterVlan-routing in 2.2.2 (worked on it whole day yesterday with 2.2.2). ... with 2.1.5 it works like a charm included mDNS for homekit unidirectional over VLANs.

Never had this all working as I expected and wanted before -> for this big thumb up for TP-Link ... TP-Link: that´s the right way !

Only difference between 2.2.2 and 2.1.5 i saw is in bugfixing point 15 to 19 for 2.1.5.

Greetings

yavin

EDIT after flashing 2.1.5: After reboot i was able to connect oc200 auto-backup location with Switch ACL over Gateway ACL (SFTP to Syno unidirectional). After random time last minutes ago i had no more connection over SFTP.

In my opinion there was a need for stateful ACL Gateway settings for unidirectional VLAN access.

Every other settings are working as expected mDNS included !

Hi @caramb 

Thanks for posting in our business forum.

caramb wrote

  @Clive_A 

 

FYI,

 

I was running firmware 2.1.4 Beta on R605v2 and it was merely ok.

 

Just gave a try today and upgraded to 2.2.2.

My experience is this one (2.2.2) is broken ; r605v2 was stuck in an adopt-provisionning-configuring-connected-heartbeat-missed infinite loop.

 

From what I saw in the "application result" beta tab, even if the r605 was marked as "connected", configuration was still in progress (deploying on all items except those unsupported). About 1 minute after transitionning to the "connected" state, it changed to "heartbeat missed" ; connectivity was broken (the gateway was not routing anymore) before configuration finished.

A few seconds after, it swtched to adopt and the others states.

After 1 hour of uptime, it was still looping.

First, a beta feature does not represent it is stable enough for production. If you have trouble with the beta feature, please report it to the SDN Controller section where Hank will take care of that.

But if the device has not made the configuration, your network is not going to work properly. This is expected behavior.

I am not sure what you have on your devices which causing the loop. There are many people upgrading to the V2.2.2 and they did not report this. Or I will see tons of similar threads recently.

So, if you'd like to work with me on this "looping" part, share your detailed configuration before the upgrade in a new thread. I'll follow it up.

caramb wrote

  @Clive_A 

 

I had quite "hard" time to recover from this as the gateway was unresponsive to manual commands ; you cannot do anything unless it is in connected state. During the short period it reached this state, I tried to force a reboot but command failed, I tried to downgraded, but it also failed.

 

At the end, I had to factory reset the gateway, connect directly, downgrade the firmware, inject minimal configuration so it is able to reach my local instance of Omada...

You can stop this by disconnecting the wire connection and resetting the device which is what you did. Right.

caramb wrote

 

BTW, do not enable the new "remember the device" feature in Omada ; it is also broken. It assumes the device comes with the Omada site provisionned admin password ; which is likely not the case after factory reset (unless you know this beforehand). In regular adoption mode (remember feature disabled), Omada will try a few times to adopt with the site credentials. In cas of failure, it will allow you to input the device specific credentials so it can overwrite the whole thing.

When "remember" feature is enabled, it just tries to adopt with the site crendentials... indefinitely...

In a few minutes, I was having hundreds of "adoption failed" log messages.

 

 This is a new feature to avoid any people resetting the device by accident. So the controller can readopt it without touching it.

You feel it broken because you did not pay attention to the Help Center with explanation.

The beta release note has also explained what that is.

Also note that V2.2.2 and V2.1.5 beta are both adapted to the V5.11. I am not saying it does not on other versions but it may have some trouble on some features. And is expected.

Hi @jpearn 

Thanks for posting in our business forum.

jpearn wrote

  @Clive_A Could you please clear up the versioning issue as 2.2.2 vs 2.1.5 beta doesn't make sense. Which is the base and what comes after 2.1.5 beta ? Which branch is being worked on, 2.2.2 going forwards ?

If you could post a branch / version table that would be helpful, thanks.

2.2.2 is a special version made for other purposes. It is not pushed via the cloud. 2.1.5 is based on 2.2.2 and added several fixes. The final build version may rely on the dev's decision.

You can upgrade from 2.2.2 to 2.1.5 beta freely and safely.