Reply

Can't ping Netgear R6300v2 router locally or with public IP

haydendavenport
Aspirant

Can't ping Netgear R6300v2 router locally or with public IP

I'm attempting to forward a port, but it doesn't seem to be working. I've opened the port via the Netgear Genie, tested it on multiple sites to see if the port is open (all have said it is closed), and I've tried running a test python http.server and going to the address. Nothing has worked

 

Eventually, I tried pinging my router locally and via the public IP. Neither worked, even after I checked "Respond to Ping on Internet Port". Then I had a tech savvy friend attempt to ping it, and he was also unable

Any thoughts on what the problem could be?

 

I'm attempting to forward a port on a Raspberry Pi, and have verified that I have the correct local IP for it in the Netgear settings, for whatever that's worth

 

Firmware Version V1.0.4.42_10.0.93 (Latest)

Thanks!

Model: R6300v2|AC1750 Dual Band Gigabit router
Message 1 of 8
antinode
Guru

Re: Can't ping Netgear R6300v2 router locally or with public IP

> I'm attempting to forward a port, [...]

 

   Why?  Which?  How, exactly?

 

> [...] but it doesn't seem to be working.

 

   "not working" is not 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.

 

> [...] I've opened the port via the Netgear Genie, [...]

 

   What, exactly, does "opened the port" mean to you?  Which "the
Netgear Genie"?  Ever helpful, Netgear uses the name "Genie" for more
than one thing.  Netgear routers have a web-browser interface called
"Genie", and Netgear offers application programs for various
computers/tablets/phones, which are also called "Genie".


   Who's listening at this (unspecified) "port"?

 

> [...] I tried pinging my router locally and via the public IP. [...]

 

   You "tried" what, exactly, from where, exactly, with what result,
exactly?  Copy+paste is your friend.

 

   Note that "ping" (ICMP) is unrelated to port forwarding (TCP/UDP).

 

> I'm attempting to forward a port on a Raspberry Pi, [...]

 

   Which "a port"?  Why?  _To_ "a Raspberry Pi"?  To _what_ "on a
Raspberry Pi"?  (Running Raspbian?)

 

> [...] and have verified that I have the correct local IP for it in the
> Netgear settings, for whatever that's worth


   It's not worth much.  It's nice that you're happy with whatever that
means to you, but, again, I can't see what you did, or what "the correct
local IP [address] means to you.  There's no reason to hide any
local/private addresses.

 

> Any thoughts on what the problem could be?

 

   For the usual problems with this stuff, see:

 

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

Message 2 of 8
haydendavenport
Aspirant

Re: Can't ping Netgear R6300v2 router locally or with public IP

Thank you @antinode for your thorough response and investigation for better details ^_^

I am attempting to forward port 65483 on my raspberry pi running Raspbian (local address of the pi is 192.168.1.51) via the netgear genie. I can establish a remote desktop connection on the local network from another computer to the Raspberry Pi at this address, which suggests this is the correct address

I am accessing the netgear genie at http://192.168.1.1/start.htm, and these are my port forwarding settings (via Advanced > Advanced Settings > Port Forwarding / Port Triggering):

owncloud65483443192.168.1.51

 

The purpose of this is to create an owncloud server that I can access anywhere. However, the port is shown to be closed when I check it at http://ismyportopen.com/

as well as

https://canyouseeme.org/

(It reports that the Connection Timed Out)


When I set up a test page via python on the Raspberry Pi (python3 -m http.server 65483) I can get the webpage to show up at 192.168.1.51:65483, however, I cannot access it using my public address (censored here): ###.###.###.###:65483 when testing from my own computer, or my phone with wifi disabled (using cellular service only)

when I attempt to ping my public ip (which I get by googling "what is my ip") via cmd: ping ###.###.###.###, the request times out with no packets received (IP Address censored):

Pinging ###.###.###.### with 32 bytes of data
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for ###.###.###.###:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Message 3 of 8
antinode
Guru

Re: Can't ping Netgear R6300v2 router locally or with public IP

> I am attempting to forward port 65483 on my raspberry pi [...]

 

   As I read your port-forwarding rule, you're forwarding external port
65483 to port 443 on the R-Pi.  Port 443 would normally be used for a
(secure) web server.  Is that what you're trying to do, or did you
choose port 443 in order to cause (or reveal) confusion, or what?

 

> When I set up a test page via python on the Raspberry Pi (python3 -m
> http.server 65483) I can get the webpage to show up at
> 192.168.1.51:65483, [...]

 

   Ok.

 

> [...] however, I cannot access it using my public address (censored
> here): ###.###.###.###:65483 [...]

 

   Of course not.  Your port-forwarding rule forwards external port
65483 to port 443 on the R-Pi, and your test server (on the R-Pi) is
listening at port 65483, not at port 443.  If nothing on the R-Pi is
listening at port 443, then "<your_public_IP_address>:65483" won't work
(with that port-forwarding rule).


   You're welcome to hide your public IP address, but it might help if
you verified that the WAN/Internet address of the router is the same as
that public IP address.  And, if you're worried about revealing secrets,
then the top half, "a.b" out of "a.b.c.d", would satisfy my curiosity
regarding its validity as a public address.

 

   Again, a clear description of the actual problem which you are trying
to solve might be more helpful than all the details of irrelevant tests.

 

> when I attempt to ping my public ip [...]

 

   From where?  A system on your LAN?  A system in the outside world?

 

   Again, is this "###.###.###.###" the same as the previous
"###.###.###.###"?

 

>    Note that "ping" (ICMP) is unrelated to port forwarding (TCP/UDP).

 

   Still true.  And it's possible that your (unspecified) ISP could
