From: ebiederm@xmission.com (Eric W. Biederman)
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: 2.6.38-rc3 regression ipv6 TFTP download with curl failing in getpeername?
Date: Tue, 08 Feb 2011 01:41:32 -0800 [thread overview]
Message-ID: <m1ei7iamnn.fsf@fess.ebiederm.org> (raw)
Does anyone have a clue what could be causing this? It looks like
getpeername for ipv6 has changed in the tcp case did udp possibly get
missed?
Currently curl is failing for me like this. When doing a tftp transfer
over ::1.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 200M 0 0 0 570k 0 12.7M 0:00:15 --:--:-- 0:00:15 12.7M
curl: (55) getpeername() failed with errno 107: Transport endpoint is not connected
Tomorrow I will dig deeper but for tonight I wanted to ask and see what
other people see.
Eric
reply other threads:[~2011-02-08 9:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m1ei7iamnn.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox