From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: passt.top; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: passt.top; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=Y/ZBpQcv; dkim-atps=neutral Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by passt.top (Postfix) with ESMTP id 748365A061C for ; Fri, 29 Nov 2024 08:43:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1732866194; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=we3Kq6UEW7SWgG40DOlkJGu+ZHUxPz+NgI+KaaKh/hI=; b=Y/ZBpQcvfE2FJWue+2YO3MkYyLPPA0Zjh+v5ZPySuMw7lRLR/WPtAwE848WzjJLrKxu9AN YTG0EtRh35ash0zdRlbelFvqoR5gFjIflqy86/o5/3thf5DLf8l+o3haZkFYTy+oYFvWFH NTsKj6pbaHJO/5+K9By/yVz7ZTPAHvo= Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-395-Inq9CXlNM0i9UyAr6n0_YA-1; Fri, 29 Nov 2024 02:43:13 -0500 X-MC-Unique: Inq9CXlNM0i9UyAr6n0_YA-1 X-Mimecast-MFC-AGG-ID: Inq9CXlNM0i9UyAr6n0_YA Received: by mail-wr1-f70.google.com with SMTP id ffacd0b85a97d-385d6ee042eso724626f8f.0 for ; Thu, 28 Nov 2024 23:43:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732866191; x=1733470991; h=content-transfer-encoding:mime-version:organization: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=we3Kq6UEW7SWgG40DOlkJGu+ZHUxPz+NgI+KaaKh/hI=; b=IbEV00wWORkFcPtwECsM2Ptfo9VEN90yqnNszEG/bwb0Z8U3nShIQW/+pbz1rpr/Z7 Ft9Q988hkrtjTcoTbYG3ZxsJ7AT4nRxOx7mAjcgzFuQcoZ3+/fJ3yiH6DTc9AbOGZxD7 HLWZ93kI9DqJKbkX3Y35tdcSOqlqDV5mG2j1ePGxk9wERfCavRhYtxiWG5Cxi9GxnKZL iiin8ELWczc5pgXuF9qIQCRNm1CGUkiEF/s8RnhEesCngiR2tJpj4WCObQUHep6iIPNu gOzelUkizx2pXPzy8ts3koP+P48KxLYQ4vxBD0iWTPvah7e/Veq1W/+DVd/kSUKFjjEM BLdg== X-Gm-Message-State: AOJu0YzblsmYDimSjp+5ANDkvVLV+YkXlQii8mI0opcIj2litl4yaOOO fAqcPrz6EurGZVOhXYFE2KQyNYE+OaZlb0rrZVjLd3B4jfuw+Gw0Z5l+h5MT8yj8zVJk89bfR7F 1D98dJMkA3xKnoquYfzignY2lFZUph9xnxjKTIi8MdJ2SeMMZHAhGXYfvmssQlx5Mg3BEazfyP+ NMlcYGLs/c+iNhgy1IvDN+Kfo2QlfkTFo+ X-Gm-Gg: ASbGncuWgA0zpJakBCP1dQKiPXuJQ3Ji8sDglbZrtS2Uu4hSXYwJY1d/8MaHzFClEru hzuCTQLf7IOIw4BCrn3a670GEvdVvRfVhY5tQvIalLFj44VWKEwODllqbb2M/fMLhluAffFQ1iq mBi98Tj8DR3CSVqkWhJeBftRxPpCuJQFmTB4+eX331c5+qvkzfYzBxguDQ+gOs6zuP3WEms3EIt JMHYNQEBxhixDznK63jQEsXsDVbkTy2u9Z0OEx7HDGckCn8d3wG5yyfpQ7qhWaeh57uQ0DE7abF a3k= X-Received: by 2002:a05:6000:491a:b0:385:bc42:52e4 with SMTP id ffacd0b85a97d-385c6eba8bemr9261511f8f.24.1732866191142; Thu, 28 Nov 2024 23:43:11 -0800 (PST) X-Google-Smtp-Source: AGHT+IFTG2egkNyCGgLdigLMp7msqpYg+x1SzH0VK8HjbWJwT2YWmeEeD6FgTXEKDWrdOE4gcNY+6Q== X-Received: by 2002:a05:6000:491a:b0:385:bc42:52e4 with SMTP id ffacd0b85a97d-385c6eba8bemr9261482f8f.24.1732866190735; Thu, 28 Nov 2024 23:43:10 -0800 (PST) Received: from maya.myfinge.rs (ifcgrfdd.trafficplex.cloud. [176.103.220.4]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-385ccd92e44sm3682671f8f.110.2024.11.28.23.43.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Nov 2024 23:43:10 -0800 (PST) Date: Fri, 29 Nov 2024 08:43:08 +0100 From: Stefano Brivio To: Jon Maloy Subject: Re: [PATCH] pasta: make it possible to disable socket splicing Message-ID: <20241129084308.5b9d0352@elisabeth> In-Reply-To: References: <20241129004532.2514834-1-jmaloy@redhat.com> Organization: Red Hat X-Mailer: Claws Mail 4.2.0 (GTK 3.24.41; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: lVXh8_GfHJdP0Bor6_Zeqwfq2rbSkh8Qaz5FvdxqvH0_1732866192 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: 2P4ADYQUADUA6KQJWWJPT3B6E6S6XLAE X-Message-ID-Hash: 2P4ADYQUADUA6KQJWWJPT3B6E6S6XLAE X-MailFrom: sbrivio@redhat.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: passt-dev@passt.top, lvivier@redhat.com, dgibson@redhat.com X-Mailman-Version: 3.3.8 Precedence: list List-Id: Development discussion and patches for passt Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Thu, 28 Nov 2024 20:21:23 -0500 Jon Maloy wrote: > I am even questioning if it is necessary: If the port is bound on the hos= t, > the client only needs to use some of the non-loopback addresses on the > host to reach it via the tap interface. The same applies to inbound traffic by the way, as I mentioned: just use a non-loopback address in the namespace/guest to reach it via the tap interface: $ { sleep 1; : | nc -4 -N passt.top 9999; } & ./pasta -q --config-net -p nc= .pcap -t 9999 -- nc -q1 -l 9999 [1] 2052460 [1]+ Done { sleep 1; : | nc -4 -N passt.top 9999; } $ tshark -r nc.pcap ip 8 0.968929 88.198.0.161 =E2=86=92 88.198.0.164 TCP 62 55898 =E2=86=92= 9999 [SYN] Seq=3D0 Win=3D65535 Len=3D0 MSS=3D61440 WS=3D256 11 0.968967 88.198.0.164 =E2=86=92 88.198.0.161 TCP 62 9999 =E2=86=92 = 55898 [SYN, ACK] Seq=3D0 Ack=3D1 Win=3D65480 Len=3D0 MSS=3D65480 WS=3D4096 12 0.969000 88.198.0.161 =E2=86=92 88.198.0.164 TCP 54 55898 =E2=86=92= 9999 [ACK] Seq=3D1 Ack=3D1 Win=3D65536 Len=3D0 13 0.969017 88.198.0.161 =E2=86=92 88.198.0.164 TCP 54 55898 =E2=86=92= 9999 [FIN, ACK] Seq=3D1 Ack=3D1 Win=3D65536 Len=3D0 14 0.969063 88.198.0.164 =E2=86=92 88.198.0.161 TCP 54 9999 =E2=86=92 = 55898 [FIN, ACK] Seq=3D1 Ack=3D2 Win=3D65536 Len=3D0 15 0.969118 88.198.0.161 =E2=86=92 88.198.0.164 TCP 54 55898 =E2=86=92= 9999 [ACK] Seq=3D2 Ack=3D2 Win=3D65536 Len=3D0 ...that is, I guess that you or David find this convenient, but strictly speaking, it's also unnecessary (actually, I won't use it myself, because it's more typing). --=20 Stefano