search for: pxebc

...there are PCs with UEFI implementations not following the former rule. i.e. HP Elitebook 2570p (single NIC) shell> dh ... 172: DevPath (..9,0x0)/MAC(FC15B4E81CAC,0x0))Net MNPSb ARPSb DHCPv4Sb TCPv4Sb IPv4Sb IPv4Config UDPv4Sb MTFTPv4Sb ... 184: DevPath (..00:0000:0000:0000:0000:0000))Load Net Pxebc ... 19D: DevPath (..v4(0.0.0.0,UDP,DHCP,0.0.0.0))Load Net Pxebc ... shell> dh 172 Handle 172 (730D8A98) Dpath (730D8E98) ACPI Device Path for Acpi HID PNP0A03, UID 0 Hardware Device Path for PCI Function (0) Device (19) Messaging Device Path for MAC M...

...ns not following the former rule. > > i.e. HP Elitebook 2570p (single NIC) > > shell> dh > ... > 172: DevPath (..9,0x0)/MAC(FC15B4E81CAC,0x0))Net MNPSb ARPSb DHCPv4Sb TCPv4Sb IPv4Sb IPv4Config UDPv4Sb MTFTPv4Sb > ... > 184: DevPath (..00:0000:0000:0000:0000:0000))Load Net Pxebc > ... > 19D: DevPath (..v4(0.0.0.0,UDP,DHCP,0.0.0.0))Load Net Pxebc > ... > > shell> dh 172 > Handle 172 (730D8A98) > Dpath (730D8E98) > ACPI Device Path for Acpi > HID PNP0A03, UID 0 > Hardware Device Path for PCI > Function (0) Devi...

On 09/26/2015 10:36 AM, Patrick Masotta via Syslinux wrote: > > About PXEbc Peter has recently said: >> The problem with the pxebc is that it only supports one concurrent TFTP >> connection, and Syslinux expects to be able to keep multiple files open >> at the same time. >> http://www.syslinux.org/archives/2015-August/024025.html > > I wonder...

>>> Lovely, the ServiceBindings are on a handle that resembles the NIC while the Pxebc is IP-type specific.? Looks like we should try to do a ServiceBinding based on Pxebc but fall back to MAC-based searching, saving all 3 handles, the image handle, Pxebc handle, and ServiceBinding handle.? Presumably the UDP and TCP handles _should_ be the same... -- -Gene <<< OK now...

...e TCPv4Sb (rather than being on a separate handle). -- -Gene <<< What I've found: (from older to newer hardware) 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) 2) SB protocols are loaded under a different that LoadeImage's DeviceHandle, while Pxebc is loaded under the LoadeImage's DeviceHandle. (Elitebook 8470p/2570p) 3) SB protocols and Pxebc are loaded under the LoadeImage's DeviceHandle (VMware Workstation 10). About MNPSb; even when it presents the same interface than all the Service Binding protocols remember we have to create...

...have a watchdog in our system, it reboots prior to completing all of the timeouts due to prolonged inactivity. Is there a better, timelier or more user friendly way to handle the errors? 2. Just curious as to why the decision was made to create new udp connection instead of using the existing pxebc? udp is already set up and configured. The reason I ask is we were having problems in our customer environment with the routetable. We modified the code to use pxebc protocol and it works perfectly. This environment consists of three separate subnets, client on one, dhcp server on a second and...

We can, and do, suspend a TFTP transfer simply by delaying the ACK packet as necessary. On September 29, 2015 7:45:27 PM PDT, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> >On 09/26/2015 10:36 AM, Patrick Masotta via Syslinux wrote: >> >> About PXEbc Peter has recently said: >>> The problem with the pxebc is that it only supports one concurrent >TFTP >>> connection, and Syslinux expects to be able to keep multiple files >open >>> at the same time. >>> http://www.syslinux.org/archives/2015-August/024025....

...lex 9010 A22 (EFI 2.31 Revision 4.653 American Megatrends): Shell> dh -p Net Handle dump by protocol 'Net' 326: DevPath (..9,0x0)/MAC(xxxxxxxxxxxx,0x0))Net MNPSb ARPSb DHCPv4Sb IPv4Sb IPv4Config UDPv4Sb MTFTPv4Sb HiiConfAccess 341: DevPath (..HCP,0.0.0.0,0.0.0.0,0.0.0.0))Load Net Pxebc 349: DevPath (..00:0000:0000:0000:0000:0000))Load Net Pxebc Dell OptiPlex 9020 A16 (EFI 2.31 Revision 4.653 American Megatrends): Shell> dh -p Net Handle dump by protocol 'Net' 335: DevPath (..9,0x0)/MAC(xxxxxxxxxxxx,0x0))Net MNPSb ARPSb DHCPv4Sb TCPv4Sb IPv4Sb IPv4Config UDPv...

On Fri, Jun 26, 2015 at 10:49 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > Commit 23b2707 should resolve this. Please > let me know if you need > test binaries > > -- > -Gene > <<< > > > 1) About the Service Binding protocols, PXE protocol, etc having the same handle# is clear if we > see that the number is in fact

