From nobody Mon Jan 29 19:56:57 2024 X-Original-To: freebsd-questions@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 4TNzb60b5yz59K2J for ; Mon, 29 Jan 2024 19:56:50 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TNzb55bl4z4Gl2 for ; Mon, 29 Jan 2024 19:56:49 +0000 (UTC) (envelope-from pprocacci@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-55ef011e934so2060457a12.3 for ; Mon, 29 Jan 2024 11:56:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706558208; x=1707163008; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pYmVDFvl7Sx+Ar6x2fJwa5S+XXryLg56EGbqz85BBLU=; b=eDyKToHENYLiN/hQnAmbwB2eJapERQBjFO8aH+weBXxI29TN7xJ7xCXu7sL+vS0G92 Cu13MVIGtcUyUrSepafjLTge2H3OdpjCYd2Co9OrEOfchvFmFFnnXc3dCqMtWJBPGkWt UUs9axpA6rxx5AWNAJqTtTmuBu8XnQ9LMt1g7qK2M4AjyFUep2HNOxySiq4EO5QFHQhX 0Iut9tm2UYjVuvILJifvzTS6JqC30XfOeq6vqFBtf/DWscglJYobAMhJzr4thjtt6FVO naMhGB5dvhSc/61xB6xbSmLs1LypkiGFLzbQ44FBy1kHVOa9h12doU75/YcwT2NRBqge Bn7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706558208; x=1707163008; 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=pYmVDFvl7Sx+Ar6x2fJwa5S+XXryLg56EGbqz85BBLU=; b=tbieKNs4GkIWqRw4kk1AILpSUP5PhgBX0J4m1f7NauBNgPJiPkHwgimH+4k7l1xHbk uClCeGU06gHzX4HOxta26JaQBq54eGhHfTvL8w/MjMYBm+Tx4SJV0g5VQbBRsRPtTgEM Ys13oaMk6I8opaxkls9cTO6Mxi+7cROzKlIuVsP2jFL+rVdn9FxxaijCDeXMzik2Bmci hXDYVR+G7/gEU4ZO3JcbrPQN+uUZ4a4CaUreHg4a6m73YZ1xvhgBlKTUwyXImeWWY/OP OY5f+8GVMSAgwooZkN47G+S6+3oR54AMEdhobpFL/tbkDAr2jNFpE4L/Z7ZZi+gQZr9o Nr0w== X-Gm-Message-State: AOJu0YynP002hRnfCzTeh86LLdWDhuLeOXK7huHtdrY7U6tZlpw3N47M 9pKbwSCFF5jd+bMtR35QyTRuYDApIT3TX13zl8HAxQ+N783Lk38vbUsvenFsoWFiogp+j973ULX 7VMHhCDstj6Vf4VgSgpgNVyHWnyZ10hU= X-Google-Smtp-Source: AGHT+IEwG+YX/6LTn6DnAKHCgX5Hw2poZH393W4e504SBvSyHnmYdUEDjREnd2YsmXa/kPaovolgJ08bvbL89M+LGYc= X-Received: by 2002:a05:6402:278c:b0:55f:31f7:4279 with SMTP id b12-20020a056402278c00b0055f31f74279mr465757ede.12.1706558208014; Mon, 29 Jan 2024 11:56:48 -0800 (PST) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Paul Procacci Date: Mon, 29 Jan 2024 14:56:57 -0500 Message-ID: Subject: Re: VirtIO/ipfw/natd throughput problem in hosted VM To: Jim Long Cc: freebsd-questions@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c6fbcb06101b0b64" X-Rspamd-Queue-Id: 4TNzb55bl4z4Gl2 X-Spamd-Bar: ---- 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] --000000000000c6fbcb06101b0b64 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jan 29, 2024 at 1:39=E2=80=AFPM Jim Long wrote: > On Mon, Jan 29, 2024 at 12:54:49PM -0500, Paul Procacci wrote: > > > > The most glaringly obvious thing to me is to use in-kernel nat instead = of > > natd. > > Packets won't have to leave the kernel at that point. > > It's detailed in ipfw(8). > > > > ~Paul > > Thank you very much! Your tip plus some cribbing from: > > https://www.neelc.org/posts/freebsd-ipfw-nat/ > > seems to have taken care of it. > > Regards, > > Jim > My pleasure Jim. ~Paul --=20 __________________ :(){ :|:& };: --000000000000c6fbcb06101b0b64 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Jan 29, 2024 at 1:39=E2= =80=AFPM Jim Long <fr= eebsd-questions@umpquanet.com> wrote:
On Mon, Jan 29, 2024 at 12:54:49PM -0500, Paul= Procacci wrote:
>
> The most glaringly obvious thing to me is to use in-kernel nat instead= of
> natd.
> Packets won't have to leave the kernel at that point.
> It's detailed in ipfw(8).
>
> ~Paul

Thank you very much!=C2=A0 Your tip plus some cribbing from:

https://www.neelc.org/posts/freebsd-ipfw-nat/

seems to have taken care of it.

Regards,

Jim

My pleasure Jim.
=
~Paul

--
________= __________

:(){ :|:& };:
--000000000000c6fbcb06101b0b64--