NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

jtvrls's avatar
jtvrls
Aspirant
Nov 25, 2020

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 the router on the local as the public IP.

 

The only 2 ports that are open are, port 80 (DMZ enabled) and 53.

So there's defenetly someting worg with the firmwire. I need a fast fix!

 

Current firmwire: NTG9X40CC_11.14.08.3

 

8 Replies

  • > The port forwarding functionality does NOT work on the Aircard 810s.

     

       Or, it doesn't work the way you expect.

     

    > I have enable port forwarding and added varouis port. [...]

     

       Not a very detailed description of anything.  What are your actual
    port-forwarding rules?  What are they supposed to do?

     

    > [...] But stiil all of the added port remains closed when i nmap to
    > the router on the local as the public IP.

     

       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.

     

    > The only 2 ports that are open are, port 80 (DMZ enabled) and 53.

     

       Those would be the router's management web site, and its DNS server,
    respectively.  Looks normal to me.


    > So there's defenetly someting worg with the firmwire. [...]

     

       Not really.

     

    > [...] I need a fast fix!

     

       _You_ might, but there's no evidence here that the router firmware
    does.

     

       What's the IP address of the router's WAN/Internet interface?  Have
    you tried testing that?

     

       For the usual problems with port forwarding, see:

     

          https://community.netgear.com/t5/x/x/m-p/1859106

     

    (That posting does not include talking to the wrong side of the router,
    but, if you have other problems, you might find it helpful.)

    • jtvrls's avatar
      jtvrls
      Aspirant

      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.

      • antinode's avatar
        antinode
        Guru

        > 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?