From nobody Sat Jul 19 18:10:31 2025 X-Original-To: freebsd-current@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 4bkvpv36N2z62854 for ; Sat, 19 Jul 2025 18:10:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lj1-f174.google.com (mail-lj1-f174.google.com [209.85.208.174]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bkvpt1yLVz41WX; Sat, 19 Jul 2025 18:10:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of adrian.chadd@gmail.com designates 209.85.208.174 as permitted sender) smtp.mailfrom=adrian.chadd@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-lj1-f174.google.com with SMTP id 38308e7fff4ca-32f1df5b089so29545831fa.3; Sat, 19 Jul 2025 11:10:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752948644; x=1753553444; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/q8LXt/jQgRZBAXnO0QemXKDdDrC6Cvrc344YrC5DbE=; b=eIu0php82fkWobFFIqyNEUGdg+wKUhH1+taPqR76GgLTbQU4YSH9F0gBu55TQEgQFF cL3pxjgAjBocOJ9NjPiC0zELNOXfXuZrYJp0VyasbZvuwtq5OKC2oTiDXG9v79vUVXeH QYBWgKqLeyhfYFPeHUfgyAOimkqg5rNQwHDvSvnbbZtM8wQ6BHTo8TIH5BW2zC9Yu9gO 3WMmNHCCV1K480SwG5vWPzQkYpsqGvmWkglH/3HEzLCbTZNO4f0VcNh59Cdod8z8fAPA FA5MAvdQt2dqiutxJC8yzI9zolk8q6C1Fpz40rtjJfkk9y9/HvIgxF3Y5QYFWtUFPFi0 xt4g== X-Forwarded-Encrypted: i=1; AJvYcCW1HIv+aA9Y7ldtdgTBvIAw8B2ehrnvOX9w4srDFX1f5WkKwkNGLYuwfLYVhWp6ZVM1010=@freebsd.org X-Gm-Message-State: AOJu0Ywnj9rrvQaqJZo48ytcHUMk+5KdNUndBr0oudSiRSuiRN+ETGRA soDpLIqFAMnZLHusCv47tGbkqO1sZ3KfNGrbxoa5oaz7NL4E52bwLCAk0v3R6HzUZRgANroLTqI 3xWIantrt609uNeQFR1xNBfziezM3KWVcgQ== X-Gm-Gg: ASbGncv/GRXlwRzbZvnT2ACQ1A8wxedVSu/RzjnI9EEPHaq1w+KoU30mMG5S46MJXEr t6OUQiBQb2T7RX6Zs+DOQTL66CJH8J5kH6kePWYlR6ZVGlFOF7aCwMBZI0gTxYWgEHBjrb7aHZi 2VAypSzxSi+5QqWsucQky52A3ccYLPCW3K0jZYOHtSTCuusMu7tNabVBpFn2IX4rQenyhd4FKpa Dwn4oAx X-Google-Smtp-Source: AGHT+IGouoPHOIuzeOlngQGFIcyEq7bDMTmS0hh2L++amM7m2HHjcyfWZtGV0TyJCJyIbH6x9aebAW/hhK7Jrh9VVcg= X-Received: by 2002:a05:651c:2220:b0:32a:81a2:8a8d with SMTP id 38308e7fff4ca-330a7bfb3b1mr19232901fa.26.1752948643885; Sat, 19 Jul 2025 11:10:43 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <20250515162552.9209B20E@slippy.cwsent.com> <20250515185919.87008219@slippy.cwsent.com> <45d0f49d-229b-46b4-af95-6e8c4c856661@plan-b.pwste.edu.pl> <932111f8-f5ca-46d1-9f66-983f80f6116b@protected-networks.net> <8DCF0DAB-5EE5-4FEF-8CCC-1D7AF971BA8C@hausen.com> In-Reply-To: From: Adrian Chadd Date: Sat, 19 Jul 2025 11:10:31 -0700 X-Gm-Features: Ac12FXyChC7yjrj1oV1vQJt_AS82lbH9FBjlxq5UUxL37uWLKcXb4TXjt7OZ8ik Message-ID: Subject: Re: epair(4) To: qroxana , Lexi Winter Cc: "freebsd-current@freebsd.org" Content-Type: multipart/alternative; boundary="0000000000003a77e3063a4c2928" X-Spamd-Result: default: False [-0.56 / 15.00]; NEURAL_SPAM_MEDIUM(0.98)[0.984]; NEURAL_HAM_LONG(-0.83)[-0.826]; NEURAL_HAM_SHORT(-0.81)[-0.813]; FORGED_SENDER(0.30)[adrian@freebsd.org,adrianchadd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; TO_DN_EQ_ADDR_SOME(0.00)[]; FREEMAIL_TO(0.00)[protonmail.com,freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; TAGGED_FROM(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.174:from]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[adrian@freebsd.org,adrianchadd@gmail.com]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.174:from]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4bkvpt1yLVz41WX X-Spamd-Bar: / --0000000000003a77e3063a4c2928 Content-Type: text/plain; charset="UTF-8" On Fri, 18 Jul 2025 at 02:06, qroxana wrote: > Hi all, > > What's the best practice for setting up bridge0 on a NFS root system? > Let's say the system is boot from TFTP via em0 and mount the NFS root > filesystem, is there any way to create bridge0 and addm em0 after the > system is up? or is it possible to create and use bridge0 before mounting > the NFS root? > > That's an interesting problem that I don't think was even thought about when bridge(4) was added to FreeBSD. :-) Ivy, we should talk about how to err, "reconfigure" things in /etc/rc.conf appropriately, as I /think/ the tftp boot path configures the interface addressing via kernel APIs, and we'll need to undo it and flip it to a bridge. -adrian Thanks, > > > --0000000000003a77e3063a4c2928 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, 18 Jul = 2025 at 02:06, qroxana <qroxan= a@protonmail.com> wrote:
Hi all,

What's the best practice for setting up bridge0 on a NFS root system? Let's say the system is boot from TFTP via em0 and mount the NFS root f= ilesystem, is there any way to create bridge0 and addm em0 after the system= is up? or is it possible to create and use bridge0=C2=A0 before mounting t= he NFS root?


That's an interesting problem that= I don't think was even thought about when bridge(4) was added to FreeB= SD. :-)

Ivy, we should talk about how to err, &quo= t;reconfigure" things in /etc/rc.conf appropriately, as I /think/ the = tftp boot path configures the interface addressing via kernel APIs, and we&= #39;ll need to undo it and flip it to a bridge.


-adrian

Thanks,


--0000000000003a77e3063a4c2928--