#1 I point to and quote part of DSLR (dslreports.com) -> Forums -> Software and Operating Systems -. All Things Unix -> Windows 10: Another reason to use Linux!
As I stated in that thread I fail to see the point in using this program.
Why? Most routers today have a pretty simple GUI based interface to setup forwarding of ports for programs. And thus this program has NO USE.
IF you KNOW the ports.... Now there is the rub..... but here is also the part where users can learn something(s). Yeah I can rattle off ports/programs for the popular stuff, one cause I use it, and two stupid A+/Network+ ask you to fill out such stuff on their tests.
I would suggest creating a thread in the networking or software forum(S) and posting WHAT SOFTWARE this is, and most can probably tell you which port(S) to open in your router. Most routers have the basics for ftp etc. covered.. For some program I am sure it is just a google search away mostly to find the port(s) needed, or even using uPNP (although that would NOT be my choice, security risk) again simple GUI on/off in most consumer/low end SOHO routers.
Most will probably be glad to tell you the port(S) and post some screen snaps if needed to set this up.
Again I just don't see the purpose or need for this program?!?!?
#2 Thinking about what I was told, they are correct
#3 As how to forward manually, it goes like this...
#1 As how to check what the IP Address is/are, Subnet Mask is/are, Default Gateway is, MAC Address(es) is/are, DNS Server(s) are of your computer, it depends on the OS and Version.
Note: This example assumes that you are on Windows 2000, Windows XP, Windows Vista, Windows 7, Windows 8 or Windows 10
a) Press the Windows Start key to open the Start screen.
b) Type cmd
and press Enter to launch the command prompt.
Note: You do not need to click on anything on the Start screen—typing will automatically initiate a program search.
c) Type ipconfig /all
at the command prompt to check the network card settings.
d) If not on Windows 2000, Windows XP, Windows Vista, Windows 7, Windows 8 or Windows 10 and you do not know how to check that network info - then post what is your OS and Version is.
e) You need to make sure that the Default Gateway on your computer is the same LAN IP as your NAT router.
#4 On http://ipv4.whatismyv6.com/
is the non bogan/Public/route-able IPv4 Address that users from Internet use to connect to you.
#5 In your router, at the Status page in there you must have the same non bogan IP Address.
a) It will look something like the screen that you see at http://event.asus.com/2012/nw/dummy_ui/en/
b) If you are not taken to a screen that looks like that after logging in, go to it.
c) Example non bogan IP Address is 999.888.777.666, but in the router the WAN IP is 10.0.0.100 - this is not ok.
d) Important note: This is not to say that the non bogan IP Address has to be Static.
e) Example yesterday's IP Address was 999.888.777.666 and today's IP Address is 999.888.777.555 - this is ok.
#7 If you do not see the non bogan IP Address anywhere in the your NAT routers screens, it first matters what the WAN IP Address in it is:
a) From 100.64.0.0 - 100.127.255.255, then CGNAT/NAT444/LSN is present
If you want more details about CGNAT/NAT444/LSN, you can look athttp://en.wikipedia.org/wiki/Carrier-grade_NAT
c) The possible fixes to fix your issue if CGNAT/NAT444/LSN is present.
#1 Have them in their NAT router forward the ports to the IP of your router..
#2 Upgrading the type of plan that you are on with your ISP so that you get a non bogan IP Address.
For example if you are a Residential Service Plan, consider going to a Business Service Plan.
#3 Consider switching to another ISP that can give you you a non bogan IP Address.
#4 For the long term future, get IPv6 working.
b) From 10.0.0.0 to 10.255.255.255, from 172.16.0.0 to 172.31.255.255 OR from 192.168.0.0 to 192.168.255.255 - based upon your NAT router, then:
Step 1: Physically find your ASUS
Step 2: Find the WAN
port of it.
port could be called Internet
or To Modem
or To ONT
Step 3: Report back what the brand and model of the device that is connected at the other end of the wire that is connected to the WAN port of the ASUS.
c) If the WAN IP is not the same and is not any of these/those IP Address(es), it would be a good idea to check to see how the non bogan IP Address is not the same (and not NAT). If you need help finding why that is, you are to asking for help doing so.
#7 Moving along assuming that the non bogan/Public/route-able IP Address is the same (even if it is not static / "always the same") :
When forwarding manually remember to forward to your local IP Address, that is unless you are trying to forward some other computer (example to Xbox)
So if you get output...
IP Address 192.168.1.6
Subnet Mask 255.255.255.0
Default Gateway 192.168.1.1
At least one DNS 192.168.1.1
#8 Now, moving along assuming that your are forwarding to your local IP Address.
From DSLR (dslreports.com) -> Forums -> Broadband and Networking -> Networking -> How to know if ports are reaching my computer from outside
the post by DSLR user mackey
(user # 1479488
) on 2015-Sep-24
at 8:05 pm
- if you wanted to test port 5154, besides using an inbound client side port checker:
Run tcpdump (`tcpdump -p -n -i <interface> port 5154` would be a good command to start with). If you see incoming TCP SYN packets (not SYN/ACK), or incoming UDP packets from an IP which did not have an outgoing packet first, then the port is open.
-> For tcpdump on Windows I found this info https://uwnthesis.wordpress.com/2014/05/26/windump-how-to-use-windump-tcpdump-on-windows-7-the-visual-guide/
-> For a TCP and a UDP port checker you can use http://www.base64online.com/port-check.php
-> Using a packet sniffer (like tcpdump = command line / like wireshark = GUI) you should see the traffic from an outside IP address reaching your computer, like I did (when you are forwarding the ports to your computer).
user-name@pc-name:~$ tcpdump -p -n -i eth0 port 5154
tcpdump: eth0: You don't have permission to capture on that device
(socket: Operation not permitted)
user-name@pc-name:~$ sudo tcpdump -p -n -i eth0 port 5154
[sudo] password for user-name:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
08:40:24.169428 IP 192.168.2.138.50157 > 192.168.2.255.5154: UDP, length 6
08:42:15.839461 IP 22.214.171.124.37174 > 192.168.2.138.5154: Flags [S], seq 1464127243, win 8192, options [mss 1460], length 0
08:49:05.773987 IP 126.96.36.199.51145 > 192.168.2.138.5154: UDP, length 0
08:49:06.938818 IP 188.8.131.52.36530 > 192.168.2.138.5154: UDP, length 0
08:57:57.580814 IP 184.108.40.206.42092 > 192.168.2.138.5154: Flags [S], seq 3027635480, win 14600, options [mss 1460,sackOK,TS val 4240686068 ecr 0,nop,wscale 8], length 0
08:57:57.712334 IP 220.127.116.11.42093 > 192.168.2.138.5154: Flags [S], seq 1267700791, win 14600, options [mss 1460,sackOK,TS val 4240686102 ecr 0,nop,wscale 8], length 0
08:57:57.840328 IP 18.104.22.168.42095 > 192.168.2.138.5154: Flags [S], seq 1515263633, win 14600, options [mss 1460,sackOK,TS val 4240686134 ecr 0,nop,wscale 8], length 0
7 packets captured
7 packets received by filter
0 packets dropped by kernel
-> Some notes about my testing..
a) 192.168.2.138.50157 is from this same computer.
b) As noted at grc.com -> Services -> Shield's Up
they own 22.214.171.124 -thru- 126.96.36.199.
c) I believe 188.8.131.52 is from http://www.yougetsignal.com/tools/open-ports/
as it only checks TCP ports.
d) As you can see, I checked port 5154.
-> The only UDP ports that grc.com checks, that I know of, are:
a) DNS (53) grc.com -> Freeware -> Utilities -> DNS Benchmark -> DNS Spoofability Test Introduction (or grc.com -> Services -> DNS Spoofability Test)
#9 Now, moving along assuming that you see traffic that is reaching your computer from the outside:
Here are some notes about listening:
a) If you are on Windows I point you to http://www.howtogeek.com/howto/28609/how-can-i-tell-what-is-listening-on-a-tcpip-port-in-windows/
b) If you are not on Windows (Mac, Unix/Linux), go look lookup listen on port and then your OS name using Google (or your other favorite search engine).
c) If nothing is listening any TCP ports that you check with a web based port checker, then TCP ports does not show up as open.
d) Be advised that you can not have two servers listening on the same the port on the same computer. So for example before you use an inbond-client side port checker you must make sure that uTorrent is not running - which explains on http://portforward.com/softwareguides/utorrent/utorrent.htm that they say
If uTorrent is currently open, you will need to completely close it at this time. Make sure that the green uTorrent icon is not still hiding in your notification area (next to your clock). If it is, right click on it and choose "Exit". Before moving forward to things like selecting torrents, seeders, and leachers, we need to verify that your port is open. We recommend downloading our free Open Port Check Tool to test if incoming connections are being allowed through your router on your uTorrent Listening Port
e) And generally if the program/app is running that you are trying to forward for, then the server is listening.
#10 Now, moving along assuming that your server is in the listening state ( and now users from the net should be able to connect to you) :
Part two: Here are some catches about ping:
a) If the server that you forwarded requires that you reply to ping, well then you must enable responding to ping in the router.
b) If the server that you forwarded does not require that you reply to ping, well that depends on another factor..
As to what that other factor is, I point to and quote the post by nwrickert (DSLR user #1070900)
in DSLR (dslreports.com) Forums >Broadband Tech > Security > Security > DMZ and portforwarding are equally dangerous?
While he tells people that responding to ping is dangerous, he replys to ping.
That's a pretty minor point. The reason some people prefer to not respond to ping, is to avoid demonstrating their presence on the net. Gibson has a public site whose presence on the net is well known, so that reason for not responding to ping simply does not apply.
While Steve Gibson does sometimes say some useful things, he mostly seems to be making mountains out of molehills
Note: Sorry for my misspelling, I meant replies.
c) There are certain troubleshooting tools that require that you reply to ping.
For example if you wanted to use the followings tool(s) at DSLR (dslreports.com) -> Tools
, Line quality - Ping Test
, and for 24x7 Line Monitoring
#11 If the ports are open (this means not just in the router) but the program/app does not work: I have an odd feeling that with this server, you must reply to ping.
Part three: With most apps/programs that you forward, you must provide to users from the outside either your non non bogan/Public/route-able IP Address or DDNS.
What DNS is, here is the simple as possible version as how it works.
I know of a given domain name. What is the IP Address for that domain?
The first D in DDNS means/allows you to have a domain name the follows your non static non bogan IP Address. Which is a lot easier to provide and normally most people use DNS over the IP Address for the content servers that they want to connect to..