From owner-freebsd-jail@freebsd.org  Sun May 29 00:16:24 2016
Return-Path: <owner-freebsd-jail@freebsd.org>
Delivered-To: freebsd-jail@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 D1067B450C1
 for <freebsd-jail@mailman.ysv.freebsd.org>;
 Sun, 29 May 2016 00:16:24 +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 C19411C8F
 for <freebsd-jail@FreeBSD.org>; Sun, 29 May 2016 00:16:24 +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 u4T0GOm7096403
 for <freebsd-jail@FreeBSD.org>; Sun, 29 May 2016 00:16:24 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-jail@FreeBSD.org
Subject: [Bug 208001] After turning off the jail does not remove network routes
Date: Sun, 29 May 2016 00:16:24 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.3-BETA2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: admin@support.od.ua
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-jail@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-208001-9824-VOLRfoHVyd@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-208001-9824@https.bugs.freebsd.org/bugzilla/>
References: <bug-208001-9824@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-jail@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion about FreeBSD jail\(8\)" <freebsd-jail.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-jail>,
 <mailto:freebsd-jail-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-jail/>
List-Post: <mailto:freebsd-jail@freebsd.org>
List-Help: <mailto:freebsd-jail-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-jail>,
 <mailto:freebsd-jail-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 29 May 2016 00:16:24 -0000

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

Vladislav V. Prodan <admin@support.od.ua> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Closed                      |Open
         Resolution|Works As Intended           |---

--- Comment #4 from Vladislav V. Prodan <admin@support.od.ua> ---
The problem is not the creation of an IP address, network mask, other than =
/32.
I can give some examples of network topology, when the IP jail need to assi=
gn a
subnet mask for the correct operation of the network protocols. For example=
, a
DHCP-server or Samba services (nmbd and winbindd)
The problem is in the removal of a route to this IP when you turn off the j=
ail.

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