block "ping" (ICMP), even if your router is willing to respond to it.

Message 4 of 8
haydendavenport
Aspirant

Re: Can't ping Netgear R6300v2 router locally or with public IP

Thanks a ton for your thorough response and patience as I try to explain the issue, @antinode ^_^

 

> Port 443 would normally be used for a (secure) web server. Is that what you're trying to do

In a nutshell, yes. I am trying to set up my Raspberry Pi with an OwnCloud server so that I can upload/download files remotely

 

> If nothing on the R-Pi is
> listening at port 443, then "<your_public_IP_address>:65483" won't work
> (with that port-forwarding rule).

 

Ah, I see

To hopefully explain more about the situation, I have the OwnCloud set up such that, if I type https://192.168.1.51:443 into another computer (in a browser on a machine that isn't the Raspberry Pi) on the same LAN, it brings up the OwnCloud webpage that I expect to see

> "a.b" out of "a.b.c.d", would satisfy my curiosity regarding its validity as a public address


Sure: 208.104.###.###

>> when I attempt to ping my public ip [...]

> From where? A system on your LAN? A system in the outside world?

I have tried on a system on my LAN, and from a phone connected only to cellular service, and had a friend in a different state try as well

> Again, is this "###.###.###.###" the same as the previous "###.###.###.###"?

Yes -- 208.104.###.###

> Note that "ping" (ICMP) is unrelated to port forwarding (TCP/UDP).

 

Ah ok, I did not realize what you meant initially. Does this mean that you can successfully port forward even if your IP is not ping-able?

---

Hopefully that helped clarify the issue further. Thank you again for the help!

Message 5 of 8
antinode
Guru

Re: Can't ping Netgear R6300v2 router locally or with public IP

> [...] if I type https://192.168.1.51:443 [...]

 

   With "https://" the browser/client should default to using port 443,
so you shouldn't need to specify it (":443") explicitly.

 

> Sure: 208.104.###.###

 

> Yes -- 208.104.###.###

 

   Ok.  Then the port-forwarding rule might be your only problem.

 

   Interestingly, on my D7000[v1] (V1.0.1.78_1.0.1, currently), with
"Respond to Ping on Internet Port" checked, I can "ping" my router at
its WAN/Internet address from my LAN.  No bets on whether that's
intentional.

 

> [...] Does this mean that you can successfully port forward even if
> your IP [address] is not ping-able?

 

   Yup.  Different protocols.


   As suggested in that "usual problems" posting, if it works using:

 

      https://<server_LAN_IP_address>

 

then, if the router's "NAT loopback" feature is working, it should also
work from your LAN using:

 

      https://<router_WAN/Internet_IP_address:<p-f_rule_ext_port>

 

With your port-forwarding rule, that'd be:

 

      https://208.104.###.###:65483

 

And, because the router's WAN/Internet address is your public address,
that URL should also work from the outside world.

 

   With the non-default (external) port number, you would need to
specify it explicitly when using that external/public address.


   Having to specify that ":65483" might be annoying, but unless you
really want everyone on the Intenet to be trying to access your server
(frequently), using a non-default (external) port number is probably a
good idea.

Message 6 of 8
haydendavenport
Aspirant

Re: Can't ping Netgear R6300v2 router locally or with public IP

a

Thanks again, @antinode for your patience and persistence with helping me with this issue!

> With "https://" the browser/client should default to using port 443, so you shouldn't need to specify it (":443") explicitly.

 

Ah, interesting! https://192.168.1.51 does indeed work as well!

 

> if the router's "NAT loopback" feature is working, it should also work from your LAN using:

> https://<router_WAN/Internet_IP_address:<p-f_rule_ext_port>

 

Unfortunately, https://208.104.###.###:65483 (substituting the #s for the correct digits coorresponding to my public IP, of course) does not work on the LAN, including on the Raspberry Pi itself

 

I don't mind specifying that extra :65483 for the added security, of course. But it appears that for some reason, the port is still not open. And of course, my port forwarding rule is still as it was above:

owncloud65483443192.168.1.51

 

Any idea what I can try next?

 

Thanks again for all of the assistance!

Message 7 of 8
antinode
Guru

Re: Can't ping Netgear R6300v2 router locally or with public IP

> [...] https://192.168.1.51 does indeed work as well!

 

   Ok.  (What could go wrong?)

 

> Unfortunately, https://208.104.###.###:65483 (substituting the #s for
> the correct digits coorresponding to my public IP, of course) does not
> work on the LAN, [...]

 

   That's bad news.  Does it work any better from an outside-world
client?  What's the actual error message?

 

   I don't have a good explanation for that.  If you can access the
server at its LAN address, then the server is working.  If, in your
external-like URL, you're specifying the right external address (the
router's WAN/Internet address) and the external port number from the
port-forwarding rule, then the router should let it work.  At-straw
grasping follows...


   You might try loading an older firmware version, to see if Netgear
has introduced some new bug.  I seem to recall reading some complaints
here about problems on some model/firmware with port 443, specifically,
possibly related to Remote Management (which should be configured to use
some other port), or, perhaps local HTTPS access to the management
interface (using 443 instead of HTTP = 80).

 

   I wouldn't bet on it, but you might try configuring your server to
use a different port (say, 5443?), and adjusting the port-forwarding
rule accordingly.

 

   You might also try an external port which is further from the maximum
(say, 55483).

 

   Actual Netgear support might know something, too.

Message 8 of 8
Top Contributors
Discussion stats
  • 7 replies
  • 738 views
  • 0 kudos
  • 2 in conversation
Announcements