NETGEAR "Stealthily" Releases the Nighthawk X6S R7960P

kc6108

Regular Contributor
@e38BimmerFN

Ask and you shall receive...

Here are the results of the test:

UPnP Test (?): found: RAX120 (Gateway)
UPnP Port mapping works



STUN Test (?): Full Cone NAT



UDP Binding Test (?): Endpoint independent binding, port prediction is easy
TCP Binding Test: Endpoint independent binding, port prediction is easy



UDP Mapping Test (?): your external IP address was different from your local one (NAT).
Your external source ports were preserved on every connection.
TCP Mapping Test: your external IP address was different from your local one (NAT)
Your external source ports were preserved on every connection.



SIP ALG (?): The initial SIP INVITE packet has been modified.
Most probably, your NAT implements a SIP-ALG
FTP ALG:
The initial FTP PORT command has been modified.
Most probably, your NAT implements a FTP-ALG



UDP Hole Punching (?): High TTL Test was not successful
Low TTL Test was not successful
Silent Test was not successful
TCP Hole Punching:
High TTL Test was not successful
Silent Test was not successful



UDP Timeout (?): Your UDP timeout is approx. 40 seconds
There should be no problem when refreshing bindings.m
 
Last edited:

e38BimmerFN

Very Senior Member
@kc6108 You the man. Great results. Thank you for verifying. Glad to see FULL CONE NAT. Now hope that NG can fix the R7960P and R8000P routers for this issue. :oops:
 

kc6108

Regular Contributor
@e38BimmerFN

I didn't reboot the router after changing 'NAT Filtering' to 'Open'. After rebooting the results of the test changed slightly under the 'UDP Hole Punching' section. Just FYI...

http://nattest.net.in.tum.de/individualResult.php?hash=c9f7e327afc9d8cd544ee4a288b2b8fc

Here are the results of the test:

UPnP Test (?): found: RAX120 (Gateway)
UPnP Port mapping works



STUN Test (?): Full Cone NAT



UDP Binding Test (?): Endpoint independent binding, port prediction is easy
TCP Binding Test: Endpoint independent binding, port prediction is easy



UDP Mapping Test (?): your external IP address was different from your local one (NAT).
Your external source ports were preserved on every connection.
TCP Mapping Test: your external IP address was different from your local one (NAT)
Your external source ports were preserved on every connection.



SIP ALG (?): The initial SIP INVITE packet has been modified.
Most probably, your NAT implements a SIP-ALG
FTP ALG:
The initial FTP PORT command has been modified.
Most probably, your NAT implements a FTP-ALG



UDP Hole Punching (?): High TTL Test was not successful
Low TTL Test was not successful
Silent Test was successful
TCP Hole Punching:
High TTL Test was not successful
Low TTL Test was not successful
Silent Test was not successful



UDP Timeout (?): Your UDP timeout is approx. 40 seconds
There should be no problem when refreshing bindings.m
 

kc6108

Regular Contributor
@e38BimmerFN

I ran another test as a sanity check, and the 'UDP Hole Punching' section changed yet again. Thoughts? Just curious on my part.

http://nattest.net.in.tum.de/individualResult.php?hash=013d5d377e2624c0b2c0e2a8495515f8

Here are the results of the test:

UPnP Test (?): found: RAX120 (Gateway)
UPnP Port mapping works



STUN Test (?): Full Cone NAT



UDP Binding Test (?): Endpoint independent binding, port prediction is easy
TCP Binding Test: Endpoint independent binding, port prediction is easy



UDP Mapping Test (?): your external IP address was different from your local one (NAT).
Your external source ports were preserved on every connection.
TCP Mapping Test: your external IP address was different from your local one (NAT)
Your external source ports were preserved on every connection.



SIP ALG (?): The initial SIP INVITE packet has been modified.
Most probably, your NAT implements a SIP-ALG
FTP ALG:
The initial FTP PORT command has been modified.
Most probably, your NAT implements a FTP-ALG



UDP Hole Punching (?): High TTL Test was not successful
Low TTL Test was successful
Silent Test was successful
TCP Hole Punching:
High TTL Test was not successful



UDP Timeout (?): Your UDP timeout is approx. 29 seconds
This is a common value for the UDP timeout.
However, if an application doesn't send enough keep alive packets, this could be a problem
 

e38BimmerFN

Very Senior Member
AH ok. Yes a reboot is needed to ensure the setting took and all other data caches are cleared out. Thank you for testing this. The "Gaming with Full Cone vs Symmetric NAT Routers" web page has been updated. ;)
 

e38BimmerFN

Very Senior Member
UDP Hole Punching (?): High TTL Test was not successful
Low TTL Test was not successful
Silent Test was not successful then Silent Test was successful.

I usually don't pay any attention to these. Something you might contact the web master of that nat test page to see. I don't see any web page information on what some of these results are all about.

Patrick Sattler
[email protected]
 

e38BimmerFN

Very Senior Member
I believe it's the P version. Something to ask Costco about to see what they actually stock. They may have both.
I am confused. Is the Costco version the R8000 or the R8000P?
 

coxhaus

Part of the Furniture
So is Full Cone NAT the same as one-to-one NAT where you map an outside IP address to a range of private IP addresses? I am trying to under stand this in Cisco small business router terms.
 

e38BimmerFN

Very Senior Member

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top