From owner-freebsd-net@freebsd.org Mon Jan 25 21:37:17 2021 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BFF5F4F2631 for ; Mon, 25 Jan 2021 21:37:17 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.userve.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DPjrD4lnXz3NZd for ; Mon, 25 Jan 2021 21:37:16 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id 76B282383FF for ; Mon, 25 Jan 2021 21:37:14 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=uk1; t=1611610634; bh=W3mgLjMKwHzkIwFOy5QtWNxFmMuo3irJRGeZi8rih0Y=; h=From:To:Subject:Date; b=iOaHQDl0zClLptzEFZ3eh5ws8cK4g+IibgAJS+FEUK+WmzWj86wstaUoRY5h9VRw8 IczcDFRNJYPRst02rEqiLOXdhm2tma126wFTRvjLFxR/5k6YJv1hVkzWzsJsHVQodb mwOel6GD9mrV+6P/Gvi8/+DmB9BTwsMZdT/Nb1FE= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Mon, 25 Jan 2021 21:37:13 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Mon, 25 Jan 2021 21:37:12 +0000 From: Matt Churchyard To: "freebsd-net@freebsd.org" Subject: can't disable capability 0x400 on a vlan interface Thread-Topic: can't disable capability 0x400 on a vlan interface Thread-Index: AdbzYj0cvRQp8VQHTGi3nQ4/kpTsRQ== Date: Mon, 25 Jan 2021 21:37:12 +0000 Message-ID: <8103a3c1547549f5800fd2f2dbe259cd@SERVER.ad.usd-group.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] MIME-Version: 1.0 X-Rspamd-Queue-Id: 4DPjrD4lnXz3NZd X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=userve.net header.s=uk1 header.b=iOaHQDl0; dmarc=none; spf=pass (mx1.freebsd.org: domain of matt.churchyard@userve.net designates 217.196.1.22 as permitted sender) smtp.mailfrom=matt.churchyard@userve.net X-Spamd-Result: default: False [-3.50 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[217.196.1.22:from]; R_DKIM_ALLOW(-0.20)[userve.net:s=uk1]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:217.196.1.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-net@freebsd.org]; DMARC_NA(0.00)[userve.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[217.196.1.22:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[userve.net:+]; NEURAL_HAM_SHORT(-1.00)[-0.999]; TO_DN_EQ_ADDR_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:20652, ipnet:217.196.0.0/20, country:GB]; MAILMAN_DEST(0.00)[freebsd-net] X-Mailman-Approved-At: Tue, 26 Jan 2021 11:45:12 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.34 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, 25 Jan 2021 21:37:17 -0000 Hello, I've noticed the following warnings in dmesg and wondered if anyone had ins= ight on what they mean. It doesn't seem to actually be causing me an obviou= s problem but I'm not keen on random warnings that I haven't seen before an= d don't understand. core2: can't disable some capabilities on igb0.30: 0x400 core2 is a bridge interface that contains a few bhyve guest tap interfaces.= It's possible this message is triggered when adding or removing a tap inte= rface from the bridge. Igb0.30 is a vlan interface. As I'm not an active ke= rnel developer, actually finding out what capability 0x400 refers to seems = to be neigh on impossible. Regards, Matt Churchyard