From owner-freebsd-virtualization@freebsd.org Wed Feb 15 14:19:49 2017 Return-Path: Delivered-To: freebsd-virtualization@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 B99DBCE0DFB for ; Wed, 15 Feb 2017 14:19:49 +0000 (UTC) (envelope-from carlopmart@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 46AF1F9C for ; Wed, 15 Feb 2017 14:19:49 +0000 (UTC) (envelope-from carlopmart@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id c85so43063395wmi.1 for ; Wed, 15 Feb 2017 06:19:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=7SLdfqfghytQSqGz5/dcaFHdS6JRyqWy5Cs0t32mTkk=; b=JIVkYulXTv2iClGD85BMLfHlIE2c5ZtNKvgvQMcRH62EoO6q6xrA5HHsCepsRXzAU/ TfXhB1h9rtjHaCzDHxK332Le8V6uW+q7ID5ZEPqM53LQmLpIHSiYdrTlZfEAUmF+M6Av 8G8aJ13RsguuMLsr8TEUOSh+fTCQCUKKN7iVkJMdSKRKJ/46SRtV3w8kZ/m0y900UqND +k9c+ZzD4hHYteStoZG/vQTDb3SI6cRCXuR++45AOAsbYuqIyhZXpxNfIsvupOdoa4M9 1ZDlqkSatnkL8LPREkEJbh6O1/se62gE+6/KBC1GnsNqFNFKxjFLgpUP5MJpYAtWwu/s b86w== 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:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=7SLdfqfghytQSqGz5/dcaFHdS6JRyqWy5Cs0t32mTkk=; b=MSnqTeN/rSqlAk5aWoLg4LFjBpStEUvaiYPcKA5lrryZDW4/bdTGBmeHLA2wCrMVSJ /BLVQ2cCna1NbBiwTmPwln5EX7hWa7las64Xcv73cnQiEB0ex+IIZvbKGI2laNsOWFfT qW8Mu3i/COeNwIKk9jnVA66r3fOTq+TxTkXI8P1/5CYUblk80KcuD6iUpW4Q4j2tzUKx PR/5SL6mRtgVZDdshtV/L5NeYCkX7KvqzSywVGex/Unb9tq1ChzLcerVmlajIJZSkfo7 bFscAIRMPVRlLnwpDftwLMY0/2jO0QlXPbjJ5THhu0/WbHtSnamTgBG/p4Nf71miAxfO WH7Q== X-Gm-Message-State: AMke39nwaph9AAWHrefjLgtq3LzqUgGCq8JOM+pr0HUtTsk40qEtoERPwxo0ebyQrk1g7w== X-Received: by 10.28.0.73 with SMTP id 70mr7890820wma.109.1487168387010; Wed, 15 Feb 2017 06:19:47 -0800 (PST) Received: from localhost (231.red-79-150-68.dynamicip.rima-tde.net. [79.150.68.231]) by smtp.gmail.com with ESMTPSA id 40sm5090334wry.22.2017.02.15.06.19.46 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Feb 2017 06:19:46 -0800 (PST) Date: Wed, 15 Feb 2017 14:19:55 +0000 From: "C. L. Martinez" To: freebsd-virtualization@freebsd.org Subject: Re: tap interfaces disappears after bhyve guests shutdowns (SOLVED) Message-ID: <20170215141955.uw6jakbfjro7ytuz@scotland.uxdom.org> References: <20170213120938.hr3zu7flnm33v3zn@scotland.uxdom.org> <58A1A8A3.3030603@quip.cz> <8700dd14-cf15-20b9-38a6-e4181e4928ee@dann.ro> <20170214115708.pcw2poookycue3kk@scotland.uxdom.org> <58A2F845.5090603@quip.cz> <20170214132649.h3xwbcfrtjxk74si@scotland.uxdom.org> <20170214134158.vmczv6pramkscxhd@scotland.uxdom.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2017 14:19:49 -0000 On Tue, Feb 14, 2017 at 11:03:22PM -0800, Stephen Stuart wrote: > On Feb 14, 2017 05:42, "C. L. Martinez" wrote: > > On Tue, Feb 14, 2017 at 01:26:49PM +0000, C. L. Martinez wrote: > > On Tue, Feb 14, 2017 at 01:29:57PM +0100, Miroslav Lachman wrote: > > > C. L. Martinez wrote on 2017/02/14 12:57: > > > > On Mon, Feb 13, 2017 at 02:02:48PM +0100, Daniel Niculescu wrote: > > > > > > > > > > > Thanks Daniel. I have tried what you say, but ping doesn't works > between host and guest. If I put an ip to the bridge works ok, but not when > I assign an ip to tap interface. > > > > > > > > Any idea why?? > > > > > > Are you using IPs from the same subnet on host and in a guests? What IP > did > > > you assign to tap / bridge? > > > > > > Miroslav Lachman > > > > Yes. For host: 172.22.55.1/24 and for guest 172.22.55.29/24. When I > assign IP 172.22.55.1 to the bridge on host side, host and guest can > communicate. But when I assign 172.22.55.1 to a tap interface on the host > and create a bridge with host's tap interface and guest's tap interface, > there is no comms between them ... And I don't understand why ... > > > > > > -- > > Greetings, > > C. L. Martinez > > Ok, I think I have found the problem (but not the solution :( ) ... > > prodif: flags=8843 metric 0 mtu 1500 > ether 02:bc:f9:66:98:01 > nd6 options=9 > groups: bridge > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap11 flags=143 > ifmaxaddr 0 port 7 priority 128 path cost 2000000 > member: tap10 flags=143 > ifmaxaddr 0 port 6 priority 128 path cost 2000000 > pubif: flags=8843 metric 0 mtu 1500 > ether 02:bc:f9:66:98:02 > nd6 options=9 > groups: bridge > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap21 flags=143 > ifmaxaddr 0 port 9 priority 128 path cost 2000000 > member: tap20 flags=143 > ifmaxaddr 0 port 8 priority 128 path cost 2000000 > tap10: flags=8943 metric 0 > mtu 1500 > options=80000 > ether 00:bd:1d:15:f7:0a > nd6 options=29 > media: Ethernet autoselect > status: active > groups: tap > Opened by PID 79946 > tap11: flags=8943 metric 0 > mtu 1500 > options=80000 > ether 00:bd:24:15:f7:0b > inet 172.22.55.1 netmask 0xffffffe0 broadcast 172.22.55.31 > nd6 options=29 > media: Ethernet autoselect > status: no carrier > groups: tap > tap20: flags=8943 metric 0 > mtu 1500 > options=80000 > ether 00:bd:2b:15:f7:14 > nd6 options=29 > media: Ethernet autoselect > status: active > groups: tap > Opened by PID 79946 > tap21: flags=8943 metric 0 > mtu 1500 > options=80000 > ether 00:bd:31:15:f7:15 > inet 172.30.77.1 netmask 0xfffffff8 broadcast 172.30.77.7 > nd6 options=29 > media: Ethernet autoselect > status: no carrier > groups: tap > > .. As you can see with tap21 and tap11 (tap interfaces assigned to host) > status is: no carrier ... ¿¿¿¿¿???? Why?? Both are assigned to bridges ... > > > Those tap interfaces have no carrier because they have not been opened by a > guest VM and paired with a vtnet interface. > > A tap interface is how the vtnet interface inside the guest VM shows up on > the host side. No guest VM, no tap. > > If you want the host to be able to exchange IP packets with the guest VM > locally, the bridge (on the host) and vtnet interface (in the guest VM) > need to be numbered in the same prefix. The tap interfaces don't get IP > address assignments, the corresponding vtnet interfaces inside the VMs do. > Ok, I have solved the problem. I am using source policy routing in this installation, because I need to route Internet traffic via wlan0 interface. Due to the impossibility to bridge wlan interface, I have created two routing tables. Adding default route to rtable 1, solved the problem. Many thanks to all for your help. -- Greetings, C. L. Martinez