| /netbsd-src/crypto/dist/ipsec-tools/src/racoon/rfc/ |
| H A D | rfc3947.txt | 107 In the basic scenario for this document, the initiator is behind
120 behind NAT, but the process of how to locate the other end is out of
121 the scope of this document. In one scenario, the responder is behind
142 o only one IPsec host is behind the NAT, or
195 the peer "behind" the NAT.
262 as defined in the [RFC3948] (this end is behind the NAT).
306 multiple clients behind the NAT (See [RFC3715], section 2.3, case n).
314 Take the common case of the initiator behind the NAT. The initiator
415 The most common case for the responder behind the NAT is if the NAT
423 document. For instance, if the responder is behind a port
[all …]
|
| H A D | draft-ietf-ipsec-nat-t-ike-03.txt | 123 (only one (IPsec) host behind the NAT or for the first IPsec host it can
155 to initiate from the peer "behind" the NAT.
254 port 500 even if there are multiple clients behind the NAT. They can
262 Take the common case of the initiator behind the NAT. The initiator must
348 The most common case for the responder behind the NAT is if the NAT is
361 use. For instance, if the responder is behind a port translating NAT,
435 I.e. only the machine(s) that are actually behind the NAT need to send
476 the host behind NAT are not meaningful, so the IP and port numbers MUST
486 is rebooted). To recover from those ends which are NOT behind NAT SHOULD
488 which IP and port addresses the should be used. The host behind dynamic
[all …]
|
| H A D | draft-ietf-ipsec-nat-t-ike-08.txt | 109 behind NA(P)T and the responder has a fixed static IP address.
112 behind NAT, but the process of how to locate the other end is out of the
113 scope of this document. In one scenario, the responder is behind a
140 o only one IPsec host behind the NAT
185 need to initiate from the peer "behind" the NAT.
244 the [Hutt03] (this end is behind the NAT).
281 clients behind the NAT (See [Aboba03] section 2.3, case n). They can
289 Take the common case of the initiator behind the NAT. The initiator must
384 The most common case for the responder behind the NAT is if the NAT is
392 instance, if the responder is behind a port translating NAT, and the
[all …]
|
| H A D | draft-ietf-ipsec-nat-t-ike-05.txt | 127 o only one IPsec host behind the NAT
161 to initiate from the peer "behind" the NAT.
262 source port 500 even if there are multiple clients behind the NAT. They
269 Take the common case of the initiator behind the NAT. The initiator must
360 The most common case for the responder behind the NAT is if the NAT is
367 to use. For instance, if the responder is behind a port translating NAT,
433 The initiator is behind a NAT talking to the publicly available
512 the host behind NAT are not meaningful, so the IP and port numbers MUST
522 is rebooted). To recover from those ends which are NOT behind NAT SHOULD
524 which IP and port addresses should be used. The host behind dynamic NAT
[all …]
|
| H A D | draft-ietf-ipsec-nat-t-ike-07.txt | 126 o only one IPsec host behind the NAT
160 to initiate from the peer "behind" the NAT.
261 source port 500 even if there are multiple clients behind the NAT. They
268 Take the common case of the initiator behind the NAT. The initiator must
360 The most common case for the responder behind the NAT is if the NAT is
367 to use. For instance, if the responder is behind a port translating NAT,
439 The initiator is behind a NAT talking to the publicly available
518 the host behind NAT are not meaningful, so the IP and port numbers MUST
534 is rebooted). To recover from those ends which are NOT behind NAT SHOULD
536 which IP and port addresses should be used. The host behind dynamic NAT
[all …]
|
| H A D | draft-ietf-ipsec-nat-t-ike-06.txt | 127 o only one IPsec host behind the NAT
161 to initiate from the peer "behind" the NAT.
262 source port 500 even if there are multiple clients behind the NAT. They
269 Take the common case of the initiator behind the NAT. The initiator must
360 The most common case for the responder behind the NAT is if the NAT is
367 to use. For instance, if the responder is behind a port translating NAT,
439 The initiator is behind a NAT talking to the publicly available
518 the host behind NAT are not meaningful, so the IP and port numbers MUST
534 is rebooted). To recover from those ends which are NOT behind NAT SHOULD
536 which IP and port addresses should be used. The host behind dynamic NAT
[all …]
|
| H A D | draft-ietf-ipsec-nat-t-ike-02.txt | 123 (only one (IPsec) host behind the NAT or for the first IPsec host it can
155 to initiate from the peer "behind" the NAT.
254 port 500 even if there are multiple clients behind the NAT. They can
262 Take the common case of the initiator behind the NAT. The initiator must
348 The most common case for the responder behind the NAT is if the NAT is
361 use. For instance, if the responder is behind a port translating NAT,
435 I.e. only the machine(s) that are actually behind the NAT need to send
476 the host behind NAT are not meaningful, so the IP and port numbers MUST
486 is rebooted). To recover from those ends which are NOT behind NAT SHOULD
488 which IP and port addresses the should be used. The host behind dynamic
[all …]
|
| H A D | draft-ietf-ipsec-nat-t-ike-04.txt | 128 o only one IPsec host behind the NAT
162 to initiate from the peer "behind" the NAT.
263 source port 500 even if there are multiple clients behind the NAT. They
270 Take the common case of the initiator behind the NAT. The initiator must
362 The most common case for the responder behind the NAT is if the NAT is
369 to use. For instance, if the responder is behind a port translating NAT,
443 I.e. only the machine(s) that are actually behind the NAT need to send
483 the host behind NAT are not meaningful, so the IP and port numbers MUST
493 is rebooted). To recover from those ends which are NOT behind NAT SHOULD
495 which IP and port addresses should be used. The host behind dynamic NAT
[all …]
|
| H A D | rfc3715.txt | 237 multiple hosts behind the NAPT initiate IKE SAs to the same
249 initiating hosts behind a NAT use their source IP addresses in
267 inspecting outgoing traffic. Thus, were two hosts behind the NAT
288 host or gateway, the internal hosts behind the same NAPT can
327 establishment of IPsec SAs to hosts behind the NA(P)T.
349 one host is behind the NAT. Such NAPTs are unable to enable SCTP,
482 behind the NA(P)T, although mapping state should be maintained
495 behind at least one NA(P)T, or alternatively, both the client and
496 the VPN gateway may be behind one or more NA(P)Ts. Telecommuters
497 may use the same private IP address, each behind their own NA(P)T,
[all …]
|
| H A D | rfc3948.txt | 458 Ari and Bob, behind the same NAT talking securely to the same server
528 The server sees all clients behind the NAT as the same IP address, so
541 is impossible to guarantee security from some clients behind a NAT,
542 while allowing clear text from different clients behind the SAME NAT.
544 best-effort security: If the client from behind the NAT initiates
626 problem of multiple clients behind the same NAT simultaneously
665 DHCP-IPsec method, regardless of whether it knows it is behind a NAT.
679 discovers from NAT-D that the initiator is behind a NAT and its local
|
| H A D | draft-ietf-ipsec-nat-t-ike-01.txt | 114 (only one (IPsec) host behind the NAT or for the first IPsec host it can
152 to initiate from the peer "behind" the NAT.
308 I.e. only the machine(s) that are actually behind the NAT need to send
361 keys for everybody behind the NAT box, which is huge security risk.
365 internal address used behind the NAT box by trying all possible IP-
382 the internal ip address behind the NAT to the other end. In this case
|
| H A D | draft-ietf-ipsec-udp-encaps-03.txt | 331 Ari and Bob, behind the same NAT talking securely to the same server.
390 The server sees all clients behind the NAT as the same IP address,
402 So it is impossible to guarantee security from some clients behind
403 a NAT, and also allow clear text from different clients behind the
405 do best effort security: if the client from behind the NAT
|
| H A D | draft-ietf-ipsec-nat-t-ike-00.txt | 131 to initiate from the peer "behind" the NAT.
283 I.e. only the machine(s) that are actually behind the NAT need to send
339 keys for everybody behind the NAT box, which is huge security risk.
343 internal address used behind the NAT box by trying all possible IP-
366 the internal ip address behind the NAT to the other end. In this case
|
| /netbsd-src/games/quiz/datfiles/ |
| H A D | spell | 1 The son went behind a cloud.:sun
|
| /netbsd-src/crypto/dist/ipsec-tools/src/racoon/samples/ |
| H A D | racoon.conf.sample-natt | 42 # 172.16.0.1 and 172.16.1.1, where the first gateway is behind
45 # On 172.16.0.1 (e.g. behind the NAT):
|
| /netbsd-src/external/public-domain/tz/dist/ |
| H A D | etcetera | 17 # behind GMT but uses the completely misleading abbreviation "GMT".
41 # the abbreviation "-04" and corresponds to 4 hours behind UT
|
| /netbsd-src/sys/dev/dm/doc/ |
| H A D | design.txt | 80 Kernel driver will place list of struct dm_name_list behind
114 Change name of selected device to string found behind struct dm_ioctl header
195 DM driver will copyout dm_target_spec structures behind struct dm_ioctl.
265 behind end (start of data part is pointed with data_start var.) of dm-ioctl struct.
|
| /netbsd-src/crypto/dist/ipsec-tools/src/racoon/doc/ |
| H A D | FAQ | 45 able to ditinguish peers hidden behind the same NAT.
49 behind the same NAT.
|
| /netbsd-src/external/apache2/llvm/dist/llvm/utils/gn/secondary/llvm/unittests/Passes/ |
| H A D | BUILD.gn | 38 # Otherwise, reconfiguring with plugins disabled will leave behind a stale
|
| /netbsd-src/external/bsd/ipf/dist/ |
| H A D | README | 6 The idea behind this package is allow those who use Unix workstations as
34 is debateable, but the idea behind this package is to be able to
|
| /netbsd-src/external/apache2/llvm/dist/llvm/utils/gn/secondary/llvm/unittests/ |
| H A D | BUILD.gn | 56 # setup leaves behind stale executables.
|
| /netbsd-src/external/mit/isl/dist/doc/ |
| H A D | reading.tex | 1 \textcite{Verdoolaege2016tutorial} describes the concepts behind
|
| /netbsd-src/share/man/tools/ |
| H A D | ignore | 158 behind
159 behind.
|
| /netbsd-src/sys/external/gpl2/dts/dist/arch/arm/boot/dts/ |
| H A D | at91-ariag25.dts | 77 /* TWD2+TCLK2 hidden behind ethernet, so no i2c2 */
|
| /netbsd-src/crypto/external/bsd/openssl.old/dist/ssl/statem/ |
| H A D | README | 4 This file provides some guidance on the thinking behind the design of the
|