From owner-freebsd-net@freebsd.org Sat Sep 1 21:11:27 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFA26FFAE75 for ; Sat, 1 Sep 2018 21:11:27 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5FD977BC8A for ; Sat, 1 Sep 2018 21:11:27 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: by mailman.ysv.freebsd.org (Postfix) id 24747FFAE6F; Sat, 1 Sep 2018 21:11:27 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 132BAFFAE6E for ; Sat, 1 Sep 2018 21:11:27 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A8D77BC85 for ; Sat, 1 Sep 2018 21:11:26 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w81LBOfk009509 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 1 Sep 2018 14:11:24 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w81LBNUH009507; Sat, 1 Sep 2018 14:11:23 -0700 (PDT) (envelope-from jmg) Date: Sat, 1 Sep 2018 14:11:23 -0700 From: John-Mark Gurney To: Vincenzo Maffione Cc: "freebsd-net@freebsd.org" , Luigi Rizzo Subject: Re: vale and netmap module questions Message-ID: <20180901211123.GZ45503@funkthat.com> Mail-Followup-To: Vincenzo Maffione , "freebsd-net@freebsd.org" , Luigi Rizzo References: <20180901014953.GV45503@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Sat, 01 Sep 2018 14:11:24 -0700 (PDT) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2018 21:11:28 -0000 Vincenzo Maffione wrote this message on Sat, Sep 01, 2018 at 22:25 +0200: > Il giorno sab 1 set 2018 alle ore 03:50 John-Mark Gurney > ha scritto: > > > First, does vale work for anyone? At least one of the documented > > commands in vale(4) does not work. > > > > After manually building the netmap module and loading it: > > # tcpdump -ni vale-a:1 > > 313.748851 nm_open [947] invalid bridge name vale-a:1 > > tcpdump: netmap open: cannot access vale-a:1: Invalid argument > > That name is invalid. See netmap(4). Are there plans to update the documentation then? It seems like vale(4) should be a more authoratative reference for vale's naming than netmap(4)... > > If I run tcpdump with a more correct looking name of vale1:a, I get a > > null deref panic in ifunit_ref. Full trace is at the end. > > Yes, this is a known bug, already posted to this mailing list. Don't build > netmap as a module, but link it in the kernel image and it will work. > (Add "dev netmap" to the kernel config). > > > Second, is there a good reason why the netmap module is still > > disconnected from being built as a module? I guess not working > > would be one, but I figure the above might be an aarch64 specific > > problem, and not a general issue. > > On x86_64 netmap is not built as a module, so everything works fine. I > don't see any reason why it should be a module in aarch64. Well, sys/modules/netmap exists... If it isn't planned on ever being made to work, it should be removed so people don't get confused, or at least marked broken so it doesn't get built... I built it manually because it was quicker than recompiling an entire kernel and rebooting... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."