Displaying 20 results from an estimated 800 matches similar to: "[PATCH 0/1] Network UEFI PXE DHCP/proxyDHCP fix"
2015 Jun 12
0
[PATCH 0/1] Network UEFI PXE DHCP/proxyDHCP fix
On Thu, Jun 11, 2015 at 4:02 PM, <jeff_sloan at selinc.com> wrote:
> from: Jeff Sloan <jeff_sloan at selinc.com>
>
> Update UEFI PXE proxyDHCP handling.
>
> This patch is based on commit ID 8a00e49
>
> Modify two files to specify valid ip addresses. These files are efi/pxe.c
> and efi/udp.c.
1) In commit 2e266c35, I proposed using UseDefaultAddress. As I
2015 Jun 03
5
[PATCH 0/1] EFI PXE DHCP/proxyDHCP issues fix
The UEFI PXE boot DHCP/proxyDHCP issue is very timely. I am working on
that very topic now.
Our scenario is a manufacturing environment set up to format and
load/install custom hard drive images in our systems.
Our environment:
This is a manufacturing floor setup where we build computers for our
customers. We have two servers and a client in the mix, all connected via
Ethernet (IPv4 only).
2015 Jun 09
2
EFI and proxyDHCP: setups
>>>
And I stand corrected Patrick.? Apparently some clients are
stuffing bad values into packets and moving the code to save the MAC resolves
the deafness I observed.
Commit 8a00e49 is the change.
--
-Gene
<<<
OK; I was about to ask you a few wiershark captures...
I looked at the last commit and I think
if (mode->PxeReplyReceived)
pkt_v4 =
2015 Mar 14
0
[PATCH 0/1] EFI access from Com32 modules
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
2015 Jun 09
2
EFI and proxyDHCP: setups
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
2015 Oct 03
2
UEFI: Failed to load ldlinux.e64/ldlinux.e32
On Sat, Oct 03, 2015 at 09:20:10AM +0300, Ady via Syslinux wrote:
>
> > I have a patch that I think may help your situation of syslinux.efi
> > being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if
> > any of you are using an EFI ia32 platform).
> >
> > The basics are that we try to enable UseDefaultAddress as it helps
> > certain clients
2015 Feb 20
6
[PATCH 0/1] EFI image booting capabilities
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
---
2017 May 31
6
[PATCH 1/4] efi/udp: core_udp_connect should use SubnetMask not StationAddress for netmask
Signed-off-by: Julien Viard de Galbert <jviarddegalbert at online.net>
---
efi/udp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/efi/udp.c b/efi/udp.c
index 1088f47..b0f13ad 100644
--- a/efi/udp.c
+++ b/efi/udp.c
@@ -163,7 +163,7 @@ void core_udp_connect(struct pxe_pvt_inode *socket, uint32_t ip,
} else {
udata.UseDefaultAddress = FALSE;
2015 Jul 18
2
[syslinux:firmware] efi: Add network support
On Thu, May 9, 2013 at 6:39 AM, syslinux-bot for Matt Fleming
<matt.fleming at intel.com> wrote:
> Commit-ID: fe283b78c973268f2d1f0309826ceeb5c9e8978d
> Gitweb: http://www.syslinux.org/commit/fe283b78c973268f2d1f0309826ceeb5c9e8978d
> Author: Matt Fleming <matt.fleming at intel.com>
> AuthorDate: Fri, 22 Mar 2013 14:54:09 +0000
> Committer: Matt Fleming
2015 Jun 09
0
EFI and proxyDHCP: setups
On Tue, Jun 9, 2015 at 9:05 AM, Patrick Masotta <masottaus at yahoo.com> wrote:
>>>>
> And I stand corrected Patrick. Apparently some clients are
> stuffing bad values into packets and moving the code to save the MAC resolves
> the deafness I observed.
> Commit 8a00e49 is the change.
> --
> -Gene
> <<<
>
> OK; I was about to ask you a
2015 Jan 12
2
PXE Booting EFI
>
>Excellent investigation and
>details.? Thank you for this help.? Given
>the details of your situation, I'm
>reasonably certain it's a SYSLINUX
>bug
>but there is still a small chance of it being some sort
>of negative interaction.
>
I do not think there's a negative interaction, while the VMware EFI environment correctly retrieves
the NBP
2015 Oct 02
6
UEFI: Failed to load ldlinux.e64/ldlinux.e32
I have a patch that I think may help your situation of syslinux.efi
being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if
any of you are using an EFI ia32 platform).
The basics are that we try to enable UseDefaultAddress as it helps
certain clients with routing and works on numerous other clients. If
we timeout on receiving a packet and have never received any packets,
disable
2015 Jan 19
2
PXE Booting EFI
> EFI has proven to be more robust.? The catch
> here is order.? The
> ProxyOffer data must
> take precedence over the PxeReply data but both
> of them probably need to be parsed.
Not really; If you parse both "next server" from the
last parsed packet (PxeReply) will overwrite
the value gathered from the ProxyOffer and that leads
to "Nest-server"= DHCP Server IP
2016 Feb 24
6
[PATCH 2/5] ntfs: remove unused variable and have ntfssect use char API calls
The variable 'ok' is never used and generates a warning. Remove it. Also
ntfssect.c is designed to be compiled in non Unicode mode when using
MSVC compilers, so remove all ambiguity about it (LPCTSTR -> LPCSTR, use
of 'A' API calls) so that it doesn't break when compiled in Unicode
mode, which is what Rufus uses with MSVC.
-------------- next part --------------
2016 Feb 29
1
[PATCH 0/1] UEFI UDP/TFTP
On Sun, Feb 28, 2016 at 11:26 AM, Patrick Masotta via Syslinux
<syslinux at zytor.com> wrote:
> b) "UEFI: Failed to load ldlinux.e64/ldlinux.e32"
> http://www.syslinux.org/archives/2015-October/024341.html
> This report has led to Gene's patch:
>
> https://github.com/geneC/syslinux/commit/9e0926bb338deb5c634ccb4ee29eb4577158cfdc
> it was reported working but
2015 Feb 20
0
[PATCH 0/1] EFI image booting capabilities
On Fri, Feb 20, 2015 at 05:08:26AM -0800, Patrick Masotta via Syslinux 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.
>
> Best,
> Patrick
>
> Signed-off-by: Patrick Masotta
2015 Jul 08
4
[PATCH] Updated udp.c to use real client ip and subnetmask values if on local subnet
from: Jeff Sloan <jeff_sloan at selinc.com>
Based on commit: 9314e330
Setting UseDefaultAddress to TRUE uses invalid StationAddress and
SubnetMask values. This is in a network with a local TFTP/MTFTP server. If
the server is local, on the same subnet, UseDefaultAddress is set to false
and the client ip and subnetmask are loaded, otherwise set
UseDefaultAddress to TRUE. This is added to
2015 Jan 11
0
PXE Booting EFI
On Sun, Jan 11, 2015 at 10:32 AM, Patrick Masotta <masottaus at yahoo.com> wrote:
>
>>First, I was looking for the actual values.
>>For a VM with (among other values):
>
>> config.version = "8"
>> virtualHW.version = "10"
>> ethernet0.virtualDev = "e1000"
>> guestOS = "rhel6-64"
>> firmware =
2013 Nov 29
2
[PATCH] efi: reuse UDP port with sendto
Without an assigned source port, Transmit function assign a random new
source port to the packet being sent. It thus have to be set before
calling Transmit if the source port have already been decided.
Conversly, we have to save the assigned port to reuse it later if
needed.
Resolve bug #35.
Signed-off-by: Celelibi <celelibi at gmail.com>
---
efi/udp.c | 18 ++++++++++++++++++
1 file
2015 Jan 19
0
PXE Booting EFI
On Mon, Jan 19, 2015 at 3:09 PM, Patrick Masotta <masottaus at yahoo.com> wrote:
>
>> EFI has proven to be more robust. The catch
>> here is order. The
>> ProxyOffer data must
>> take precedence over the PxeReply data but both
>> of them probably need to be parsed.
>
> Not really; If you parse both "next server" from the
> last parsed