From nobody Sat May 17 06:34:04 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 4ZzvLK409Jz5w4P9 for ; Sat, 17 May 2025 06:34:17 +0000 (UTC) (envelope-from j.kelly.hays@gmail.com) Received: from mail-yb1-f169.google.com (mail-yb1-f169.google.com [209.85.219.169]) (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 4ZzvLK1yPWz41Yn; Sat, 17 May 2025 06:34:17 +0000 (UTC) (envelope-from j.kelly.hays@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-f169.google.com with SMTP id 3f1490d57ef6-e7b5f81594fso2126400276.3; Fri, 16 May 2025 23:34:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747463656; x=1748068456; h=content-transfer-encoding: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=GKaIc1IZEfi5/hh4n+nbFCR4TBUeynXGKU/IIukEPX4=; b=npOTV6Gc5BA6LqsnGUtz3sCDYasQYM5TQYkBtYDGiFq9twRifPV/vSHb32pvvCes9h /T4J3rHClyOHjI1UMAsQp3WI+Kx5Tzk1vyFaQxpHlNwfOxNIrFxY2627Bjuyqle4PuKi 9C1yCLHPEFDq33KZzAkURHEd0aYF4WtWbdYeMCqZ2e+w9IZICjURhtXycawn6KS7xLGc /Dt4oMHTqqKqtkK0R2fE4FhPKZgW7AnZ3KfEf4+xaHhgYLbfmlV4XTYhamWUF1q0L4bE nlaSD0lhgr3CivyEDK4CceKwP5BPA5SAJiAlKyNDvR68txk5ph1Srokqrn9n4wPmdvNI nxrA== X-Forwarded-Encrypted: i=1; AJvYcCUDKuIi+lCvkGMapJQTQMKfULAweW1INnupQzeUdIiMLP+uAvnSdRAZLB078k6typQuEvQV8Et3/FWfeok+04k=@freebsd.org, AJvYcCWiW4A8/mBhhXNHqkBclY46s0SbSYxtskN4rYYUTAOXfZ3ZxwmRtaHgv/0JZa36k7LvmEzD@freebsd.org X-Gm-Message-State: AOJu0YytQfPSrWK37F+N34CnTN1ULKA0ea3vNQoK5/ziaidopUnRwAVV rvDMtndQ7MwS8RFMsLdMtMGOKR84WD5Zjmlmedn5YUpKVwnpDh0Yltw4Y+udQjgx56SCJ5sY+IU J4q57xAtVvhBExBhR5RMGNWWLWVAFtAQ= X-Gm-Gg: ASbGncuDKxhxDh1vtcsdqJdJQtzZXKd1zPsWRX7wD0Iyefbktff3xgZS77ccrwD32bj Xp2u0oDUj003Wo2kY4Pwnl7bc819quaIzqeQc2oUy489mjBN07gCdA2cO/hrkoF9HfCjpbtvlBq VzqhNpExumyCWqcWg6Ht8ogx6q3XgNwS5/DQ== X-Google-Smtp-Source: AGHT+IGnclrLIFKXdC6cJGfUVS4G8LEzLYVpkJVvydehXAE/KqRzMtnkuAWUssAqQbOT4kwayFPhQEk30YkIp6v2X4M= X-Received: by 2002:a05:6902:110c:b0:e73:825:52eb with SMTP id 3f1490d57ef6-e7b6a42ca8emr8239439276.41.1747463656330; Fri, 16 May 2025 23:34:16 -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> <2D38F889-E8C9-49A9-AA80-D5A46FDFFD02@FreeBSD.org> In-Reply-To: From: Kelly Hays Date: Sat, 17 May 2025 01:34:04 -0500 X-Gm-Features: AX0GCFsA_CA2j2CWHVeQwHG2geSZJb9argiO69HE5BnRw516OheGXxVMO4nowDQ Message-ID: Subject: Re: epair(4) To: Konstantin Belousov Cc: Kristof Provost , Marek Zarychta , Cy Schubert , ivy@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4ZzvLK1yPWz41Yn X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Spamd-Bar: ---- On Sat, May 17, 2025 at 12:16=E2=80=AFAM Konstantin Belousov wrote: > > Let me give some context there: for me, such config appears when I set up > normal host, with the usual setting of IP address on a physical interface= . > Then some time later, realizing that I want to run a bhyve there as well, > I need to add a bridge. But for situation where the host is remote and > even without console access, it means to either keep the invalid config > if IP address on interface, or blindly do the sensitive config update > without a way to test it before reboot. > I think it is reasonable to expect there to be some safe way to transition an IP address from a physical interface to a bridge. Maybe some way to have the changes automatically backed out after some time if there is no connectivity. Anyway I think this use case is common enough we should at least provide documentation of = safe procedure to switch from physical interface to bridge when IP is the only w= ay into the machine. Thanks, Kelly