Omada Port Forwarding not working
Hello,
This week I upgraded my network with 1 ER605 Gateway and 3 Eap610's, and some switches.
Since I switched my old Archer C7 router to the ER605 my port forwarding is not working anymore.
My Setup:
ISP modem/Router(Docsis3.1) 192.168.0.1 with DMZ to 192.168.0.101(Wan ER605)
TP ER605 Gateway Wan: 192.168.0.101 Lan: 192.168.1.1
Omada Software controller running on my Synology Nas in docker 192.168.1.248
omada software 5.1.7
My port forwarding:
When I reset my ER605 and do the setup directly without the OSC my port forwarding is working. After Adopting the ER605 in the OSC I do a force Provision to get the settings from the ER605. But then my port forwarding is not working anymore?
The DMZ of my ISP modem is working, I checked this in 2 ways:
-When my PC is in the Wan network of the ER605 I can see that the ports are closed.
-When configured without OSC its ok
I turned of all the ALG function because I saw this in another post.
I really want to use Omada to have everything in the same interface? Did I forgot something in the OSC?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @Cedric-E
I just had the test on my end but I did not see the same issue.
Could you please send me a screenshot of your router Standalone(without OC200) mode Virtual Server settings? I want to have more test with your configuration.
Something you may test:
1. Enable DMZ on OC200, for Nas IP 192.168.1.248
This test can tell us if the problem is on the destination port;
2. Use HFS to make a simple test. Build the FTP server on a test PC and do port forwarding for this PC.
Then try access the PC server from WAN side.
This test can verify if port forwarding function is working properly.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Below you can find a screenshot of my virtual server settings direct in the ER605.
I already tried to do a dmz to my device on 192.168.1.246 but this doesn't work for me.
The second test I will try later, but I already did something similar without succes.
thanks a lot!
- Copy Link
- Report Inappropriate Content
Hi @Cedric-E
Other two things we may need to concern:
1. What is the WAN IP address of your Router in Standalone mode and Controller mode? Are they the same public IP?
2. With controller mode, please check if you can access 192.168.1.246 in local network. I suspect the NAS may not have correct IP/Gateway at this time.
- Copy Link
- Report Inappropriate Content
@Hank21 Sorry for the late answer. missed the notification mail.
in both standalone and controller mode the Wan Ip of my Er605 is 192.168.0.2 In the beginning this was 192.168.0.101 but I changed it to 192.168.0.2.
But changing the Wan ip doenst solve my problem.
In controller mode I can acces 192.168.1.246 without problems.
The ip of my NAS is 192.168.1.248.
In the setup of my omada docker install I was able to choose between bridge and host. But I don't understand the difference.
In host mode I wasn't able to acces the omada page. So I used bridge mode.
- Copy Link
- Report Inappropriate Content
Hi @Cedric-E
Cedric-E wrote
@Hank21 Sorry for the late answer. missed the notification mail.
in both standalone and controller mode the Wan Ip of my Er605 is 192.168.0.2 In the beginning this was 192.168.0.101 but I changed it to 192.168.0.2.
But changing the Wan ip doenst solve my problem.
In controller mode I can acces 192.168.1.246 without problems.
The ip of my NAS is 192.168.1.248.
In the setup of my omada docker install I was able to choose between bridge and host. But I don't understand the difference.
In host mode I wasn't able to acces the omada page. So I used bridge mode.
I believe your NAS is 192.168.1.246?
On your Modem Router, have you done DMZ for the IP 192.168.0.2?
I can't see "host" and "bridge" mode on the controller, could you please tell me where you set up this thing?
On Controller you can also do DMZ for the NAS, and on Modem Router's network(192.168.0.x) try access the NAS with IP 192.168.0.2
- Copy Link
- Report Inappropriate Content
I am having the exact same issue with Port Forwarding. I am running an email server with a Synology NAS & MailPlus which works fine through a combination ISP supplied modem/router.
I have upgrade my system to Omada and all works except with the inclusion of the ER605. It was the last component I added to the system which I had pre-configured using the rules that I had setup in the ISP's router. I pre-checked that the ports were working in a stand alone mode with the ISP supplied router set to bridge mode using my public static IP address.
I am fairly positive that when I inserted the ER605 into the system and the controller completed provisioning that the port forwarding rules became blocked.
My question really is, did you find a solution that worked with the OC200 and ER605. Is it a matter of setting up in a particular order which I am beginning to think may be the next action I need to take.
I find it hard to believe that there isn't more information considering this is a business solution and many would be running email servers. I will try more things out but I already know that I have lost quite a few emails because ports aren't opened so hence looking firstly for definitive solutions and hoping you have one
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 4232
Replies: 9
Voters 0
No one has voted for it yet.