From nobody Mon Apr 21 09:54:21 2025 X-Original-To: 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 4Zh11P0YZ8z5tFqk for ; Mon, 21 Apr 2025 09:54:33 +0000 (UTC) (envelope-from zlei@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Zh11N722kz3Jt3; Mon, 21 Apr 2025 09:54:32 +0000 (UTC) (envelope-from zlei@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1745229273; 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: in-reply-to:in-reply-to:references:references; bh=IPjNPk68ugLdt6GhgH4jxj4CTjmjTZxnq2MBa8zTe9Q=; b=Cx0lKPoK1W1kgScsKpf1gmzsmbZiL1gvlxwwTW89fJD0RE71ZUGn5rkF4FIylyhskDponJ laJjv2tekQBXTnKYRVB8ENIG9XcJ+6LlgfpnOeJasus76HelAo7U5MKDVftYptMb1O+bi7 3PtLTtqEfdSvJ+l1Ml5caMCmO9o4P717VSrQTwlAGyeufEvq/uzSrC/HzEbGxQ7n2DeziK LDQUlvHpHDysqxUxkjI6rpQwvaypcMOwA3byqRrUJESx//66SEm65z3awNcGYHjf6IvWVj Wr+/6JyXdfsSTOUded5srJqkfkCpzlSaKOjsc2X4WxBCXN9k/zXUIm4XBcTR6w== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1745229273; a=rsa-sha256; cv=none; b=NYshRWXBz7zT6w8Q5UApYmuLT/NxH9iY4/3UOp5Zw0xfeWC2rWXszGzW4dm3A3aIhOaT5w CI6jORCK7I5lKL/fA6p56qrDeDZyCWsfYSy0S8YKVV7WjQ77IwmcIZTdjmqYHwVF5uKFQB 65eGTpFdJwJ4JBMf7C4tWlXM8ILYm9a04ZW2TeosQpPxbHirOHZEvFJGJaXyqUejU+rCuq gIsRqJGRaMHuhptfeoY3v9QspsxsIk1iOLor8gH0IT6pJ3K+ZECoj0pBnTriK9JqLvKRUy serC5e/VT4B9VRueYhPTOpvqXGw2l9avOqB/soIFLHyHOK3v2AECtNzkjxfhFA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1745229273; 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: in-reply-to:in-reply-to:references:references; bh=IPjNPk68ugLdt6GhgH4jxj4CTjmjTZxnq2MBa8zTe9Q=; b=fStqquPl4ZgYV+PtonzKWgyuJ0A6Mz77+v8gGhveqMzGU+rEve/P84okKeBdLYyGcnfLPp B+ipkuC/CkAORVAA4CUpnXqBuCsEcJRPv7rLmdC47Hw9+hNOo0vusUbou0uRx50Supjk4J 5odOml9qmDVj8uLWSeVLN3pf1GmIZtNmVVlpesrIubxUMUmyw4s1U3uLHqiGssIwkycJGd qLlUao35OOS2I517BclMQmIjKINQwOw9OXhbpoSzFZIKcPepIKmIfQeWpqZqnLwL3Iu2D7 XZ3PVxuTr1+DKXRruKLCDD+vdCc22EJGF2L/AaDocgu9No/5HlgH/hQ3LkZOSw== Received: from smtpclient.apple (unknown [IPv6:2001:19f0:6001:9db:98f0:9fe0:3545:10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: zlei/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Zh11M2hr4zG3Q; Mon, 21 Apr 2025 09:54:31 +0000 (UTC) (envelope-from zlei@FreeBSD.org) From: Zhenlei Huang Message-Id: <27C4D9F1-51D3-42D6-A490-A825C4EB6CC2@FreeBSD.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_11DCB6A2-CA45-4E21-8F3C-E977B83E001A" 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 (Mac OS X Mail 16.0 \(3696.120.41.1.10\)) Subject: Re: [Bug 278028] VXLAN interface is not working Date: Mon, 21 Apr 2025 17:54:21 +0800 In-Reply-To: <1437AB6C-96E7-4445-8B9C-E1E6986C0568@paige.bio> Cc: net@freebsd.org, =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: paige@paige.bio References: <1437AB6C-96E7-4445-8B9C-E1E6986C0568@paige.bio> X-Mailer: Apple Mail (2.3696.120.41.1.10) --Apple-Mail=_11DCB6A2-CA45-4E21-8F3C-E977B83E001A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Apr 20, 2025, at 8:20 AM, paige@paige.bio wrote: >=20 > Hey I was kind of wondering for my own info, where would be a good = place to open a bug for this particular problem if not here? > I noticed something earlier which was upon specifying the tunneling = parameter for a vxlan interface, I didn=E2=80=99t see tunnelfib in the = summary for the interface after but it accepted the parameter. Maybe = it=E2=80=99s not supposed to show it in summary I seem to remember on = openbsd that it would though (seems like it should) Just try to make it clear. The support for ioctl SIOCSTUNFIB ( ifconfig vxlan[N] tunnelfib x ) was = added via commit https://cgit.freebsd.org/src/commit/?id=3D7f7a804ae077 = .=20 The man page of ifconfig(8) was updated to reflect the change, but = vxlan(4) was not. Well by default the tunnelfib of a vxlan(4) interface is 0 ( the = system's default fib ) and is not displayed. If you set it to a fib = number other than 0, ifconfig(8) will show that. ``` # ifconfig vxlan0 vxlan0: flags=3D1008802 metric 0 = mtu 1470 options=3D80020 ether 58:9c:fc:00:7c:2c groups: vxlan media: Ethernet autoselect (autoselect ) status: active nd6 options=3D29 # sysctl net.fibs=3D2 net.fibs: 1 -> 2 # ifconfig vxlan0 tunnelfib 1 # ifconfig vxlan0 vxlan0: flags=3D1008802 metric 0 = mtu 1470 options=3D80020 ether 58:9c:fc:00:7c:2c groups: vxlan tunnelfib: 1 media: Ethernet autoselect (autoselect ) status: active nd6 options=3D29 ``` > where would be a good place to open an inquiry about that?=20 >=20 > Thanks=20 >=20 > Sent from my iPhone >=20 >> On Jan 24, 2025, at 8:11=E2=80=AFAM, bugzilla-noreply@freebsd.org = wrote: >>=20 >> =EF=BB=BFhttps://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278028 >>=20 >> Zhenlei Huang changed: >>=20 >> What |Removed |Added >> = --------------------------------------------------------------------------= -- >> Status|New |Closed >> Resolution|--- |Works As Intended >>=20 >> --- Comment #14 from Zhenlei Huang --- >> Given this is not the fault of if_vxlan(4) but is a configuration = problem ( >> duplicated MAC address ), I'm closing this issue now. >>=20 >> -- >> You are receiving this mail because: >> You are the assignee for the bug. Best regards, Zhenlei= --Apple-Mail=_11DCB6A2-CA45-4E21-8F3C-E977B83E001A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Apr 20, 2025, at 8:20 AM, paige@paige.bio wrote:

Hey = I was kind of wondering for my own info, where would be a good place to = open a bug for this particular problem if not = here?
I noticed something earlier which was upon = specifying the tunneling parameter for a vxlan interface, I didn=E2=80=99t= see tunnelfib in the summary for the interface after but it accepted = the parameter. Maybe it=E2=80=99s not supposed to show it in summary I = seem to remember on openbsd that it would though (seems like it should) =

Just try to make = it clear.

The support for ioctl = SIOCSTUNFIB ( ifconfig vxlan[N] tunnelfib x ) was added via = commit https://cgit.freebsd.org/src/commit/?id=3D7f7a804ae077 = ;. 
The man page of ifconfig(8) was updated to reflect = the change, but vxlan(4) was not.

Well= by default the tunnelfib of a vxlan(4) interface is 0 ( the system's = default fib ) and is not displayed. If you set it to a fib number other = than 0, ifconfig(8) will show that.

```
# ifconfig = vxlan0
vxlan0: = flags=3D1008802<BROADCAST,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu = 1470
= options=3D80020<JUMBO_MTU,LINKSTATE>
ether = 58:9c:fc:00:7c:2c
groups: vxlan
media: = Ethernet autoselect (autoselect <full-duplex>)
status: = active
= nd6 = options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

# sysctl net.fibs=3D2
net.fibs: 1 -> = 2

# ifconfig vxlan0 tunnelfib = 1
# ifconfig vxlan0
vxlan0: = flags=3D1008802<BROADCAST,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu = 1470
= options=3D80020<JUMBO_MTU,LINKSTATE>
ether = 58:9c:fc:00:7c:2c
groups: vxlan
= tunnelfib: 1
media: Ethernet autoselect = (autoselect <full-duplex>)
status: active
nd6 = options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
`= ``

where would be a good place to open an = inquiry about that?

Thanks

Sent from my iPhone

On Jan 24, 2025, at 8:11=E2=80=AFAM, bugzilla-noreply@freebsd.org wrote:

=EF=BB=BFhttps://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278028<= br class=3D"">
Zhenlei Huang <zlei@FreeBSD.org> = changed:

=          What =    |Removed =             &n= bsp;       |Added
---------------------------------------------------------------= -------------
=            Status|N= ew =             &n= bsp;           |Clo= sed
=        Resolution|--- =             &n= bsp;           |Wor= ks As Intended

--- Comment #14 from Zhenlei = Huang <zlei@FreeBSD.org> ---
Given this is not = the fault of if_vxlan(4) but is a configuration problem (
duplicated MAC address ), I'm closing this issue now.

--
You are receiving this mail = because:
You are the assignee for the bug.


Best = regards,
Zhenlei
= --Apple-Mail=_11DCB6A2-CA45-4E21-8F3C-E977B83E001A--