From: rebecca@bluestop.org
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Understanding TCP4 Connect() not working after calling Close() and Configure(NULL)
Date: Fri, 10 May 2019 20:23:03 -0600 [thread overview]
Message-ID: <df731bd4-2b32-f69e-b1f7-c450a7bbf206@bluestop.org> (raw)
Hi,
I've come across what to me looks like a bug, but is probably a
misunderstanding of how to use the EFI_TCP4_PROTOCOL.
Under OVMF (I've not tried anything else), I've found that when I call
tcp4->Close(), tcp4->Configure() with NULL to reset it, then
tcp4->Connect() the TCP stack reports in the debug output that it's sent
a SYN packet, but I don't see it in Wireshark, and the connection
attempt eventually times out. I'm only able to reconnect if I call
tcp4sb->CreateChild() to get a new instance.
-- Rebecca Cran
reply other threads:[~2019-05-11 2:23 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-list 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=df731bd4-2b32-f69e-b1f7-c450a7bbf206@bluestop.org \
--to=devel@edk2.groups.io \
/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