From nobody Sat Dec 21 19:20:04 2024 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 4YFvHt2jL9z5WxfN for ; Sat, 21 Dec 2024 19:20:10 +0000 (UTC) (envelope-from vadimnuclight@gmail.com) Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 4YFvHs4Pbnz4hqC; Sat, 21 Dec 2024 19:20:09 +0000 (UTC) (envelope-from vadimnuclight@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-2ffa49f623cso36652171fa.1; Sat, 21 Dec 2024 11:20:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734808808; x=1735413608; darn=freebsd.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=Vl8UDRBRTGFAqnHkqY1sn9nUb4ZtLPziMA6Exk4GNv4=; b=F7v4ylOCUkISzhPLlykL4nMEbWqfKycWiG+C5TZioW1EzDPhq13rDn36E/pkiWqNY4 /2e19/CCVj1EtBUOkfji++d2/XkT56UqXkaUwgQIRvUl+dNRyoQ5F1lELqwr173sIMbZ FhKiZAss2PmaLxoh3Cc7AFolFbUKlsfQZ6MMnmscTEks1M0jZzO6AwD0HBXVgXk7/2hk ah9MUqx5F0tkq7+vx8CajNC1IIvwjhdHpsn35qlAWFg/sZ0rOBHm1EGs+8TyfZmGZ9AR DucrICFgf8JNus+9F/k44+yDxy/yZTfaJ/cqsBbG+2D0idQ+qCuT7PXy6x+2KjcFl/Kn TKKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734808808; x=1735413608; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Vl8UDRBRTGFAqnHkqY1sn9nUb4ZtLPziMA6Exk4GNv4=; b=LDgoHy9MJUiKbaXkaf6+sy5RvhQZ7DAHkiO69PXy+zfv4ZGszrPthiZLk0A5VDFPEQ FoPSpWgOynfbT4uJ4e48NafqFuLjlLiPsAhJ5vPk6iGUhKABSQCT/r/wcTj1fmDjTktb +cZSrWCYa7R4G7FmC28tNwTBnkFRImoe3hhMs92pmtKm8nSyiJKxrwD065ajFi3RHp9k nj/6AM+IyptOI+U8hCMtb6bqexiSasL9jCSS4Ro5qQvaTfYKfDoPFsb9cu7NaV2tJh+I t1Rcht43qD5XAn5bSnng393CH33k9U6fet4BZkQI5gGyKJbmll6np0UxfbAxvAccVZtf OSxg== X-Forwarded-Encrypted: i=1; AJvYcCXDNdQs/CEL/sy1Qg1E1hcq331acU0Y4I0B868D6abGznpdNC8emmgEKrWOd1O/hBXHgud646g2oQKeow==@freebsd.org X-Gm-Message-State: AOJu0YyMg69gNRlknTMEkSbwheNEPCHnwn7fxL9E1TyZ31RneL3Xr4E6 7aWyw/O+1Z5lV7gaUib5ncfzXDGjmjZIhHfdrPxB4Vfgl4DxrkmCfWAtfw== X-Gm-Gg: ASbGncu837yGIpaBS06igQIU1liEiE0NbKX/eGO+iR/cCHK+Pu0p5sVnL4uGR8++nCI /J3LQozT4xV52VsB+2mzCG6mJBa8BRqHSf/g2WsAO5fIo4SGz70pyEIvZC+hVELW3aZnSuiEn3A +oe4t2S5J/OmfRks6odAkoiGIfuAE0FjiibbodI9YbzoANKIkyILvB7Fprz4xNCQxSjgf5u5WZi eTrgyMv3fZgWObfMxGYYvMffgFeaDRLXaF04y8JKbLg+VnP2nUJw2Y/MqjjWppc3XXsJmPCIcWf bD2CXwLcZnXqZrxn7QDg20Y= X-Google-Smtp-Source: AGHT+IGcfgxXuFOiv3h2tkrz8ZKip8jXk+kgd5bQU/AHtyjTcMMIyaRCOzeVG5ok4jQXatFKjdyzyw== X-Received: by 2002:a05:651c:221d:b0:302:1d24:8d95 with SMTP id 38308e7fff4ca-3046860d423mr27316011fa.29.1734808807244; Sat, 21 Dec 2024 11:20:07 -0800 (PST) Received: from nuclight.lan (broadband-37-110-95-35.ip.moscow.rt.ru. [37.110.95.35]) by smtp.gmail.com with ESMTPSA id 38308e7fff4ca-3045b069e97sm8555781fa.75.2024.12.21.11.20.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 21 Dec 2024 11:20:06 -0800 (PST) Date: Sat, 21 Dec 2024 22:20:04 +0300 From: Vadim Goncharov To: "Bjoern A. Zeeb" Cc: Mark Johnston , freebsd-net@freebsd.org Subject: Re: per-FIB socket binding Message-ID: <20241221222004.60826be9@nuclight.lan> In-Reply-To: <4p5o59s4-5p70-0775-1479-990o1s5po7r2@yvfgf.mnoonqbm.arg> References: <4p5o59s4-5p70-0775-1479-990o1s5po7r2@yvfgf.mnoonqbm.arg> X-Mailer: Claws Mail 3.19.1 (GTK+ 2.24.33; amd64-portbld-freebsd12.4) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4YFvHs4Pbnz4hqC X-Spamd-Bar: ---- On Sat, 21 Dec 2024 16:34:25 +0000 (UTC) "Bjoern A. Zeeb" wrote: > On Tue, 17 Dec 2024, Mark Johnston wrote: > > > Lately I've been working on adding FIB awareness to bind(2) and > > inpcb lookup. Below I'll describe the project a bit. Any > > feedback/comments/suggestions would be appreciated. > > > > Today, a TCP or UDP socket can receive connections or datagrams > > from any FIB. > > SCTP? > > > Any thoughts/comments? > > How much use are FIBs still these days? Half of the original use > cases I can think of could easily and better be overcome by using > vnet jails with a physical or virtual interface (e.g, vcc) being > delegated to the vnet. > > I wonder if anyone on FreeBSD is using FIBs to actually have > multi-FIB forwardig but that very little touches your use case apart > from the mgmt which again can be factored out better (or inversely, > factoring out the forwarding). > > I would honestly know who and how FIBs are still in use today or if > they should be put on a list to be removed for 16 (I assume I might be > surprised). That sounds pretty strange. The main FIB utilization is in routing area and has nothing to do with jails at all (a router/firewall don't need jails). (not that I'm fine with FIB concept at all, but unfortunately that's routing industry standard concept, and removing FIBs will make FreeBSD lacking behind competitors here as it was before 6.x) -- WBR, @nuclight