From: Laszlo Ersek <lersek@redhat.com>
To: Karin Willers <karin@visti.de>, edk2-devel@lists.01.org
Subject: Re: EDK II Network Stack Issue
Date: Mon, 7 Jan 2019 20:27:24 +0100 [thread overview]
Message-ID: <8f102d0f-3856-f01f-9302-16f6b86103da@redhat.com> (raw)
In-Reply-To: <ff11ca6fa69fd82e2236f7de77771623@webmail-alfa3035.alfahosting-server.de>
On 01/04/19 15:02, Karin Willers wrote:
> G'Day!
>
> I'm trying to get networking under edk2 up and running. I tried
> AppPkg/Applications/Sockets/RawIp4Tx
> under OVMF. The raw packet is sent out on the network, but the
> application never returns from the
> socket close routine.
>
> I'm currently using UDK2017 with the latest security patches (downloaded
> December 18 2018). The network
> driver under OVMF is the e1000 driver.
>
> The effect that the socket close never returns is also visible when
> running RawIp4Tx on real hardware,
> so I think the behavior has nothing to do with OVMF or the UEFI itself.
>
> Does anyone see similar effects? Any hints on setting up networking
> under edk2 correctly?
The socket (= libc-level networking) APIs are not the most robust ones
in edk2, in my -- admittedly limited -- experience. I'd suggest using
applications and shell commands that use UEFI protocols instead, for
networking. (I understand that could be a challenge if you are porting a
standard C program to UEFI.)
Thanks
Laszlo
next prev parent reply other threads:[~2019-01-07 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 14:02 EDK II Network Stack Issue Karin Willers
2019-01-07 19:27 ` Laszlo Ersek [this message]
2019-01-10 12:40 ` Karin Willers
2019-01-16 12:57 ` Karin Willers
2019-01-16 16:51 ` Laszlo Ersek
[not found] ` <b747eeda2cb9af7318986091b1645fb0@webmail-alfa3035.alfahosting-server.de>
2019-01-22 17:34 ` Laszlo Ersek
2019-01-23 22:14 ` Karin Willers
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=8f102d0f-3856-f01f-9302-16f6b86103da@redhat.com \
--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