...tion file) later the parsing action on the >>received file defines if other/s TFTP+parsing actions are required in >>case the INCLUDE command was previously found. If this is correct then >>there is never more than one TFTP file transfer at any given time (and >>we could use PXEbc). >>Please let me know if I'm wrong. Thanks. >> >>Best,Patrick On Wed, Sep 30, 2015 at 1:42 AM, H. Peter Anvin <hpa at zytor.com> wrote: > > We can, and do, suspend a TFTP transfer simply by delaying the ACK packet as necessary. Observing this behavior appears...

>>> > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) The only solution for these is to use our own stack (likely full TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL).? Does the handle for Pxebc contain a Net?? >>> It does contain a Net but there are 2 issues with SNP: 1) The interface is different than UDPv4/TCPv4 protocols; this imply lot of code. 2) SNP has its non-blocking transmit issues ; see "Flaws in the design" at https://wiki.linaro.org/LEG/Engineering/Kernel/...

...firmware? OK, then buy our new line of PC. > i.e. Elitebooks 2560p/8460p fail while the newer Elitebooks 2570p/8470p work > like a charm :-/ As stated before, it is my understanding that the Elitebook 2560p/8460p devices _are_compliant_ with UEFI-2.0 which stated to use an SNP directly under PXEBC while UEFI-2.1 stated to use a MNP directly under the PXEBC. Please don't call these devices non-compliant UNLESS you are more specific. Another solution that I'm not sure if anyone has tried with these devices that are UEFI-2.0-compliant and UEFI-2.1-noncompliant is using iPXE to stack o...

...;ve found: > (from older to newer hardware) > > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) The only solution for these is to use our own stack (likely full TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL). Does the handle for Pxebc contain a Net? I found out that my EFI shell on VMware VMs can also handle output redirection like: guid > fs0:\efi-guid.txt dh > fs0:\efi-dh.txt dh bd >> fs0:\efi-dh.txt fs0 being the EFI boot partition on the hard drive of the VM. > 2) SB protocols are loaded under a different...

>>> > Considering any editing/buffering benefits are only marginal (AFAIK) there are not benefits with the current approach.On the other hand the list of potential problems includes: > 1) We cannot use the ubiquitous EFI PXEbc protocol forcing us to rely on the (not always present) EFI Binding Services. > Best,Patrick Speaking utterly ignorantly here... could this switch help with the issues we see with HP systems?? The load-and-hang many of them do with syslinux.efi as discussed here?? E.g., maybe they implement thi...

...653 American Megatrends): > > Shell> dh -p Net > Handle dump by protocol 'Net' > > 326: DevPath (..9,0x0)/MAC(xxxxxxxxxxxx,0x0))Net MNPSb ARPSb DHCPv4Sb > IPv4Sb IPv4Config UDPv4Sb MTFTPv4Sb HiiConfAccess > > 341: DevPath (..HCP,0.0.0.0,0.0.0.0,0.0.0.0))Load Net Pxebc > > 349: DevPath (..00:0000:0000:0000:0000:0000))Load Net Pxebc > > > > Dell OptiPlex 9020 A16 (EFI 2.31 Revision 4.653 American Megatrends): > > Shell> dh -p Net > Handle dump by protocol 'Net' > > 335: DevPath (..9,0x0)/MAC(xxxxxxxxxxxx,0x0))Net MNPSb...

...L protocol in order to perform packet level transactions." while version 2.1 states "An EFI_PXE_BASE_CODE_PROTOCOL will be layered on top of an EFI_MANAGED_NETWORK_PROTOCOL protocol in order to perform packet level transactions." >>> Could this be the reason why in the past Pxebc and the SBs where attached to different handles?? mmhhh I have to admit; UEFI development is a bit messy... Best, Patrick

...Patrick's code and I finally see good responses with a VMware VM's e1000e NIC (never saw ANYTHING good from it until now). git://github.com/geneC/syslinux.git https://github.com/geneC/syslinux.git -- -Gene <<<< I've seen your code. Your first patch considered Pxebc, UDPv4Sb and TCPv4Sb are created under the same handle but now we know this is not the case. Your new patch now considers UDPv4Sb and TCPv4Sb are created under the same handle thing that we really do not know if is always true or not. My patch looks slower than yours because it parses the hand...

> > Is syslinux.efi supposed to be able to handle HTTP URLs? > > If the underlying firmware can. Try just specifying an HTTP URL in the > config or on the command line instead of the path-prefix option. Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. Somehow I was under the impression improvements from pxelinux variants like lpxelinux were

...could >>> easily be localized though I believe there's only 2 common groups, the >>> two we see here. >>> >>> Did you happen to peek at the version command? I'm guessing it's >>> saying 2.0 since the UDPv4Sb is not on the same handle as the PxeBc. >> >> Gene, I am curious, do you have an idea how to fix this? > > Yes, I have an idea but I need to add some debug code so I can > understand more how your particular machine is behaving. > > -- > -Gene On Tue, Nov 28, 2017 at 6:45 AM, Joakim Tjernlund via Syslinux...

...wrote: >>>> > > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) > > The only solution for these is to use our own stack (likely full > TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL). > Does the handle for Pxebc contain a Net? >>>> > > It does contain a Net but there are 2 issues with SNP: > 1) The interface is different than UDPv4/TCPv4 protocols; this imply lot of code. Not as much as you may think. We already have lwIP implemented into lpxelinux.0. It's more a matter of using...