From owner-freebsd-net@FreeBSD.ORG Wed Apr 22 16:22:59 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A5DFC6CE for ; Wed, 22 Apr 2015 16:22:59 +0000 (UTC) Received: from bin.sds.com (bin.sds.com [198.133.242.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bin.sds.com", Issuer "bin.sds.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 88FDD1569 for ; Wed, 22 Apr 2015 16:22:59 +0000 (UTC) Received: from dhcp-assigned205.sds.com (dhcp-assigned205.sds.com [10.0.1.205] (may be forged)) (authenticated bits=0) by bin.sds.com (8.15.1/8.14.7) with ESMTPSA id t3MG20QJ013567 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 22 Apr 2015 09:02:01 -0700 (PDT) (envelope-from scotto@sds.com) Message-ID: <5537C5F8.1090000@sds.com> Date: Wed, 22 Apr 2015 09:02:00 -0700 From: "Scott O'Connell" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: bhyve with vlans - host and vm can't pass traffic X-Virus-Scanned: clamav-milter 0.98.6 at bin.sds.com X-Virus-Status: Clean Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2015 16:22:59 -0000 I'm very new to bhyve and am having an issue. I'm trying to get VM's and VLAN's working. I'm able to get VLAN's working in a VM, but the VM and the VMHOST, can't communicate with each other on the same vlan. Using 10.1-RELEASE-p9 for both VMHOST01 and DEV. Upstream from the VMHOST on lagg0 is a Cisco 3750G. VMHOST01 before starting VM: bge0: flags=8843 metric 0 mtu 1500 options=c019b ether f0:1f:af:dd:2e:c5 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active bge1: flags=8843 metric 0 mtu 1500 options=c019b ether f0:1f:af:dd:2e:c5 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 lagg0: flags=8843 metric 0 mtu 1500 options=c019b ether f0:1f:af:dd:2e:c5 nd6 options=29 media: Ethernet autoselect status: active laggproto lacp lagghash l2,l3,l4 laggport: bge1 flags=1c laggport: bge0 flags=1c vlan100: flags=8843 metric 0 mtu 1500 options=103 ether f0:1f:af:dd:2e:c5 inet 10.0.1.17 netmask 0xffffff00 broadcast 10.0.1.255 nd6 options=29 media: Ethernet autoselect status: active vlan: 100 parent interface: lagg0 VMHOST after starting VM (added tap0 & bridge0): tap0: flags=8902 metric 0 mtu 1500 options=80000 ether 00:bd:70:71:1d:00 nd6 options=29 media: Ethernet autoselect status: no carrier bridge0: flags=8843 metric 0 mtu 1500 ether 02:d3:e4:02:03:00 nd6 options=1 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: tap0 flags=143 ifmaxaddr 0 port 6 priority 128 path cost 2000000 member: lagg0 flags=143 ifmaxaddr 0 port 4 priority 128 path cost 10000 Note that the "status: no carrier" is because I hadn't brought up the VM yet. It properly changes to the following after the VM is started: tap0: flags=8943 metric 0 mtu 1500 options=80000 ether 00:bd:70:71:1d:00 nd6 options=29 media: Ethernet autoselect status: active Opened by PID 70827 VM: vtnet0: flags=8943 metric 0 mtu 1500 options=80028 ether 00:a0:98:2b:34:37 nd6 options=29 media: Ethernet 10Gbase-T status: active lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 vlan100: flags=8843 metric 0 mtu 1500 ether 00:a0:98:2b:34:37 inet 10.0.1.6 netmask 0xffffff00 broadcast 10.0.1.255 nd6 options=29 media: Ethernet 10Gbase-T status: active vlan: 100 parent interface: vtnet0 With this configuration, both VMHOST01 and DEV can communicate anywhere, EXCEPT to each other using their IP on VLAN100. The ultimate goal is to have more than one VLAN presented to the VM, whether it exists on the VMHOST or not. Where did I go wrong? Thanks in advance, scotto