From nobody Thu Aug 28 14:18:52 2025 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cCNmt1HLhz665ST for ; Thu, 28 Aug 2025 14:18:54 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cCNms6Wg2z3y52; Thu, 28 Aug 2025 14:18:53 +0000 (UTC) (envelope-from jhb@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1756390733; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Nb/g8QUR8bWFtUGpB8I4C+fbjwmYZD8XtLWSXC/p/Bk=; b=p6kqXfPc22C1m+ajfRnnSWITcmjk/htXxUn3m/YMD/y+O34IsxBdo9xnfR9u6e1blVjIj3 9MkRGUJA+zynVlZE32rywBnvm3tgJq924IgD5Jgfpq8Dy/N6zMcyVjfHfdo3vbCXUWqQS/ NuV6+RXlriDuldfD+VeGPK9TKa6OhWe0sQt0x/NttbcMn5rhIIHdtm0+6r5uGpAuTrGaKT UIpaiQKsFYTpb2YozonTr+fzzhJkwEcrLZNxdFImNKbhxGHNZtg5w0b7m3c4r9kK0GfdXN 5U9HNH5NNtjhiFyMui58bl1dxAuCmOPgtNOHjkHOl/88sC1sq0K+zS6ktvy1wA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1756390733; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Nb/g8QUR8bWFtUGpB8I4C+fbjwmYZD8XtLWSXC/p/Bk=; b=f+b7xde0MHQs9AtfFDriz8sQ8nVzROoWaoY4JrxAYLahDvEFufKP7pc76eit18Qw2c++9r VJr5bJJCNjUu4QMT3TlfpS5bhid08/JvWn2zbj7L1vPBN+3xw0IDwrYnlofJDnGBd6/riU RqSdA9v+Wh5pqgdbuf6ft8cGZS2gRXJiw4dD04qbj6dVOHvBh7QQKmnGlXbky4zgdLhd7r +HMFDICvhqace4nJ7JQ9dDhpKU4Gof5CUKQtcMHCsQgygmfP9aSa2F7kfTYX8I66qK0HPP 2rRzkD55Gc69QSA1Snm2j2qPvfpyTWoDqyHaIF5Bx3r9g5zbA+GRwIEpyePQtQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1756390733; a=rsa-sha256; cv=none; b=McHcLe/ypXvjIip48EpNi52Nx3wRlgP+dqOkf1+NRRzbL0021ijX50USfz4aOXh5ADxiVA W7ViD4cPuoU6nw6ej/FxUgsZuecSHuthtd7ho4d7IxiERqlQOc0yOGeqgeZOSrZJbTXMoj aPodUG9L5jMUySrQwSLkuGnItP3ot1Ir6dK8dCHJaMA4QpOniRTZBK2XwJyDk4nPt19pqJ qdgdLLdRxJjY8kHtWsEnssLwRzfooKHuDFFRL+ElAreLjuVBnJrqNLKMZwahNuf/bvSSdk NN3mDXngBe1a+W8pBNuO8I6ZW+ehJNtaZtVSkdEqj9MNP/i612ynYWcDWJAHTg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from [IPV6:2601:5c0:4202:5670:4881:bfa2:e7ac:d89c] (unknown [IPv6:2601:5c0:4202:5670:4881:bfa2:e7ac:d89c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 4cCNms4VPCztn5; Thu, 28 Aug 2025 14:18:53 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Message-ID: Date: Thu, 28 Aug 2025 10:18:52 -0400 List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Static vxlan configuration fails - probably because of wrong order in rc Content-Language: en-US To: "Patrick M. Hausen" Cc: Zhenlei Huang , =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= , "freebsd-net@freebsd.org" References: <5F0F9208-9F4B-401B-B7B8-BCF64737A97F@punkt.de> <7000BD16-48A8-4D4A-A5F9-843F9F15F1FB@FreeBSD.org> <86y0rbiyln.fsf@ltc.des.dev> <738B8306-03E4-464A-B55A-66F635A2B5D3@FreeBSD.org> <44753230-F684-439D-B633-3CFFB99905C1@punkt.de> <864itzxrmr.fsf@ltc.des.dev> <75885C39-68D7-437E-9ECB-581E59AADC61@punkt.de> <701d0ee9-b532-4bd4-9ff5-7e485eef9447@FreeBSD.org> <991B637F-2C2B-4387-BE5B-909120E158B1@punkt.de> <2AB75754-C433-4736-9FD9-EDA5E13DF500@punkt.de> From: John Baldwin In-Reply-To: <2AB75754-C433-4736-9FD9-EDA5E13DF500@punkt.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 8/28/25 09:47, Patrick M. Hausen wrote: > Hi! > >> Am 26.08.2025 um 20:02 schrieb John Baldwin : >> >> On 8/22/25 17:30, Patrick M. Hausen wrote: >>> Hi, >>>> Am 22.08.2025 um 21:02 schrieb John Baldwin : >>>> >>>> A verbose dmesg of the two cases would probably be helpful. >>> I set verbose_loading="YES", then booted two times, once without, once >>> with if_smsc_load="YES". >>> -------- >>> $ diff dmesg-not-loaded.txt dmesg-loaded.txt >>> 10a11 >>>> module smsc already present! >>> 12c13 >>> < avail memory = 945016832 (901 MB) >>> --- >>>> avail memory = 944844800 (901 MB) >>> 178a180 >>>> vxlan0: Ethernet address: 58:9c:fc:00:82:82 >>> 182d183 >>> < vxlan0: Ethernet address: 58:9c:fc:00:82:82 >>> -------- >> >> That's not the full dmesg, just a diff. > > I was reluctant to spam the list with two full dmesg outputs if just a small part > is probably relevant. Thought a diff would catch it. > > Anyway I'll add both as an attachment - hope that passes the list server. Yep, and the context around the last diff (the vlxan) does show it is intertwined with smsc0 initializing. That said, I'm still not sure why it's not always failing TBH. In both cases vxlan0 reports its MAC address before ue0 has even attached. It might be useful to look at dmesg -a output to see what console messages from userspace are firing (e.g. when the rc.d scripts run), but I doubt that will really tell us anything new. >> A more general fix would be to add support for a 'vxlans_' >> variable similar to `vlans_' which would be a list of child vxlan >> interfaces. You would then just need `vxlans_ue0="vxlan0"` instead of >> cloned_interfaces="vxlan0" in rc.conf. > > That's actually the most interesting suggestion because shell scripting is what > I can do and I am familiar with that mechanism having used e.g. vlans_igb0... > for years. I'll try to implement and submit that possibly in the coming week. > OTOH there are still two EuroBSCCon presentations to be done, atm. :-) I think this would also perhaps fix your original root bug you mentioned at the start of the thread that vxlans are not created when an interface is brought up. -- John Baldwin