NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Port forwarding aircard 810s not working
Hi there, The port forwarding functionality does NOT work on the Aircard 810s. I have enable port forwarding and added varouis port. But stiil all of the added port remains closed when i nmap to...
You might get more help, and find earlier questions and answers about your hardware, in the appropriate section for your device. That's probably here:
Mobile Routers, Hotspots & Modems
Ok here a screenshot of my ports i want forward:
And to my basic understanding, when this is set i should see that the port is open when i namp to the router via the local as public ip. But localy i get that the port is filterd and publicy i get that de port is closed.
> Ok here a screenshot of my ports i want forward:
I can't (yet) see your picture. In-line images must be approved by
a moderator before others can see them. The time required varies.
Attachments have no such limitation. Of course, attachments have their
own one-per-message limitation.> And to my basic understanding, when this is set i should see that the
> port is open when i namp to the router via the local as public ip.I don't understand "via the local as public ip". An IP address can
be local/private or external/public. They're different. An actual
address might be more helpful than your description of an actual
address.> The router's LAN IP address is different from its WAN/Internet IP
> address. I would not expect port forwarding to be effective when you
> specify the router's LAN IP address.Still true. Port forwarding couldn't possibly work from the router's
LAN IP address. If it did, and you configured port forwarding for a web
server on port 80, then you could never again reach the router's
management web server (at the router's LAN IP address and port 80).
> [...] But localy i get that the port is filterd and publicy i get that
> de port is closed.I don't know what that means, either. "get" _how_?
None of that is a useful problem description. It does not say what
you did. It does not say what happened when you did it. As usual,
showing actual actions (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.> https://community.netgear.com/t5/x/x/m-p/1859106
Did you run any of those tests? Or think about what it said?
Ok I added ports like, 22, 443 and 5900 that point to a specific IP. Then I did a scan with nmap to see if the ports are really open. Like: nmap -p 22,433,5900 192.168.1.1 Via the private and public IP you will receive a message that thee port state is closed or filtered.
With every other router I've ever done this, I could immediately see that the port was open. So what am I doing wrong or what should be on or off to get this working.
