Date: Tue, 20 May 2025 23:45:23 +0200 From: Michael Grimm <trashcan@ellael.org> To: Kristof Provost <kp@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: epair(4) Message-ID: <43BAB886-2553-4EFE-9341-660F4D209B10@ellael.org> In-Reply-To: <369F5F7C-F88E-4C92-9DE0-C0FB0E5EFD54@FreeBSD.org> References: <20250515162552.9209B20E@slippy.cwsent.com> <20250515185919.87008219@slippy.cwsent.com> <45d0f49d-229b-46b4-af95-6e8c4c856661@plan-b.pwste.edu.pl> <2D38F889-E8C9-49A9-AA80-D5A46FDFFD02@FreeBSD.org> <6e33a247-4b2a-4f7c-8e1f-14a549db27cd@plan-b.pwste.edu.pl> <47624B57-16CA-4141-9761-A51F9E3F4078@FreeBSD.org> <75A8047F-73E0-467F-8005-7CA1ADA09788@ellael.org> <369F5F7C-F88E-4C92-9DE0-C0FB0E5EFD54@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
Kristof Provost <kp@freebsd.org> wrote: > On 20 May 2025, at 22:13, Michael Grimm wrote: >> Does "member interfaces" include or exclude the corresponding epair0b part? > It does not. Typically you’d insert epair0b in a different vnet, but either way, it is not a member interface of the bridge, so it can have IP addresses assigned to it. Thanks for the clarification and regards, Michaelhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43BAB886-2553-4EFE-9341-660F4D209B10>