From owner-freebsd-net@freebsd.org Mon Mar 20 18:41:32 2017 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 D2FA2D14192 for ; Mon, 20 Mar 2017 18:41:32 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 566161E55 for ; Mon, 20 Mar 2017 18:41:32 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v2KIfTGR081855; Mon, 20 Mar 2017 19:41:29 +0100 (CET) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 79868294; Mon, 20 Mar 2017 19:41:29 +0100 (CET) Message-ID: <58D02259.9010101@omnilan.de> Date: Mon, 20 Mar 2017 19:41:29 +0100 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Vincenzo Maffione CC: "freebsd-net@freebsd.org" Subject: Re: Are ./valte-ctl and ./bridge friends or competitors? References: <58CBA727.3040108@omnilan.de> <58CBBF7A.8050604@omnilan.de> <58CC26CF.5050708@omnilan.de> <58CFA606.7090306@omnilan.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Mon, 20 Mar 2017 19:41:29 +0100 (CET) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Mar 2017 18:41:32 -0000 Bezüglich Vincenzo Maffione's Nachricht vom 20.03.2017 12:50 (localtime): … >> So to summarize for newbies exploring netmap(4) world in combination >> with physical uplinks and virtual interfaces, it's important to do the >> following uplink NIC configuration (ifconfig(8)): >> -rxcsum -txcsum -rxcsum6 -txcsum6 -tso -lro promisc >> > > Exactly. This is mentioned at the very end of netmap(4): > > "netmap does not use features such as checksum offloading, TCP segmentation > offloading, encryption, VLAN encapsulation/decapsulation, etc. When using > netmap to exchange packets with the host stack, make sure to disable these > features." > > But it is probably a good idea to add these example ifconfig instructions > somewhere (man page or at least the README in the netmap repo). > > >> >> I guess vlanhwtag, vlanhwfilter and vlanhwtso don't interfere, do they? >> > > Well, I think they interfere: if you receive a tagged packet and the NIC > strips the tag and puts it in the packet descriptor, then with netmap you > will see the untagged packet, and you wouldn't have a way to see the tag. Hmm, if I connect a vlan child to VALE (once I provided crash info and someone capable fixed it), it's intentional that the tag was removed. Otoh, if I attach the parent interface to VALE, stripping isn't done yet, even if there are children defined for a specific vlan id. I see all frames tagged on the parent, at least it was so when I checked that last time, maybe 2 years ago. I'm always creating childs with vlan id 1 if I want a interface without taged frames. Hope I'm not missing something obvious again, I'm about to call it a day here. Thanks, -harry