search for: servas

Hello, I did join 2 sites using an IPSEC tunnel, and made one domain trust the other (2 small Samba DC based domains with about 10 users in each) I first had resolving issues until I decided to keep only one WINS server for both networks (though this is still an issue to me because if for any reason the tunnel is broken, I have no longer WINS on one side). Finally here is my setup : Network A

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

On Sun, Jun 7, 2015 at 5:09 PM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > Patrick, I think I've been able to figure out some missing details > about your VMware Workstation tests. For a proxyDHCP, > I'm using dnsmasq. Could you try to confirm your test was the > same basic setup? > > On VMware Workstation 10 with a VMHWv10 VM set to

Patrick, I think I've been able to figure out some missing details about your VMware Workstation tests. For a proxyDHCP, I'm using dnsmasq. Could you try to confirm your test was the same basic setup? On VMware Workstation 10 with a VMHWv10 VM set to EFI firmware for x64, I've been able to get mixed results, depending on if a gateway is provided. With a VMHWv9 VM, I see what appear

On Mon, Jun 8, 2015 at 8:19 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Jun 7, 2015 at 5:09 PM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>>> >> Patrick, I think I've been able to figure out some missing details >> about your VMware Workstation tests. For a proxyDHCP, >> I'm using dnsmasq. Could you try to confirm

On Mon, Jul 6, 2015 at 6:04 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > > What I'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

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

Hi Bruce Thank you very much for reaching out. This is likely to be a short discussion due to me potentially learning that my infrastructure possibly has shortfalls that I did not appreciate until just recently. What I was hoping to do is deploy Windows from a Thecus branded NAS. Natively the NAS does not support PXE, but with community created mods it is achievable. So with this mod

This patch adds to the core EFI image booting capabilities. It was tested on VMware EFI clients and HP Elitebook EFI notebooks, only on PXE environments but it should work on non-PXE scenarios as well. Feedback appreciated. Best, Patrick Signed-off-by: Patrick Masotta <masottaus at yahoo.com> --- diff -uprN a/com32/elflink/ldlinux/execute.c b/com32/elflink/ldlinux/execute.c ---

On Thu, Jul 9, 2015 at 5:30 AM, Patrick Masotta <masottaus at yahoo.com> 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?

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

On Fri, Feb 20, 2015 at 8:08 AM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: > This patch adds to the core EFI image booting capabilities. > It was tested on VMware EFI clients and HP Elitebook EFI notebooks, > only on PXE environments but it should work on non-PXE scenarios as well. > > Feedback appreciated. If you've made any changes to this, I'd

Thank you for the prompt reply. What you said is promising so if I may, with your help can we decipher what SYSLinux files goes where from the ground up? If this is too broad a question or may take up too much of your time then I understand and appreciate your help thus far. Richard -----Original Message----- From: Bruce Ferrell [mailto:bferrell at baywinds.org] Sent: Saturday, 17 November 2018

This patch adds to Com32 modules the capabilities of accessing the EFI environment The idea is simple, the EFI parameters "image" and "table" received by syslinux.efi's efi_main() are stored in the "firmware" structure, next they are retrieved from the Com32 module which is linked against the gnu-efi static library. The Com32 module can use the EFI

>>> Patrick, I think I've been able to figure out some missing details about your VMware Workstation tests.? For a proxyDHCP, I'm using dnsmasq.? Could you try to confirm your test was the same basic setup? On VMware Workstation 10 with a VMHWv10 VM set to EFI firmware for x64, I've been able to get mixed results, depending on if agateway is provided.? With a VMHWv9

Hi Anfo, Windows 7 deployment is actually something I do from pxe... It does requires "extras" from Microsoft to build the windows install image, but they don't cost anything and it's a one time thing.? I'll have to locate my docs on the Windows deployment tool. PXE install of windows is the fastest Windows 7 Ultimate N install I've ever done... Much faster than

Hello all I was just hoping to see if there was a forum, or a patient individual kind enough to help me configure PXELinux (I only understand the wiki to a point). Apologies for using this medium to call for aid as I've been unable to locate an alternative support channel. Richard

Lately I've working on a backup script that utilize rsync together with MySQL logging. Everything has been working just fine until now when I needed to generate some errors for my error handling code. So I took a CD (which I scratched with a needle) and mounted it to the file system. There after I started the backup job which went on forever and never got completed. It seems that rsync

>>> The real DHCP server supplies client ip address only. Everything else comes from proxyDHCP. The proxyDHCP server supplies boot file name, boot file (syslinux.efi), boot loader (ldlinux.e64), config file, tinycore and OS image files. <<< This is not completely correct: your DHCP server provides an IP and your proxyDHCP server only processes a complementary DHCP

On Sun, Feb 28, 2016 at 04:26:07PM +0000, Patrick Masotta via Syslinux wrote: > > > I have re-implemented /efi/udp.c > Signed-off-by: Patrick Masotta <masottaus at yahoo.com> > > diff -uprN a/core/fs/pxe/pxe.h b/core/fs/pxe/pxe.h > --- a/core/fs/pxe/pxe.h 2014-10-06 10:27:44.000000000 -0600 > +++ b/core/fs/pxe/pxe.h 2016-02-28 08:44:47.127996962 -0700 > @@