ER605 Port Forwarding with multiple WAN IP address
Hello,
I am using multiple (static) WAN IP addresses using the "WAN IP alias" option. This is working great and as expected and I can access the router via either IP.
I want to be able to port forward (say port 443) to both the WAN IP AND the WAN IP Alias - this would require two entries for the same external port. However, the router complains that I cannot duplicate the external port. Believe, this may be a restriction that should not apply when there are multiple WAN IPs. Should I be able to have the same port repeated for each WAN IP? Each IP at said port 443 will have a different forwarding IP (or technically could be the same too).
Lastly, the WAN IP box/dropdown only shows the Alias IP - am I to assume if I don't specify the alias IP then then this defaults to the default IP?
Any help is appreciated.
Thanks
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @snathan
Thanks for posting in our business forum.
See the current solution: Port Forwarding Issues with WAN Alias - Same Port Not Allowed
- Copy Link
- Report Inappropriate Content
Hi @snathan
Thanks for posting in our business forum.
See the current solution: Port Forwarding Issues with WAN Alias - Same Port Not Allowed
- Copy Link
- Report Inappropriate Content
Hello @Clive_A
The links / solution you pointed to seem to indicate this will be fixed in the upcoming software release of the Omada Controller. However, I don't use the Omada Controller and rely on the web administration on the router itself. Is there a release candidate for resolving this in the ER605 v2 firmware itself?
Thanks
- Copy Link
- Report Inappropriate Content
Hi @snathan
Thanks for posting in our business forum.
snathan wrote
Hello @Clive_A
The links / solution you pointed to seem to indicate this will be fixed in the upcoming software release of the Omada Controller. However, I don't use the Omada Controller and rely on the web administration on the router itself. Is there a release candidate for resolving this in the ER605 v2 firmware itself?
Thanks
I don't understand what you mean. The official fix is gonna be placed in one of the firmware adapting to V5.15.X.Y.
That was a firmware to address the issue based on the latest firmware.
That's not an RC but good enough for the issue now.
RC will be posted as a Pre-Release on the forum. Not gonna provide individually to users.
- Copy Link
- Report Inappropriate Content
Hello again @Clive_A
When I go to Download page (https://support.omadanetworks.com/us/product/er605/v2/) I see that the latest software version for Omada Controller is v5.15.8.2. The software release for the ER605 v2 firmware is ER605(UN)_V2_2.2.6 Build 20240718. I am understanding this will be fixed under the Omada controller software release given the release numbering the solution post is providing is in the 5.15 range. I am looking to see if this will be fixed under the ER605 firmware release which will have a release number of v2.x possibly.
Thanks
- Copy Link
- Report Inappropriate Content
Hi @snathan
snathan wrote
Hello again @Clive_A
When I go to Download page (https://support.omadanetworks.com/us/product/er605/v2/) I see that the latest software version for Omada Controller is v5.15.8.2. The software release for the ER605 v2 firmware is ER605(UN)_V2_2.2.6 Build 20240718. I am understanding this will be fixed under the Omada controller software release given the release numbering the solution post is providing is in the 5.15 range. I am looking to see if this will be fixed under the ER605 firmware release which will have a release number of v2.x possibly.
Thanks
If that's what you think, so be it.
I think this is pretty clear and explained in both the solution post and here. Adapting is the keyword in our conversation. I don't know if I understand the same concept as you do but I think it is explained. Again, this is a period of time, not a specific timeline guaranteed.
It's not what you think. It is the firmware with the router, not the controller. You cannot find any release note regarding this, how could it be fixed so far? Or should be fixed by a simple controller upgrade?
Since last year, we don't provide a specific version or timeline. No guarantee of the firmware compilation or release schedule. See the release on the forum or the official. It is what you have.
Also the new controller version has a dynamic version which you find no clues or pattern. Just the major and minor versions got a pattern.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A
Think I understand that although not specifically called out, the upgrade will be both in the Omada controller software AND the Firmware.
Thanks for the explanation.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 95
Replies: 6
Voters 0
No one has voted for it yet.