* Understanding TCP4 Connect() not working after calling Close() and Configure(NULL)
@ 2019-05-11 2:23 rebecca
0 siblings, 0 replies; only message in thread
From: rebecca @ 2019-05-11 2:23 UTC (permalink / raw)
To: devel@edk2.groups.io
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-05-11 2:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-05-11 2:23 Understanding TCP4 Connect() not working after calling Close() and Configure(NULL) rebecca
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox