-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test questions #46
Comments
The Behavior test measures how predictable the port mapping is with respect
to source address (ip and port) to destination address. Most well behaved
NATs will have Endpoint Independent Mapping - meaning that the same
external port is used to map to the internal ip:port pair regardless of
what remote address is used.
Some NAT environments (whether a result of a NAT device or the ISP) are
Address and Port dependent mapping - which means the port mapping is
difficult to predict. Subsequent P2P or VOIP calls may need a relay server.
The Filtering test measures how open the device can be reached from
addresses and ports it did not originally send to. Given that most NATs
act as firewalls in addition to the PC having its own local firewall,
incoming packets are simply dropped if there was not any corresponding
outbound packet sent to the remote address it originated from. Hence,
unless you've turned off your PC's firewall and connect it directly to the
internet (without a NAT), you are almost guaranteed to have Address and
Port Dependent Filtering.
Does that make sense? I can elaborate more if needed.
For what it's worth, I don't find the Behavior and Filtering tests
particularly useful for establishing connectivity with another
endpoint. They are best used to simply log the NAT type so you can debug
the reasons for a failed connectivity failure later.
…On Thu, Jan 27, 2022 at 12:50 AM gengfeipeng ***@***.***> wrote:
Why the detected filter types are all AddressAndPortDependentFiltering,
but the map detection has EndpointIndependentMapping and
AddressAndPortDependentMapping types. Is there anything to pay attention to
in filter detection?
—
Reply to this email directly, view it on GitHub
<#46>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHNSF2QZPITS4OYZ2I5RXTUYEBONANCNFSM5M5IJQ4Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why the detected filter types are all AddressAndPortDependentFiltering, but the map detection has EndpointIndependentMapping and AddressAndPortDependentMapping types. Is there anything to pay attention to in filter detection?
The text was updated successfully, but these errors were encountered: