- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Port forwarding not working
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nighthawk R8300
Firmware: V1.0.2.130
I've setup port forwarding for two ports on same server. There are services listening on those ports. I can access them using my local IP and port. I've attached a screenshot of my config.
When I check the log it looks like the port is being fowarded correctly but notice the port on the incoming.
[LAN access from remote] from 73.64.xxx.yyy:64092 to 192.168.1.35:8888, Sunday, May 05,2019 07:00:55
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Should have thought of this sooner when setting up the FiOS router (192.168.1.1) in bridge mode and the Nighthawk (192.168.1.4) as the primary router...All my devices have a static IP so they are all hard-coded to use my original router's IP for the gateway/router IP (192.168.1.1).
Everything started working once I flipped the IPs so the Nighthawk is set to 192.168.1.1.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port forwarding not working
Greetings,
Remove what you have entered.
Click +Add Custom Service instead of +Add.
Now use netstat -a to ensure the machine is listening.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port forwarding not working
> I've setup port forwarding for two ports on same server. There are
> services listening on those ports. I can access them using my local IP
> and port. I've attached a screenshot of my config.
Ok. And what, exactly, does _not_ work?
> When I check the log it looks like the port is being fowarded
> correctly but notice the port on the incoming.
Yes, and you were expecting the remote port to be "8888" also?
Don't. The port used at the far end is independent of the port where
the server is listening.
Free advice: Enabling SSH access on external port 22 wiil almost
certainly attract frequent break-in attempts. You'd be wiser to use
some other external port for that purpose, I claim. SSH and related
commands have a "-p <port>" option for a reason.
> Remove what you have entered.
It looks fine to me, except for the unwise choice of "External Port
22".
> Now use netstat -a to ensure the machine is listening.
Because "I can access them using my local IP and port" is not a
sufficient test?
My advice is to beware of free advice.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port forwarding not working
@farbodr wrote:
I've setup port forwarding for two ports on same server. There are services listening on those ports. I can access them using my local IP and port. I've attached a screenshot of my config.
Looks OK if the LAN IP is correct, and both 22/TCP and 8888/TCP should be reachable.
@farbodr wrote:
When I check the log it looks like the port is being fowarded correctly but notice the port on the incoming.
[LAN access from remote] from 73.64.xxx.yyy:64092 to 192.168.1.35:8888, Sunday, May 05,2019 07:00:55
Nothing wrong, the source port can be any...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Port forwarding not working
I'm in the same boat and I see port forwarded correctly in the logs but it's not actually establishing a connection. I can telnet to it from my box internally, but doesn't work when trying to do the same from a remote host. Logs show the port it's connecting to and the internal server but nothing actually happens.
FWIW, I'm using a FiOS G1100 Modem+Router in bridge mode, passing the traffic to the R7900P.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Should have thought of this sooner when setting up the FiOS router (192.168.1.1) in bridge mode and the Nighthawk (192.168.1.4) as the primary router...All my devices have a static IP so they are all hard-coded to use my original router's IP for the gateway/router IP (192.168.1.1).
Everything started working once I flipped the IPs so the Nighthawk is set to 192.168.1.1.
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more