From owner-freebsd-jail@freebsd.org Mon Jul 24 17:05:04 2017 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 A733DCFEB33 for ; Mon, 24 Jul 2017 17:05:04 +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 95D3A6FB07 for ; Mon, 24 Jul 2017 17:05:04 +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 v6OH53jA059358 for ; Mon, 24 Jul 2017 17:05:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 213896] when starting vimage jails the kernel crashes Date: Mon, 24 Jul 2017 17:05:04 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: stefan@gronke.net X-Bugzilla-Status: New 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.23 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2017 17:05:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213896 --- Comment #10 from gronke --- I used a similar script to reproduce the bug and noticed it only occurs when the host's epair nic went up before destroying the jail. This snippet manually attaches the nic to the jail after it was started and takes "yes" as first argument to change the host's nic state. $ ./crash-demo.sh no ... > done $ ./crash-demo.sh yes > crash -- #!/bin/sh UPDOWNIF=3D"$1" BRIDGE_IF=3Dbridge1 ifconfig $BRIDGE_IF create set -x for i in $(seq 0 200); do #jail -c vnet persist path=3D$RELEASE_FOLDER name=3Djail-vnet jail -c vnet persist name=3Djail-vnet epair_a=3D"$(ifconfig epair create)" epair_b=3D"$(echo $epair_a | rev | cut -c2- | rev)b" mac_a=3D$(openssl rand -hex 6 | sed 's/\(..\)/\1:/g; s/.$//') ifconfig $epair_a name a-$i ifconfig a-$i ether "$mac_a" if [ "$UPDOWNIF" =3D=3D "yes" ]; then ifconfig a-$i up fi ifconfig $BRIDGE_IF addm a-$i ifconfig $epair_b vnet jail-vnet jexec jail-vnet /sbin/ifconfig $epair_b name vnet0 jexec jail-vnet /sbin/ifconfig vnet0 up jexec jail-vnet /sbin/ifconfig jail -r jail-vnet if [ "$UPDOWNIF" =3D=3D "yes" ]; then ifconfig a-$i down fi ifconfig $BRIDGE_IF deletem a-$i ifconfig a-$i destroy done echo "done" --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-jail@freebsd.org Mon Jul 24 21:23:45 2017 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 4C84CDA4536 for ; Mon, 24 Jul 2017 21:23:45 +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 3ABD77D090 for ; Mon, 24 Jul 2017 21:23:45 +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 v6OLNi5a001359 for ; Mon, 24 Jul 2017 21:23:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 213896] when starting vimage jails the kernel crashes Date: Mon, 24 Jul 2017 21:23:45 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: heinz@project-fifo.net X-Bugzilla-Status: New 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.23 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2017 21:23:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213896 --- Comment #11 from Heinz N. Gies --- Given how easy this is to reproduce and we've 3 people in here now any chan= ce to change the importance from 'affects only me' to 'affects some people'? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-jail@freebsd.org Mon Jul 24 21:30:56 2017 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 A9DABDA4AE7 for ; Mon, 24 Jul 2017 21:30:56 +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 9857A7D4E6 for ; Mon, 24 Jul 2017 21:30:56 +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 v6OLUumT014198 for ; Mon, 24 Jul 2017 21:30:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 213896] when starting vimage jails the kernel crashes Date: Mon, 24 Jul 2017 21:30:56 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-jail@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_severity 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.23 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2017 21:30:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213896 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Affects Only Me |Affects Some People --- Comment #12 from Mark Linimon --- Flip the "affects some people" switch. IIUC FreeBSD really doesn't pay much attention to that field; it's a default field in Bugzilla. e.g. there's no formal triage procedure. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-jail@freebsd.org Tue Jul 25 06:23:38 2017 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 62368DB786E for ; Tue, 25 Jul 2017 06:23:38 +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 505F16A11F for ; Tue, 25 Jul 2017 06:23:38 +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 v6P6Nbet029059 for ; Tue, 25 Jul 2017 06:23:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 213896] when starting vimage jails the kernel crashes Date: Tue, 25 Jul 2017 06:23:38 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nospam@ofloo.net X-Bugzilla-Status: New 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.23 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2017 06:23:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213896 --- Comment #13 from Ofloo --- I'm not sure if this is the cause, but I can't upgrade 2 other machines wit= h 10 jails because of it. So to me it is important as well. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-jail@freebsd.org Tue Jul 25 06:26:39 2017 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 58DA9DB793B for ; Tue, 25 Jul 2017 06:26:39 +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 473156A19D for ; Tue, 25 Jul 2017 06:26:39 +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 v6P6QdIM033116 for ; Tue, 25 Jul 2017 06:26:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 213896] when starting vimage jails the kernel crashes Date: Tue, 25 Jul 2017 06:26:39 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nospam@ofloo.net X-Bugzilla-Status: New 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.23 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2017 06:26:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213896 --- Comment #14 from Ofloo --- I should of payed more attention to what was said never mind. Disregard that last comment. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-jail@freebsd.org Wed Jul 26 14:08:21 2017 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 08EA7DBEB35 for ; Wed, 26 Jul 2017 14:08:21 +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 EB1E263AE2 for ; Wed, 26 Jul 2017 14:08:20 +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 v6QE8K7a032501 for ; Wed, 26 Jul 2017 14:08:20 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 213896] when starting vimage jails the kernel crashes Date: Wed, 26 Jul 2017 14:08:20 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: stefan@gronke.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-jail@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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.23 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2017 14:08:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213896 --- Comment #15 from gronke --- Created attachment 184726 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D184726&action= =3Dedit core.0.txt on a VM with HyperThreading disabled on the host The core.0.txt after crashing the system on a 11.0-RELEASE-p11 with VIMAGE enabled. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-jail@freebsd.org Thu Jul 27 18:05:47 2017 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 604B6DAC91B for ; Thu, 27 Jul 2017 18:05:47 +0000 (UTC) (envelope-from marcel.plouf@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7342223 for ; Thu, 27 Jul 2017 18:05:46 +0000 (UTC) (envelope-from marcel.plouf@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id 184so24661890wmo.3 for ; Thu, 27 Jul 2017 11:05:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=gYUXfALpBNiMT1bJW3G0eIs0aEZ/qujUxSoxU23PUQE=; b=iTzsI+weac2LAZEQ69/Q8nr2PU2t0Ygqw2gT7NsYgknjl0/GnYSKRNyH4AGjeRwVro qxzDp2soc2Y/Ia5BLXZYFOx/q0KKpolw4M1USdpdmgFSVS4IFcyUhA/kH2gXEr9Coqip D4Q7Nut7B4rMcINZWknrCt+CZQ707UtP1RSObklZYOZ4zCK7pZrSi2oltSA/C+6mtHGL A+SE7fkG9kv8rEnOEmIor0vU1mo0JY6g/JYzvOvP/keHU9UxIRq/YSxdgXfzX7P+S3B3 UTeS37KG4OlTqxrKO5F8V3sCUwUzmv02CV7D+zY2r+2Mu5AdrnMB06bvXNNg9BhbNlgc nDtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=gYUXfALpBNiMT1bJW3G0eIs0aEZ/qujUxSoxU23PUQE=; b=IXy5ZwMSoCsj66NujSFoG4vhk50VM/3gvGy/yA3vHXTsjXDnVJ+MSNhi53UgLPhfp0 DW1gsMBa3imMgRhTNezuhPkR2QPNVx0Y6E9AAtR9C4Fo0KrX+B4lQlq5CqEpn6M43w4u tXmhwMh/rFjoG31GSAOMPjnJUSmXHY7HsmvZSKciVlDLMVL1TYMTBSUxu/C8+Ulvkb2l 9OBg92+K/Ny2B0f7uWMVie/3dPrRjzUXIEdD54RCWGDsoygX1dkZIXHYDvQEMCwPAFAI u2VL5NMoiEGDgw0lUyAx9NijzJICDQCRrZFoH7Um5AGT4OegpG6NlI2rT7FL9HgbZdTC HSyg== X-Gm-Message-State: AIVw110gHW3I/xv7uwFVcgZinm6oO40iHQun4RdPq2XPHPAAA8xTxE+x QGACOusYF+Z2cCcm X-Received: by 10.28.129.70 with SMTP id c67mr3978939wmd.175.1501178745319; Thu, 27 Jul 2017 11:05:45 -0700 (PDT) Received: from marcel-laptop.lan (212-198-10-164.rev.numericable.fr. [212.198.10.164]) by smtp.gmail.com with ESMTPSA id 16sm12265338wrx.26.2017.07.27.11.05.44 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 27 Jul 2017 11:05:45 -0700 (PDT) Date: Thu, 27 Jul 2017 20:05:40 +0200 From: marcel To: freebsd-jail@freebsd.org Subject: Trying to set up VLANs with jail Message-ID: <20170727200540.7e159499@marcel-laptop.lan> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-unknown-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2017 18:05:47 -0000 Hi, I try to set up VLANs following the howto of Shawn Debnath http://shawndebnath.com/articles/2016/03/27/freebsd-jails-with-vlan-howto.html Actually, I want to isolate each jails from the other so I thought assign a VLAN ID to each jail was a good solution. So, I correctly followed the howto of Shawn but my host can't no more communicate with anything, when I try to ping 8.8.8.8, it says "sendto: no route to host" while my netstat -r output is exactly the same as in the howto. re0 is up and vlan0 has 192.168.2.6 ip, like in the howto and my firewall is down. So I decided to assign to re0 the ip 192.168.2.6 and to vlan0 192.168.2.7 and my host is now available remotely (with my ipfw rules this time) and can ping 8.8.8.8 (but still doesn't resolve domain name...) but I don't know if vlan work and I don't know how I can verify it. I noticed thaht when I do ifconfig destroy vlan0, my host can resolv domain name... I am a little bit lost, can anyone give me some help or explanation please ? Thanks, marcel