From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by passt.top (Postfix) with ESMTPS id 42E015A0262 for ; Mon, 27 Mar 2023 15:17:16 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 205CE320034E; Mon, 27 Mar 2023 09:17:12 -0400 (EDT) Received: from imap47 ([10.202.2.97]) by compute2.internal (MEProxy); Mon, 27 Mar 2023 09:17:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yawnt.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1679923031; x=1680009431; bh=il nLHnjHhrM3FOqpyoRNccy+UISvzSgFG4cxbXxI+q0=; b=vaahaV2tv81koUED38 Ga482V1oFrAhnoWYXpCEC0fuWDeWnaqZOHfW9bomcUu6mKt0ntbOXvqJ6uuYXY50 J2RdDp3OSQJWHxv3aEyO6dMnLHsiFoWrKJ6alFJFbHrlgVqcnFLn2Oqow6sSh0tP X/HJFhM4h0GIWrEfZ8m3kzoexxiZl4qPGcIE5ADSPpG8/6MqFC/9PiphVtk0VN6d TzsyQUhToaUox7tbLciL1DXY43M3MwMRaaioJJ5cONDk+5hupRzdWbt+4haD6VKV 3nWXhlXxswQ1T3oO9KHRKtL+pW09ZGvDatRFCs2oDUXhQUnC+N37w7HBAJMddvbz j0rA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1679923031; x=1680009431; bh=ilnLHnjHhrM3F OqpyoRNccy+UISvzSgFG4cxbXxI+q0=; b=n8pwQuQ5JZK1gtifNTeKO/c2O1CjF Tl5u8LxDVBP/2itSPjsImXdVbPppnaTsgf4yr/wY9OSzhY16PRsvJ0TmczHCY1OY SFr4Pm9jBb9+8sv1YzvrXa9mcDoL2QnekZQ+AeitPRbq4kCxvNv1+2hd/m5avE9+ E1imkgJE+f2Ox1C/ZbbzP6QNY4sKwzsJnS2Roxz9v8XGxNvf7WKrVMVtavDMOYnD p5nfOx1IRDOKBOnE3fpqrvGAO4VFzQ00KclTb5lkJ77EJQEX+Djrmd6Zhxaz1AFi ZQQcCmn6cAABWyXxISl43NVI+GZ9UL0z6rELkBrnIKOLMNlmMZ+mZpOUA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdehvddgieefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtsehttdertderredtnecuhfhrohhmpedfifhi rghnlhhutggrucfuthhivhgrnhdfuceomhgvseihrgifnhhtrdgtohhmqeenucggtffrrg htthgvrhhnpefhudehgeffhffgvdelueeigffgveffgfeftefhiedvjeeglefhueefudei keehvdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hmvgeshigrfihnthdrtghomh X-ME-Proxy: Feedback-ID: i7a494753:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 70E79A6007C; Mon, 27 Mar 2023 09:17:11 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-236-g06c0f70e43-fm-20230313.001-g06c0f70e Mime-Version: 1.0 Message-Id: In-Reply-To: <20230327150232.0cbc1ecc@elisabeth> References: <8a314e36-9459-4078-9e6c-db9b8c19464a@app.fastmail.com> <20230327114729.4f7a5c7d@elisabeth> <20230327150232.0cbc1ecc@elisabeth> Date: Mon, 27 Mar 2023 14:16:51 +0100 From: "Gianluca Stivan" To: "Stefano Brivio" Subject: Re: Failed to open tun socket in namespace Content-Type: text/plain X-MailFrom: me@yawnt.com X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation Message-ID-Hash: MN4DAZP27EO2P36OFDVYJLGCLSFUHZYX X-Message-ID-Hash: MN4DAZP27EO2P36OFDVYJLGCLSFUHZYX X-Mailman-Approved-At: Mon, 27 Mar 2023 15:40:58 +0200 CC: passt-user@passt.top X-Mailman-Version: 3.3.8 Precedence: list List-Id: "For users: support, questions and answers" Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Thanks for the reply, I'll give that a go and report back! Apologies, it seems my unusual use case is causing some headaches :) Kernel version: 5.19.0-35-generic (just a boring Ubuntu 22.04). Cheers, On Mon, Mar 27, 2023, at 14:02, Stefano Brivio wrote: > On Mon, 27 Mar 2023 13:22:12 +0100 > "Gianluca Stivan" wrote: > >> Thanks for the reply! >> >> Here is the ending of the log file: >> >> ... >> >> 3944.3562: TCP: index 19, timer expires in 2.000s >> 3944.3563: TCP: index 19, timer expires in 2.000s >> 3944.3566: TCP: index 19: STALLED >> 3944.3578: TCP: index 7: STALLED dropped >> 3944.3579: TCP: index 7, timer expires in 2.000s >> 3944.3584: TCP: index 7: STALLED >> 3944.3586: TCP: index 7: STALLED dropped >> 3944.3587: TCP: index 7: ACK_FROM_TAP_DUE dropped >> 3944.3588: TCP: index 7: ACK_FROM_TAP_DUE >> 3944.3588: TCP: index 7, timer expires in 2.000s >> 3944.3589: TCP: index 12: STALLED dropped >> 3944.3590: TCP: index 12, timer expires in 2.000s >> 3944.3620: tap write: No buffer space available >> 3944.3620: TCP: index 17: STALLED dropped >> 3944.3620: TCP: index 17: ACK_FROM_TAP_DUE dropped >> 3944.4420: ERROR: Failed to open tun socket in namespace >> >> No buffer space available seems interesting? > > Interesting, I had never seen ENOBUFS from a tap file descriptor. Let me > find out where it might come from (and how pasta should react to it), > it might take a bit. What kernel version are you using by the way? > > I mean, maybe we just have to try again (as if we received EAGAIN): > > diff --git a/tap.c b/tap.c > index 68ef480..21a786d 100644 > --- a/tap.c > +++ b/tap.c > @@ -323,7 +323,8 @@ static size_t tap_send_frames_pasta(struct ctx *c, > if (write(c->fd_tap, (char *)iov[i].iov_base, > iov[i].iov_len) < 0) { > debug("tap write: %s", strerror(errno)); > - if (errno != EAGAIN && errno != EWOULDBLOCK) > + if (errno != EAGAIN && errno != EWOULDBLOCK && > + errno != ENOBUFS) > tap_handler(c, c->fd_tap, EPOLLERR, NULL); > i--; > } > > but I'm not sure it's correct. You could probably try that as a > workaround meanwhile. > >> PS: let me know if you'd like the full file! > > No no, thank you, that was enough! > > About issue number 2. (the fact that we can't actually close and reopen > the tap file descriptor after this failure), I'll check if I can easily > reproduce that in a Podman setting. > > -- > Stefano