search for: nic_1

...patch and so far it proved to work in a multi-NIC environment: I've set a VMware EFI client with 2 NICs connected to the same network, using the VMware DHCP server and Serva as proxyDHCP. Setting a MAC filter in Serva I forced the client not receiving PXE redirection parameters alternative on NIC_1 or NIC_2; the client always booted correctly from the NIC that received the full set of PXE parameters. It seems to work. It would be really interesting if the HP guys having this issue can give it a try... Please see the new code at https://github.com/ppatpat/syslinux/blob/master/efi/main.c P...

>>> Please see the new code at https://github.com/ppatpat/syslinux/blob/master/efi/main.c <<< I'm having a bit of a problem with the build using the latest version of main.c. I get an error that stops the build because variable i is redefined in efi_create_binding. On line 104 i is defined as UINTN and then on line 182 it is redefined as int. I deleted 182 but just

...proved to work in a multi-NIC environment: > I've set a VMware EFI client with 2 NICs connected to the same network, > using the VMware DHCP server and Serva as proxyDHCP. > Setting a MAC filter in Serva I forced the client not receiving PXE redirection parameters > alternative on NIC_1 or NIC_2; the client always booted correctly from the NIC that received the > full set of PXE parameters. It seems to work. This sounds positive for cases 2&3 but still leaves #1 high and dry. > It would be really interesting if the HP guys having this issue can give it a try... > &g...

...ved to work in a multi-NIC environment: > I've set a VMware EFI client with 2 NICs connected to the same network, > using the VMware? DHCP server and Serva as proxyDHCP. > Setting a MAC filter in Serva I forced the client not receiving PXE redirection parameters > alternative on NIC_1 or NIC_2; the client always booted correctly from the NIC that received the > full set of PXE parameters. It seems to work. This sounds positive for cases 2&3 but still leaves #1 high and dry. <<< Case #1 is really a problem; the only alternative would be implementing SNP but...

...ti-NIC environment: > > I've set a VMware EFI client with 2 NICs connected to the same network, > > using the VMware DHCP server and Serva as proxyDHCP. > > Setting a MAC filter in Serva I forced the client not receiving PXE redirection parameters > > alternative on NIC_1 or NIC_2; the client always booted correctly from the NIC that received the > > full set of PXE parameters. It seems to work. > > This sounds positive > for cases 2&3 but still leaves #1 high and dry. > <<< > > Case #1 is really a problem; the only alternativ...

>>> 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 attempting to migrate from vmware to xen, however I need to be able to run more than one bridge. Think of it this way: xen0 xenU-1 xenU-2 xenU-3 ------------------------------------------------------------------------ Inside_bridge_1: eth0 vm1_eth0 vm2_eth0 virtual_switch_2: vm1_eth1 vm2_eth1 vm3_eth1 Outside_bridge_3: eth1 vm2_eth2 vm3_eth0 Now, I can modify the existing