PcWinTech.com Forums

Tools & Programs By PcWinTech.com => (Program) Simple Port Forwarding => Topic started by: Techman Pro on January 10, 2018, 01:06:40 PM

Title: Arris Surfboard SB6183
Post by: Techman Pro on January 10, 2018, 01:06:40 PM
The list of routers in the program doesn't show this specific modem, is there any other modem that comes close to matching the on I have which is the Arris SB6183? Trying to do port forwarding but can not do anything since I can not pass this part. :sarcastic:
Title: Re: Arris Surfboard SB6183
Post by: trpted on January 11, 2018, 12:59:04 PM
#1 In the screen shot you are showing the Asus RT-N16.

#2 For that NAT router either,

a) http://www.simpleportforwarding.com/supported-routers Asus - RT-N16 (Asus Firmware)

b) OR see and follow http://www.pcwintech.com/port-forwarding-asus-rt-n15-asus-firmware

#3 While I know that your Arris Surfboard SB6183 has a power supply and TV cable connected to it. is there anything else that is between the Arris Surfboard SB6183 and your Asus RT-N16?

If so, report back the brand and model of all device(s) - if any are found.

#4 What/who is your ISP?
Title: Re: Arris Surfboard SB6183
Post by: Techman Pro on January 13, 2018, 08:22:12 PM
Hi, I do not have anything else in between the cable modem and router, also my ISP is Spectrum.
Title: Re: Arris Surfboard SB6183
Post by: trpted on January 15, 2018, 12:59:32 PM

#1 At http://ipv4.whatismyv6.com/ is the IPv4 Address that users from the net use to connect to you.

#2 In the router after you log-in you will see a page that looks something like what you see at https://event.asus.com/2012/nw/dummy_ui/en/index.html

#3 In your router, not the demo / emulator!! , in the WAN area you should see the same true WAN IP (as seen with/on step 1).

#4 If not, report back that fact.

#5 If the WAN IP in the router matches the true WAN IP, then the next goes like this..

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.

#6 If the Default Gateway does not match, report back that fact.

#7 Otherwise - 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
Subnet Mask
Default Gateway
At least one DNS

-> you would forward to


a) From DSLR (dslreports.com) -> Forums -> Broadband and Networking -> Networking -> How to know if ports are reaching my computer from outside (http://www.dslreports.com/forum/r30314241-) 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.

b) 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/

#9 For a TCP and a UDP port checker you can use http://www.base64online.com/port-check.php

#10 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).

Code: [Select]
    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 > UDP, length 6
    08:42:15.839461 IP > Flags [S], seq 1464127243, win 8192, options [mss 1460], length 0
    08:49:05.773987 IP > UDP, length 0
    08:49:06.938818 IP > UDP, length 0
    08:57:57.580814 IP > 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 > 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 > 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

#11 Some notes about my testing..

a) is from this same computer.

b) As noted at grc.com -> Services -> Shield's Up they own -thru-

c) I believe is from http://www.yougetsignal.com/tools/open-ports/ as it only checks TCP ports.

d) As you can see, I checked port 5154.

#12 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)

b) Universal Plug n'Play (UPnP) = 1900


From grc.com -> Services -> Shield's Up: Click on Proceed and then GRC's Instant UPnP Exposure Test.

#13 Info part 8, after you get the ports the ports forwarded in the router:

Info - Part a)

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.

Info - Part b)

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? (http://www.dslreports.com/forum/r24693587-) on 2010-08-21 at 13:53:23.
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 (http://www.dslreports.com/tools): Smokeping, Line quality - Ping Test, and for 24x7 Line Monitoring...

d) 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.

Info - Part c:

You must provide to users from the outside either your non bogan 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 their 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.. ;)