Hi @drigo 

Thanks for posting in our business forum.

drigo wrote

  @Clive_A Hi, its been about 3 months I opened this thread.
No fix so far.

As I said, this router bornt broken.
It never worked as was to be.

Say that it is in EOL state is not valid.

 

So, lucky that I am not busy today. I spent 3 hours today with the dev and cooperated with her (one of the devs) on this issue.

Preliminarily, we conclude it is an issue with the VLAN from the router being tagged and the Linux failing to receive this. As long as you add a new VLAN interface on the controller, it will be tagged by default.

As it is tagged, Linux does not process it and fails to create the correct ARP as well.

But the dev questioned that if this happens to V1, it should happen to V2 as well. Well, in your very first post, you mentioned that this is not reproduced on your ER605 V2.

As this is the design and expected behavior.

I gotta confirm this again, you have to answer this part as we move along with the dev.

If you add a new VLAN interface to the ER605 V2 from the Omada Controller and set the PVID to the port, the Linux gets the frames/packets well and gets Internet? Without any problems. No issues with the ping to GW or Internet at all?

Hi @drigo

It is a problem with the Omada Controller which fails to correctly set the port as untagged when PVID is set.

Dev shared the info that ETA V5.15 will optimize this. You can pay attention to the firmware release in the future.

As a reminder, we are not able to give a specific date for a beta or official firmware release. Nor can we guarantee an ETA for the firmware. We recommend you subscribe for the Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates.