From owner-freebsd-net@freebsd.org  Thu Mar  9 00:22:17 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@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 559E2D01699
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Thu,  9 Mar 2017 00:22:17 +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 45941311
 for <freebsd-net@FreeBSD.org>; Thu,  9 Mar 2017 00:22:17 +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 v290MGrG072745
 for <freebsd-net@FreeBSD.org>; Thu, 9 Mar 2017 00:22:17 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 217600] Gateway enable not working
Date: Thu, 09 Mar 2017 00:22:16 +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: 10.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: judah.levine@colorado.edu
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217600-2472-jsvaL5UsOB@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217600-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-217600-2472@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-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Mar 2017 00:22:17 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217600

--- Comment #5 from judah.levine@colorado.edu ---
I have configured the two systems to use NAT as you suggested, and that wor=
ks.
The problem is solved from my perspective, and I have no objection to closi=
ng
the ticket.=20
However, I think there is still a problem. The diagram that I mentioned
originally (section 30.2.2) supposedly does not require NAT to work. So, ei=
ther
there is a problem with the software or the documentation is not completely
correct. The discussion that discusses that diagram is found in many places=
 --
in the man pages and in many books. In none of these places is there mentio=
n of
the requirement to add NAT.

--=20
You are receiving this mail because:
You are the assignee for the bug.=