ER605 V1 with Omada doest not work properly with Linux/HUAWEI Router
Hi, I have ER605 V2 and V1 routers.
Four of them configured with Omada 5.13.30.4
The ER605 V2 works normally.
The ER605 V1 takes more time and little work but works.
The problem is.
If I create a second LAN, let's say 11.11.0.1/24 and attach it to the port number 3 for example.
If I plug a computer running LINUX it does not works. Windows works normally.
The LINUX computer get the ip by DHCP normally, but I can't ping to my gateway '11.11.0.1' (in our example) or ping to the internet.
If I use the main LAN (that one that we cannot change), it works normally (even If I change the IP of this LAN).
So the problem with LINUX is when I set another LAN to the port it is connected to.
I reproduze the same configuration in ER605 V2, everything works ok.
Works with LINUX normally.
And I didn't change anything, is the same configuration.
Somebody could help?
Add: Downgrade the controller is not a option.
Add2: The HUAWEI Wifi AX2 Router has the same problem. (the router is upgraded, with ER605 V1 Omada it didnt' works).
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
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?
- Copy Link
- Report Inappropriate Content
@Clive_A Hi, Thanks for your quick answer.
First of all, this behavior only happens with Omada.
The ER605V1 and V2 routers works normally with the WEB interface, without Omada.
Second (and I cannot be 100% sure about this anymore)
Either ER605V1 and V2 had this same problem with Omada in the past.
(But don't remember If its true, neither the firmware or Omada versions used).
Now, with the lastest versions of firmware and Omada on both routers, only V1 has this issue.
The V2 works as expected.
The V1 with Omada always had this problem and continue to.
Both routers without Omada works normally.
- Copy Link
- Report Inappropriate Content
Hi @drigo
Thanks for posting in our business forum.
drigo wrote
@Clive_A Hi, Thanks for your quick answer.
First of all, this behavior only happens with Omada.
The ER605V1 and V2 routers works normally with the WEB interface, without Omada.
Second (and I cannot be 100% sure about this anymore)
Either ER605V1 and V2 had this same problem with Omada in the past.(But don't remember If its true, neither the firmware or Omada versions used).
Now, with the lastest versions of firmware and Omada on both routers, only V1 has this issue.
The V2 works as expected.The V1 with Omada always had this problem and continue to.
Both routers without Omada works normally.
No. V2 does NOT work properly.
Something you wrote is NOT accurate. I tested it today and I found out it was the same behavior. I expect you to be accurate in your description but it isn't.
This is a universal system for the VLAN interface as I discussed with the dev. That was what I thought earlier. So, if you are telling me this works for V2, I suspect whether you did the same setup on the V2.
It is still the reason that has been explained previously. It is not a problem with the router function. It is because the port is tagged so that Linux cannot process it. VLAN function and the whole system are intact.
- Copy Link
- Report Inappropriate Content
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.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1678
Replies: 24
Voters 0
No one has voted for it yet.