…w not to work before you've even added the masquerade rule? Because my LAN uses RFC1918 IPs, which are not routable over the internet. You cannot connect to 10.0.0.2 on my LAN. Similarly, without the masquerade/snat rule the router passes an outgoing packet with source IP 10.0.0.…

…he WKP, such as forbidding its use in combination with private IPv4 addresses [ RFC1918 ]. These restrictions might conflict with the operator's desired use of an IPv4/IPv6 translation mechanism. In summary, there is a need for a local-use prefix that facilitates the coexistence …

…ain names [ RFC2606 ]. Documentation also makes use of the ranges reserved in [ RFC1918 ]. 2 . Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as de…

… as a result of historical hijackings of IPv4 addresses that are not RFC 1918 [ RFC1918 ] for private use. The whole need for the proposed allocation grows from the desire to be able to use ORCHIDs with existing applications and APIs. This desire leads to the potential conflict, …

…he WKP, such as forbidding its use in combination with private IPv4 addresses [ RFC1918 ]. These restrictions might conflict with the operator's desired use of an IPv4/IPv6 translation mechanism. In summary, there is a need for a local-use prefix that facilitates the coexistence …

…¶ In a typical configuration, a TURN client is connected to a private network [ RFC1918 ] and, through one or more NATs, to the public Internet. On the public Internet is a TURN server. Elsewhere in the Internet are one or more peers with which the TURN client wishes to communica…

…v6 site local addresses is in many ways similar to the management of RFC 1918 [ RFC1918 ] addresses in some IPv4 networks. In theory, the private addresses defined in RFC 1918 should only be used locally, and should never appear in the Internet. In practice, these addresses "leak…

… as a result of historical hijackings of IPv4 addresses that are not RFC 1918 [ RFC1918 ] for private use. The whole need for the proposed allocation grows from the desire to be able to use ORCHIDs with existing applications and APIs. This desire leads to the potential conflict, …

…I 10.17487/RFC8445 , July 2018 , < https://www.rfc-editor.org/info/rfc8445 > . [RFC1918] Rekhter, Y. , Moskowitz, B. , Karrenberg, D. , de Groot, G. J. , and E. Lear , "Address Allocation for Private Internets" , BCP 5 , RFC 1918 , DOI 10.17487/RFC1918 , February 1996 , < https:/…

…. In a typical configuration, a TURN client is connected to a private network [ RFC1918 ] and through one or more NATs to the public Internet. On the public Internet is a TURN server. Elsewhere in the Internet are one or more peers with which the TURN client wishes to communicate…

…v6 site local addresses is in many ways similar to the management of RFC 1918 [ RFC1918 ] addresses in some IPv4 networks. In theory, the private addresses defined in RFC 1918 should only be used locally, and should never appear in the Internet. In practice, these addresses "leak…

…lar to what has happened as a result of historical hijackings of non-RFC 1918 [ RFC1918 ] IPv4 addresses for private use. The whole need for the proposed allocation grows from the desire to be able to use ORCHIDs with existing applications and APIs. This desire leads to the poten…

… The reason for this is that otherwise the tracker would give out the internal (RFC1918) address of the client, which is not routable. Therefore the client must explicitly state its (external, routable) IP address to be given out to external peers. Various trackers treat this par…

…lar to what has happened as a result of historical hijackings of non-RFC 1918 [ RFC1918 ] IPv4 addresses for private use. The whole need for the proposed allocation grows from the desire to be able to use ORCHIDs with existing applications and APIs. This desire leads to the poten…

…I 10.17487/RFC8445 , July 2018 , < https://www.rfc-editor.org/info/rfc8445 > . [RFC1918] Rekhter, Y. , Moskowitz, B. , Karrenberg, D. , de Groot, G. J. , and E. Lear , "Address Allocation for Private Internets" , BCP 5 , RFC 1918 , DOI 10.17487/RFC1918 , February 1996 , < https:/…