From owner-freebsd-net@freebsd.org Sun May 15 23:41:52 2016 Return-Path: Delivered-To: freebsd-net@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 A6892B3CA51 for ; Sun, 15 May 2016 23:41:52 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (vm1982.vellance.net [79.99.184.240]) (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 45E861704 for ; Sun, 15 May 2016 23:41:51 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id 707FF301CC for ; Mon, 16 May 2016 01:41:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1463355702; bh=2zG9ZBnwWypWIknojwyx8/CjpcQFtqB3lrv3UJ6fxLc=; h=Subject:To:References:From:Date:In-Reply-To; b=AleBT/dT8YM0OF30fuV9Ipn2XlspvtMncpoPnUm54eQ0MsXkH+2b6SlgOUroyY+dy IduPhPZN3XZIWub6zJm88mNwB8BmdfhxKg9I31yJ/IX3QYjElWAyGPdqBDBfn8vXZd C5Qo53/EGnCnAZ9piFbywQQeSTKBm3Q1BqY+vrbOPTPbu8EI8VmfKUw6otWXncxfaT b1Lwmqh7y4W/mlv/zRG/flSQjB1Bv4q3iMWtaa97WePvHwl/iQKP6HjLQqOCccun0I ufJItlFMjYyfhzQDYXZIKKd8Ct+gf9SfiJ3QRG+SrGHbWzbsYDvvgppNHIorNBaAM4 fa77eMhnIswve43tdfxTwZwzenm3Sc2cdDjzzXeDs2FkBcDMXKDoinKogLuVv8wNyk zwnyKx9eY4BJqcbQnoP4vdpfiJMdt0yGnC1roGbKzxYeQT5S4ZUbhGJB2FPc/SmfvY lJqCiHpg+Ig2jXCiy1Fz4seK4xKRGNdmZQI0QN4OH6QgTqgnJjco8kTasa847BEZof zP+ukS5DKHxQmO8G90W7xsPnx/+2lf0d1LxfAetzLLBn/1QcB9UYmh3OJNQCUdnjUk fDUCK/L5kbLK7QilpB5bQKSa8PKa2JEp4e58QHKSeXqk3p09VnV+n39sCywbdWAZv5 YIkoW7TIapJwM9xSOcYqiydA= Received: from rubens-MacBook-Air.local (ip4da7bddc.direct-adsl.nl [77.167.189.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vm1982.vellance.net (Postfix) with ESMTPSA id F0DA2301BE for ; Mon, 16 May 2016 01:41:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1463355702; bh=2zG9ZBnwWypWIknojwyx8/CjpcQFtqB3lrv3UJ6fxLc=; h=Subject:To:References:From:Date:In-Reply-To; b=AleBT/dT8YM0OF30fuV9Ipn2XlspvtMncpoPnUm54eQ0MsXkH+2b6SlgOUroyY+dy IduPhPZN3XZIWub6zJm88mNwB8BmdfhxKg9I31yJ/IX3QYjElWAyGPdqBDBfn8vXZd C5Qo53/EGnCnAZ9piFbywQQeSTKBm3Q1BqY+vrbOPTPbu8EI8VmfKUw6otWXncxfaT b1Lwmqh7y4W/mlv/zRG/flSQjB1Bv4q3iMWtaa97WePvHwl/iQKP6HjLQqOCccun0I ufJItlFMjYyfhzQDYXZIKKd8Ct+gf9SfiJ3QRG+SrGHbWzbsYDvvgppNHIorNBaAM4 fa77eMhnIswve43tdfxTwZwzenm3Sc2cdDjzzXeDs2FkBcDMXKDoinKogLuVv8wNyk zwnyKx9eY4BJqcbQnoP4vdpfiJMdt0yGnC1roGbKzxYeQT5S4ZUbhGJB2FPc/SmfvY lJqCiHpg+Ig2jXCiy1Fz4seK4xKRGNdmZQI0QN4OH6QgTqgnJjco8kTasa847BEZof zP+ukS5DKHxQmO8G90W7xsPnx/+2lf0d1LxfAetzLLBn/1QcB9UYmh3OJNQCUdnjUk fDUCK/L5kbLK7QilpB5bQKSa8PKa2JEp4e58QHKSeXqk3p09VnV+n39sCywbdWAZv5 YIkoW7TIapJwM9xSOcYqiydA= Subject: Re: bhyve with vlans - host and vm can't pass traffic To: freebsd-net@freebsd.org References: <553A8DF0.2060901@sds.com> <9c759cf4-01f0-6f21-c18a-27b3d491dcbf@osfux.nl> From: Ruben Message-ID: <8fae9862-90e5-9098-d30c-a2f0a4b01aa1@osfux.nl> Date: Mon, 16 May 2016 01:41:40 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <9c759cf4-01f0-6f21-c18a-27b3d491dcbf@osfux.nl> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 May 2016 23:41:52 -0000 Hi Scott, It turns out that my predicament (incorrect _tcp_ connectivity between guest and host, but correct tcp connectivity between guest and rest of network) was probably being caused by a combination of both using the lagg driver, the intel em driver, and probably vlan traffic (an old post (finally) pointed me towards a solution : https://forums.freebsd.org/threads/7668 ). tcpdump -vvv on the related tap / vtnet interfacs showed a lot of checksum errors specifically related to tcp traffic (icmp was fine) and after disabling tso4, lro and hardware vlan tagging for both the lagg and the nics making up the lagg interface, my ordeal was over. I just added these directives to the server's specific rc.conf ifconfig_ lines : -vlanhwtag -lro -tso eg: ifconfig_em0="up media 1000baseTX mediaopt full-duplex -tso4 -lro -vlanhwtag" ifconfig_lagg0="laggproto lacp laggport em0 -tso4 -lro -vlanhwtag" And (after a reboot) everything started working like a charm. So: my problem was not bhyve related, but rather to the networking stack / specific drivers (and my "combination" of using them ofc). Kind regards / sorry for polluting this bhyve thread, Ruben On 13/05/16 02:37, Ruben wrote: > Hi Scott, > > Since I'm currently facing a somewhat similar problem (to the best of my > understanding): where you ever able to solve this? I'd be more than > happy to hear of any solution for the predicament you were in :P > > Kind regards, > > Ruben