NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
By not providing dynamic DNS support, which is a standard feature for ALL other routers/brands these days, you are greatly reducing your target audience and market share this device will appeal to. I'd like to submit feature request to your engineering/product management to add dynamic DNS support to Nighthawk M2 MR2100.
A lot of people would love to use this device as a stationary, not mobile, home router and the fact it supports battery-less mode proves that Netgear supports that use case as well. However, ALL modern routers support dynamic DNS, because being able to connect to your home network remotely is an essential requirement for any router, which is meant to serve as the main gateway to your household.
Also, Nighthawk M2 is not on the dropdown list of devices for this forum, for which users can submit ideas - please add it.
13 Comments
- To be honest there are workarounds for this that make it less than critical as a missing feature. Simple one would be to run a ddns client on the machine you are wishing to connect to from outside you network. You could also fire up a cheap raspberrypi running pihole and a ddns client on your LAN for a low powered solution to the problem. In the stationary use case there are simply other options than having this baked into the modem/router.
There are no workarounds for dynamic DNS here, let alone "simple" ones. The fact, that you suggest running ddns client on a machine internal to a network, that uses mobile carrier as an ISP, unmistakably indicates you dont understand how carrier networks set up and how they work. Carriers have they own DNS servers, and their own NAT for ALL devices, provisioned on their network. Running ddns client on such computer, which gets internet from Nighthawk, and therefore is already behind carrier NAT, creates double NAT setup, and such ddns clients do not work. It is a known fact - Google it and educate yourself. I'm also speaking from experience of trying to set this up, not just theoretical knowledge.
I also don't own a raspberrypi and buying additional, possibly expensive hardware, and spending time on learning to use it, while knowing it will almost certainly not work due to the same double NAT considerations, sounds like a VERY lousy and questionable workaround to Netgear, simply adding dynamic DNS support to their Nighthawk. As discussed - it has been a standard out of the box feature on 99.9% of routers, released in the past 5 years or even longer.
In the "stationary use case" as you refer to it, there are simply NO options/workarounds to adding dynamic DNS support.
Prey tell what magic will the client on the Nighthawk do to get you a routable return address exposed via ddns if your carrier won't expose you anyways.
You think the Netgear boys and girls aren't using anything other than ddclient integration...?
Please go argue somewhere else. I'm not here for your petty bickering about things we've established you don't understand. Do not hijack this thread for that. I'm here to let Netgear product managers for Nighthawk know they have left out a very important feature, all other routers have, which hinders usability of the product, and reduces attractiveness of the device to prospective customers. They need to fix this.
- It is not an argument at all. I genuinely don't understand what you are looking for in DDNS whilst at the same time accepting you are sitting behind CG-NAT. You either expose the 10.x.x.x address you are assigned to have which we know isn't usable. Or the CG-NAT address which you can't route via anyways. In order to solve this for my own setup, I could either pay more for a routable ISP-provided address (now not offered unless I convert to a business account) OR set up an external IP and a VPN. I took the latter option with a wireguard setup and an Amazon lightsail instance using algo, I can now publish services via this VPN tunnel. There simply was no other way around it. Whatever Netgear do for DDNS won't solve a CG-NAT issue UNLESS they also provided a MITM type service to route you back in that runs on the M1/2 and their external infra. The way chrome remote access and others get around CG-NAT.
- Just to add in a positive way, this is a super quick and simple way to expose services from behind CG-NAT https://ngrok.com/ You can spin up a trial account for free. You can expose almost anything.
Just to add in a positive way - PLEASE go away, and take your incorrect, misleading assumptions about mobile carrier's NAT and your unwelcome, not applicable suggestions with you. I've replied to you in the other thread, where you're also hounding me, more extensively, to make it absolutely clear where I stand on the need for your input. If this request to leave me and my threads alone also gets ignored - I'll be reaching out to Netgear forum admins to have your stalker profile removed from these forums...in a positive way!
- I am pretty sure the admins think the same of you that I and anybody else reading your threads does. It is clear you have ZERO idea what you are asking for. A DDNS client will NOT help you in the slightest if you are behind CG-NAT. ZERO ZERO ZERO. Good luck getting precisely nowhere with your request. Your inability to hold a civil thread is apparent in your posts.
- https://community.netgear.com/t5/Mobile-Routers-Hotspots-Modems/Nighthawk-M2-MR2100-features-and-availability/m-p/1747973/highlight/true#M9343 You literally haven't responded once at a technical level. You just keep insulting me and calling me a troll. See the link above for MORE discussion on the topic of bypassing CG-NAT. It does not involve DDNS solely. Rather proxies and / or VPNs. Why are you so offended, and ultimately offensive, because someone is disagreeing with you. Yet you won't provide a technical counter argument. Just post the solution to bypassing CG-NAT solely with DDNS you keep alluding to.