public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Maloy <jmaloy@redhat.com>
Cc: sbrivio@redhat.com, passt-dev@passt.top
Subject: Re: [PATCH] test/lib: Add --config-net to setup_pasta()
Date: Sun, 21 Jun 2026 11:18:25 +1000	[thread overview]
Message-ID: <ajc74at3GE7zpSka@zatzit> (raw)
In-Reply-To: <20260620200921.1720380-1-jmaloy@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1954 bytes --]

On Sat, Jun 20, 2026 at 04:09:21PM -0400, Jon Maloy wrote:
> Since commit b4dace8 ("fwd: Direct inbound spliced forwards to the
> guest's external address"), inbound splice connections target the
> guest's external address (addr_seen) rather than loopback.  This
> requires the namespace tap interface to be configured with that
> address.
> 
> setup_pasta() starts pasta without --config-net, so the tap interface
> in the namespace is never brought up and has no addresses or routes.
> Splice connections to addr_seen fail because the address is
> unreachable in the namespace, breaking all pasta TCP and UDP tests.
> 
> Add --config-net to the pasta command line in setup_pasta(), matching
> what setup_passt_in_ns() and setup_two_guests() already do.
> 
> Signed-off-by: Jon Maloy <jmaloy@redhat.com>

No.  We use setup_pasta() to test NDP and DHCP behaviour with pasta,
so we need it not to preconfigure the network.

> ---
>  test/lib/setup | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/test/lib/setup b/test/lib/setup
> index 59945987..dbf8079d 100755
> --- a/test/lib/setup
> +++ b/test/lib/setup
> @@ -107,7 +107,7 @@ setup_pasta() {
>  	[ ${DEBUG} -eq 1 ] && __opts="${__opts} -d"
>  	[ ${TRACE} -eq 1 ] && __opts="${__opts} --trace"
>  
> -	context_run_bg passt "./pasta ${__opts} -f -t 10002 -T 10003 -u 10002 -U 10003 -P ${STATESETUP}/passt.pid $(${NSTOOL} info -pw ${STATESETUP}/ns.hold)"
> +	context_run_bg passt "./pasta ${__opts} -f -t 10002 -T 10003 -u 10002 -U 10003 --config-net -P ${STATESETUP}/passt.pid $(${NSTOOL} info -pw ${STATESETUP}/ns.hold)"
>  
>  	# pidfile isn't created until pasta is ready
>  	wait_for [ -f "${STATESETUP}/passt.pid" ]
> -- 
> 2.52.0
> 

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-06-21  2:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-20 20:09 Jon Maloy
2026-06-21  1:18 ` David Gibson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ajc74at3GE7zpSka@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=jmaloy@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).