From owner-freebsd-jail@freebsd.org Sun May 29 00:30:46 2016 Return-Path: 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 6C55FB45673 for ; Sun, 29 May 2016 00:30:46 +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 5D14E1779 for ; Sun, 29 May 2016 00:30:46 +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 u4T0UkSF028696 for ; Sun, 29 May 2016 00:30:46 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:30:46 +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: jamie@FreeBSD.org 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: Message-ID: In-Reply-To: References: 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\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 00:30:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208001 --- Comment #5 from Jamie Gritton --- Yes, of course there are cases where something besides a /32 is appropriate= - that is why jail(8) allows that. However, as I mentioned it did appear that you had violated the specification that an alias should be on a non-conflic= ting netmask. The fact remains that I am unable to reproduce your problem. Perhaps I cou= ld if I had your entire configuration - all jails, all other network setup. jail(8) simply calls ifconfig(8) with "alias" to add IP addresses, and with "-alias" to remove them - see the output of "jail -vc" and "jail -vr". The jail will not be removed if the "ifconfig ... -alias" command fails, which implies that the command is succeeding. Unless of course there actually is= a bug in the way jail(8) is running this program. My guess is the command is succeeding, but isn't removing some arp entry because the alias when incorrectly specified when it was created. If it's clear (from "jail -v") that the correct ifconfig commands are being run, then this might be considered an ifconfig bug. If the correct commands aren't being run, then it could be a jail bug. --=20 You are receiving this mail because: You are the assignee for the bug.=