From owner-freebsd-pf@freebsd.org  Tue Jun  6 04:30:12 2017
Return-Path: <owner-freebsd-pf@freebsd.org>
Delivered-To: freebsd-pf@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFC2DBF09E6
 for <freebsd-pf@mailman.ysv.freebsd.org>; Tue,  6 Jun 2017 04:30:12 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9E6B37CA77
 for <freebsd-pf@FreeBSD.org>; Tue,  6 Jun 2017 04:30:12 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v564UCZ0063151
 for <freebsd-pf@FreeBSD.org>; Tue, 6 Jun 2017 04:30:12 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
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)
Date: Tue, 06 Jun 2017 04:30:12 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: damjan.jov@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-pf@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-pf@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Technical discussion and general questions about packet filter
 \(pf\)" <freebsd-pf.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-pf>,
 <mailto:freebsd-pf-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-pf/>
List-Post: <mailto:freebsd-pf@freebsd.org>
List-Help: <mailto:freebsd-pf-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-pf>,
 <mailto:freebsd-pf-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jun 2017 04:30:12 -0000

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.=