Home
last modified time | relevance | path

Searched refs:NAT (Results 1 – 25 of 26) sorted by relevance

12

/external/ipsec-tools/src/racoon/samples/
Dracoon.conf.sample-natt4 # This file can be used as a template for NAT-Traversal setups.
5 # Only NAT-T related options are explained here, refer to other
19 # To use NAT-T you must also open port 4500 of
29 # To keep the NAT-mappings on your NAT gateway, there must be
34 # whom it does NAT-Traversal.
43 # a NAT which translates its address to 172.16.1.3, you need the
45 # On 172.16.0.1 (e.g. behind the NAT):
61 # NAT-T is supported with all exchange_modes.
64 # With NAT-T you shouldn't use PSK. Let's go on with certs.
68 # This is the main switch that enables NAT-T.
[all …]
/external/webrtc/webrtc/base/
Dnattypes.cc17 class SymmetricNAT : public NAT {
24 class OpenConeNAT : public NAT {
31 class AddressRestrictedNAT : public NAT {
38 class PortRestrictedNAT : public NAT {
45 NAT* NAT::Create(NATType type) { in Create()
Dnattypes.h25 class NAT {
27 virtual ~NAT() { } in ~NAT()
42 static NAT* Create(NATType type);
Dnatserver.h30 explicit RouteCmp(NAT* nat);
40 explicit AddrCmp(NAT* nat);
90 TransEntry(const SocketAddressPair& r, AsyncUDPSocket* s, NAT* nat);
111 NAT* nat_;
Dnatserver.cc18 RouteCmp::RouteCmp(NAT* nat) : symmetric(nat->IsSymmetric()) { in RouteCmp()
41 AddrCmp::AddrCmp(NAT* nat) in AddrCmp()
131 nat_ = NAT::Create(type); in NATServer()
229 const SocketAddressPair& r, AsyncUDPSocket* s, NAT* nat) in TransEntry()
/external/ipsec-tools/
DNEWS6 o Fixed a NAT-T flag check
14 o NAT-T fixes related to purging of IPsec SA:s and retransmission
58 o NAT-T works with multiple peers behind the NAT (need kernel support)
102 o Fixed NAT-T with more proposals (e.g. more crypto algos).
109 o Fixed NAT-T in aggresive mode.
118 o Added documentation for NAT-T
119 o Better NAT-T diagnostic.
123 o Support for NAT Traversal (NAT-T)
DChangeLog94 when NAT-T enabled and trying to purge non NAT-T SAs
330 some port matching problems with NAT-T
333 track some port matching problems with NAT-T
454 * src/racoon/cfparse.y: Fixed a check of NAT-T support in libipsec
698 required even without NAT-T
/external/libcxx/test/std/thread/thread.mutex/thread.lock/thread.lock.guard/
Dvariadic_types.pass.cpp28 struct NAT {}; struct
34 auto test_typedef(...) -> NAT;
38 return !std::is_same<decltype(test_typedef<LG>(0)), NAT>::value; in has_mutex_type()
/external/ipsec-tools/src/racoon/doc/
DFAQ36 Enable NAT-Traversal. This needs kernel support, which is
37 available on Linux. On NetBSD, NAT-Traversal kernel support
41 using NAT-Traversal might infringe a patent.
45 able to ditinguish peers hidden behind the same NAT.
49 behind the same NAT.
/external/curl/docs/cmdline-opts/
Dftp-ssl-ccc.d9 unencrypted. This allows NAT routers to follow the FTP transaction. The
/external/tcpdump/tests/
DOLSRv1_HNA_sgw_1.out6 Smart-Gateway: LINKSPEED IPV4 IPV4-NAT 10000/10000, 10.175.220.0/24
/external/mdnsresponder/mDNSWindows/DLLX/
DDLLX.idl218 kDNSSDError_NATPortMappingUnsupported = -65564, /* NAT doesn't support NAT-PMP or UPnP */
219 …kDNSSDError_NATPortMappingDisabled = -65565, /* NAT supports NAT-PMP or UPnP but it's disabled…
/external/iptables/extensions/
Dlibxt_addrtype.man38 .BI "NAT"
Dlibxt_DNAT.man25 Later Kernels (>= 2.6.11-rc1) don't have the ability to NAT to multiple ranges
Dlibxt_SNAT.man26 Later Kernels (>= 2.6.11-rc1) don't have the ability to NAT to multiple ranges
/external/iptables/iptables/
Dnft.h12 #define NAT 4 macro
Dnft.c414 [NAT] = {
499 [NAT] = {
/external/iproute2/doc/
Dip-cref.tex1212 \item \verb|nat| --- a special NAT route. Destinations covered by the prefix
1215 are selected with the attribute \verb|via|. More about NAT is
1216 in Appendix~\ref{ROUTE-NAT}, p.\pageref{ROUTE-NAT}.
1297 For NAT routes it is the first address of the block of translated IP destinations.
2078 table. NAT and masquerading rules have an attribute to select new IP
2096 of the IP packet into some other value. More about NAT is
2097 in Appendix~\ref{ROUTE-NAT}, p.\pageref{ROUTE-NAT}.
2172 The \verb|ADDRESS| may be either the start of the block of NAT addresses
2173 (selected by NAT routes) or in linux-2.2 a local host address (or even zero).
2176 More about NAT is in Appendix~\ref{ROUTE-NAT},
[all …]
/external/mdnsresponder/
DPrivateDNS.txt111 2) Upon setup every LLQ must NAT map two ports. Upon tear down every LLQ
112 must tear down two NAT mappings.
/external/iptables/utils/
Dpf.os163 # the case that X is a NAT firewall. While nmap is talking to the
/external/mdnsresponder/mDNSCore/
DmDNSEmbeddedAPI.h905 #pragma mark - NAT Traversal structures and constants
DuDNS.c416 #pragma mark - NAT Traversal
/external/dnsmasq/
DCHANGELOG.archive53 A really clever NAT-like technique allows the daemon to have lots
56 any more memory after start-up. The NAT-like forwarding was
/external/libmicrohttpd/
DChangeLog993 client (special use-case for servers behind NAT), thereby
/external/libmicrohttpd/doc/
Dlibmicrohttpd.texi1488 server is behind NAT and needs to connect out to the

12