NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6250 does not persist ddns
A free ddns account has been created at NoIP, port forwarding configured at the router and the NoIP account credentials and dns name entered in Advanced Setup, Dynamin DNS. The firewall has been configured to allow port 80 traffic. With this setup it is possible to connect to the dns name. However, the window for making a connection is short lived - less than 5 minutes.
Refreshing NoIP has no effect. Their port check tool shows the port is not open. Only after clicking on Apply at the router's Dynamin DNS screen will the port open. I suspect that the port remains open only until my router login times out.
How to keep the port open?
Doumo arigatou gozaimasu
Especially for all of your valuable time. I believe the issue is just now resolved. The problem was using my wireless adapter as a bridge to a virtual machine. It took me a couple of days to think of stringing a long cable to the router to see what might happen. When I looked at adapter properties I saw that the wireless was offline. No wonder the port was down. Lesson learned. Hardwire from now on.
18 Replies
What is the value of the router's NoIP Advanced Setup, Dynamin DNS setup? By turning it off the port appears to remain open! I could find no mention of that screen in the online manual. But I figured it was required. Looks like not.
geoBrooks wrote:A free ddns account has been created at NoIP, port forwarding configured at the router and the NoIP account credentials and dns name entered in Advanced Setup, Dynamin DNS.
Not convinced the port 80/TCP can be used for port forwarding - even if 80/TCP might be available - the Netgear router design migth have some shortcomings. Your observations with the admin access seems to confirm.
geoBrooks wrote:The firewall has been configured to allow port 80 traffic.
Where/how do you have access to firewall rules for WAN/Internet->LAN/port-forwarding? There is no such thing on the Netgear conumer routers. Only a service blocking is available - to restrict LAN->WAN/Internet services. Silly but true.
I assume that offering to forward incoming port 80 means that the router is capable of doing such. After all, it has demonstrated that it can. So I'd like to know why you are not convinced it can be used that way.
What I did not describe was that the IP address to which traffic is forwarded is a bridge to a virtual machine. That's the reason for mentioning the firewall - it's conceivable that it could block traffic to the VM. Altho' my test of that was that adding the rule made no difference in performance.
It remains unclear whether the router or No-IP is causing the time out. It is clear to me, at least, that clicking on the apply button does enable traffic to pass if just prior to the click the connection times out.
Because I know that other more advanced router models (like the R9000) block 443/TCP for port forwarding as long as it's in use for the LAN side management - even if a different https port is active on the WAN/Internet. And yes, 443/TCP is offered for port forwarding, too. Even UPnP PMP requests appear to be handled, kind of.
So confirm the firewall you talk of is part of the VM platform or of the VM - but not on the R6250?
geoBrooks wrote:It remains unclear whether the router or No-IP is causing the time out. It is clear to me, at least, that clicking on the apply button does enable traffic to pass if just prior to the click the connection times out.
It's not No-IP ... the DDNS service will keep the name-to-IPv4 certainly longer than five minutes.
Beyond what you experience - that's the fishy part I have in mind. Test with a different, non-stanard port, e.g. 81/TCP to compare.
