Date: Tue, 06 Jun 2017 04:30:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-pf@FreeBSD.org Subject: [Bug 219803] [patch] PF: implement RFC 4787 REQ 1 and 3 (full cone NAT) Message-ID: <bug-219803-17777-dC4lGfKh8A@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219803-17777@https.bugs.freebsd.org/bugzilla/> References: <bug-219803-17777@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219803 --- Comment #2 from Damjan Jovanovic <damjan.jov@gmail.com> --- In its current state, the patch provides application with a NAT hole punchi= ng capability. Unlike in a symmetric NAT, in any cone-type NAT, an internal UDP application can negotiate to receive packets from a known peer, by using ST= UN to create a external IP:port for its UDP socket and discover what they are, communicating them to its peer and learning what external IP:port its peer = is using, and even if it's behind the most restrictive "ported-restricted cone" NAT, it can just send 1 packet to its peer's IP:port to create a connection= and allow that peer to send packets back. This works even if both peers are NATed, as long as at least 1 (the server)= is not a symmetric NAT. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219803-17777-dC4lGfKh8A>