From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=109.237.142.228; helo=relay14.alfahosting-server.de; envelope-from=karin@visti.de; receiver=edk2-devel@lists.01.org Received: from relay14.alfahosting-server.de (relay14.alfahosting-server.de [109.237.142.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 1E78521962301 for ; Wed, 16 Jan 2019 04:57:40 -0800 (PST) Received: by relay01.alfahosting-server.de (Postfix, from userid 1001) id 9C74232C2F94; Wed, 16 Jan 2019 13:57:38 +0100 (CET) X-Spam-DCC: : X-Spam-Level: *** X-Spam-Status: No, score=3.5 required=7.0 tests=BAYES_99 autolearn=disabled version=3.2.5 Received: from alfa3035.alfahosting-server.de (alfa3035.alfahosting-server.de [109.237.140.40]) by relay01.alfahosting-server.de (Postfix) with ESMTPS id DBDF032C02BB; Wed, 16 Jan 2019 13:57:36 +0100 (CET) Received: from webmail-alfa3035.alfahosting-server.de (localhost [IPv6:::1]) by alfa3035.alfahosting-server.de (Postfix) with ESMTPSA id 8EA6164EC279; Wed, 16 Jan 2019 13:57:36 +0100 (CET) MIME-Version: 1.0 Date: Wed, 16 Jan 2019 13:57:36 +0100 From: Karin Willers To: Laszlo Ersek Cc: edk2-devel@lists.01.org In-Reply-To: References: <8f102d0f-3856-f01f-9302-16f6b86103da@redhat.com> Message-ID: <7db27fc01100d84d543cd5caa8fabbe2@webmail-alfa3035.alfahosting-server.de> X-Sender: karin@visti.de User-Agent: Alfahosting Webmail/1.0 X-Alfa-Client-IP: 145.253.133.255 Subject: Re: EDK II Network Stack Issue X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2019 12:57:41 -0000 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit On 2019-01-10 13:40, Karin Willers wrote: > On 2019-01-07 20:27, Laszlo Ersek wrote: >> 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 > > The reason for this undertaking initially was to compile a Python.efi > that > supports sockets. We wanted that to be able to run the Chipsec suite > with > external network test partners under UEFI. The Chipsec guys do provide > pre-compiled Pyhon executables, but these do not include the network > stack. > > I think, I have to debug the issue myself ... > > Greetings, Karin Could please someone shed some light on how to enable debug prints using UefiDebugLibConOut in EfiSocketLib/Socket.c. Enabling debug prints is, IMHO, not very intuitive in edk2 ... Thanks, Karin