search for: udpv4sb

...k'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 handles on ev...

...can Megatrends): Shell> dh -p Net Handle dump by protocol 'Net' Dell OptiPlex 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 (...

...f them when you have chosen a special NIC handle."" Unfortunately 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...

...mp; memcmp(mac_1, mac_2, PXE_MAC_LENGTH) > == > > 0) { is correct > > > https://sites.google.com/site/genecsyslinux/150829-efi-1136.tgz?attredirects=0&d=1 > > Those should produce debug text listing the original PxeBc handle and > its full MAC then proceed to list the UDPv4Sb handles and their MACs. > I'm still trying to figure out if there's a way to get the handle > numbers that the shells use. > > > On Fri, Aug 28, 2015 at 3:46 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > >> > >> On Fri, Aug 28, 2015 at 6:34 AM, Patri...

...onsole commands to a USB pendrive >>> > 2) SB protocols are loaded under a different that LoadeImage's DeviceHandle, > while Pxebc is loaded under the LoadeImage's DeviceHandle. (Elitebook 8470p/2570p) a) Hunt for a Sb. b) use Net <<< I do a hunt for either UDPv4Sb or TCPv4Sb >>> > 3) SB protocols and Pxebc are loaded under the LoadeImage's DeviceHandle (VMware Workstation 10). a) use Sb on Pxebc handle b) use Net <<< I reuse the "Hunt for a Sb" approach (the overhead is not much) but I could easily use a) >&gt...

On Fri, Aug 28, 2015 at 4:22 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > Thanks Derrik; I got your efi-dh.txt > > I've found this: > > 252: SimpleNetwork PXEBaseCode LoadFile DevicePath(0000:0000:0000:0000:0000:0000)) > 267: SimpleNetwork PXEBaseCode LoadFile DevicePath(065F36E00EE,0x1)/IPv4(0.0.0.0)) > 27C: SimpleNetwork PXEBaseCode LoadFile

>>> 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 it

>>> I'm just debating what's the best algorithm here.? It would seem if the LoadeImage's DeviceHandle provides UDPv4Sb, use it as it's guaranteed to be the same interface.? Otherwise, we need a MNPSb (EFI_MANAGED_NETWORK_SERVICE_BINDING) that provides UDPv4Sb across the same interface.? Presumably it should also provide TCPv4Sb (rather than being on a separate handle). -- -Gene <<< What I'...

On Wed, Jul 8, 2015 at 7:34 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > What about the observed symptoms? Have you performed an inline packet Jeff, there's specific code that creates specific responses that if you had mentioned what you saw, I'd expect we could have seen something sooner. -- -Gene

...'t know what to do with this info so attaching it here. > > > > Ok. Different GUID aliases. Line 1381 says what I see as "Net" you > > likely see as "SimpleNetwork". This handle has the necessary > > "UDPv4ServiceBinding" (I see as "UDPv4Sb"). > > > > Thanks for the excellent data. It's been a while since I looked at > > the handle search code to debug this. > > Did you ever see a "disable UseDefaultAddress" message? The code > should have printed those original messages dump the new m...

...e 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. Not strictly. Look closer. > My patch looks slower...

...he mac is 8c-dc-d4-0d-a5-f0 so && memcmp(mac_1, mac_2, PXE_MAC_LENGTH) == > 0) { is correct https://sites.google.com/site/genecsyslinux/150829-efi-1136.tgz?attredirects=0&d=1 Those should produce debug text listing the original PxeBc handle and its full MAC then proceed to list the UDPv4Sb handles and their MACs. I'm still trying to figure out if there's a way to get the handle numbers that the shells use. > On Fri, Aug 28, 2015 at 3:46 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Fri, Aug 28, 2015 at 6:34 AM, Patrick Masotta <masottaus at y...

On Mon, Aug 31, 2015 at 06:08:19AM -0400, Gene Cumm via Syslinux wrote: > On Aug 30, 2015 8:42 PM, "Derrick" <derrick22 at gmail.com> wrote: > > > > Gene thanks, here is the output > > > > My IP is 10.2.49.10 > > Img @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 =

...NIC handle."" > > Unfortunately 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...

..._1, mac_2, PXE_MAC_LENGTH) == >> > 0) { is correct >> >> https://sites.google.com/site/genecsyslinux/150829-efi-1136.tgz?attredirects=0&d=1 >> >> Those should produce debug text listing the original PxeBc handle and >> its full MAC then proceed to list the UDPv4Sb handles and their MACs. >> I'm still trying to figure out if there's a way to get the handle >> numbers that the shells use. >> >> > On Fri, Aug 28, 2015 at 3:46 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> >> >> On Fri, Aug 28...

...attaching it here. > > > > > > > > Ok. Different GUID aliases. Line 1381 says what I see as "Net" you > > > > likely see as "SimpleNetwork". This handle has the necessary > > > > "UDPv4ServiceBinding" (I see as "UDPv4Sb"). > > > > > > > > Thanks for the excellent data. It's been a while since I looked at > > > > the handle search code to debug this. > > > > > > Did you ever see a "disable UseDefaultAddress" message? The code > > &gt...

...>>> > > 2) SB protocols are loaded under a different that LoadeImage's DeviceHandle, > > while Pxebc is loaded under the LoadeImage's DeviceHandle. (Elitebook 8470p/2570p) > > a) Hunt for a Sb. > b) use Net > <<< > > I do a hunt for either UDPv4Sb or TCPv4Sb Just summarizing choices. >>>> > > 3) SB protocols and Pxebc are loaded under the LoadeImage's DeviceHandle (VMware Workstation 10). > > a) use Sb on Pxebc handle > b) use Net > <<< > I reuse the "Hunt for a Sb" approach (the...

...ps://sites.google.com/site/genecsyslinux/150829-efi-1136.tgz?attredirects=0&d=1 >> >> >> >> >> >> Those should produce debug text listing the original PxeBc handle >> >> >> and >> >> >> its full MAC then proceed to list the UDPv4Sb handles and their >> >> >> MACs. >> >> >> I'm still trying to figure out if there's a way to get the handle >> >> >> numbers that the shells use. >> >> >> >> >> >> > On Fri, Aug 28, 2015 at 3:46 AM,...

On Mon, Aug 31, 2015 at 07:59:06PM -0400, Gene Cumm via Syslinux wrote: > On Mon, Aug 31, 2015 at 6:42 PM, Derrick M <derrick.martinez at gmail.com> wrote: > > Thanks Gene! > > > > this one is much better > > EXCELLENT! That's what I wanted to see. It iterates through 3 > handles, printing the entire MAC buffer and the handle's memory > address.

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