Displaying 20 results from an estimated 3000 matches similar to: "pxelinux 6.03 EFI using proxy DHCP"
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 Sep 12
2
pxelinux tries to load ldlinux.c32 from DHCP server, instead of next-server
On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote:
> On Sat, Sep 12, 2015 at 5:54 AM, Teun Docter
> <teun.docter at brightcomputing.com> wrote:
>> On 2015-09-12 04:58, Gene Cumm wrote:
>>>>
>>>> I've captured the following DHCP ACK:
>>>>
>>>> 10.141.20.1.bootps > 10.141.20.2.bootpc: [udp sum ok]
2015 Jun 26
3
[PATCH 0/1] Network UEFI PXE DHCP/proxyDHCP fix
from: Jeff Sloan <jeff_sloan at selinc.com>
Update UEFI PXE proxyDHCP handling updated.
This patch is based on commit ID 8a00e49
Updated pxe.c and udp.c to incorporate feedback.In addition to the
previous modifications:
pxe.c: Changed to use ProxyOffer Packet and added client ip from PxeReply
into temp packet for parsing. Left all existing cached packets untouched.
udp.c:
2014 Sep 25
1
UEFI PXE / split config / TFTP attempted to DHCP server, not TFTP server
>Date: Sun, 21 Sep 2014 22:19:12 -0400
>From: Gene Cumm <gene.cumm at gmail.com>
>To: Spike White <spikewhitetx at gmail.com>
>Cc: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com>
>Subject: Re: [syslinux] UEFI PXE / split config / TFTP attempted to
> DHCP server, not TFTP server
>Message-ID:
>
2014 Dec 26
3
Chain-loading from WDS to PXELinux on a different tftp server
> Date: Thu, 25 Dec 2014 07:07:52 +0000
> From: Luke Ledgerd <luke.ledgerd at niteco.se>
> To: "syslinux at zytor.com" <syslinux at zytor.com>
> Subject: [syslinux] Chain-loading from WDS to PXELinux on a different
> tftp server
> Message-ID: <17ba7ad419d54b6cab685c2cedc3de95 at NI-MAILEX.niteco.se>
> Content-Type: text/plain;
2015 Sep 12
2
pxelinux tries to load ldlinux.c32 from DHCP server, instead of next-server
On 2015-09-12 04:58, Gene Cumm wrote:
>> I've captured the following DHCP ACK:
>>
>> 10.141.20.1.bootps > 10.141.20.2.bootpc: [udp sum ok] BOOTP/DHCP, Reply,
>> length 399, xid 0xf0eb955a, secs 14, Flags [none] (0x0000)
>> Your-IP 10.141.20.2
>> Server-IP 10.141.255.254
>> Client-Ethernet-Address fa:16:3e:08:31:b9
2014 Dec 29
0
Chain-loading from WDS to PXELinux on a different tftp server
Thanks for your email. Yes it does provide some insight into why I could hack a Linux DHCP server into providing enough PXE boot information for PXE 3 clients but PXE 2.1 were happy (ROMs under many circumstances need to use proxy dhcp 4011 - as documented by IBM on the link I shared earlier).
It appears only the most latest Dell business systems have EFI 64 support, and the best you can expect
2015 Sep 12
2
pxelinux tries to load ldlinux.c32 from DHCP server, instead of next-server
On Sat, Sep 12, 2015 at 08:42:15AM -0400, Gene Cumm via Syslinux wrote:
> On Sat, Sep 12, 2015 at 7:37 AM, Gene Cumm <gene.cumm at gmail.com> wrote:
> > On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote:
> >> On Sat, Sep 12, 2015 at 5:54 AM, Teun Docter
> >> <teun.docter at brightcomputing.com> wrote:
> >>> On
2015 Jun 11
2
[PATCH 0/1] Network UEFI PXE DHCP/proxyDHCP fix
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.
In efi/pxe.c: In net_parse_dhcp function.
If ProxyOffer has been received, start with DhcpAck packet since it is the
most complete. This requires a minimum of changes to the
2004 Apr 30
1
Novell DHCP and Pxelinux
Hello Friends,
once more.
We got pxelinux run with win 2000 dhcp. It works really fine.
there a not problems at all.
Now we want to get it run also under novell, but we want to use
the novell dhcp, we don't need the tftpd from novell, we want to use
a tfptd on another machine (a simple micrsoft tfptd).
As we found out, novell does not support the dhcp options (67 = bootserver,
68 =
2015 Oct 07
4
UEFI: Failed to load ldlinux.e64/ldlinux.e32
On Wed, Oct 7, 2015 at 6:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
>> -----Original Message-----
>> From: Gene Cumm [mailto:gene.cumm at gmail.com]
>> Sent: Wednesday, October 07, 2015 4:43 PM
>> To: For discussion of Syslinux and tftp-hpa; Geert Stappers
>> Subject: Re: [syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32
>>
>> On Wed, Oct
2015 Sep 12
0
pxelinux tries to load ldlinux.c32 from DHCP server, instead of next-server
On Sat, Sep 12, 2015 at 7:37 AM, Gene Cumm <gene.cumm at gmail.com> wrote:
> On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote:
>> On Sat, Sep 12, 2015 at 5:54 AM, Teun Docter
>> <teun.docter at brightcomputing.com> wrote:
>>> On 2015-09-12 04:58, Gene Cumm wrote:
>>>>>
>>>>> I've captured the
2015 Jun 07
2
EFI and proxyDHCP: setups
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
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 Jan 11
3
PXE Booting EFI
>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 = "efi"
> I see:
> option-93 = 0x07
> option-60 ="PXEClient:Arch:00007:UNDI:003016"
OK I take
2015 Sep 12
0
pxelinux tries to load ldlinux.c32 from DHCP server, instead of next-server
On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers <stappers at stappers.nl> wrote:
> On Sat, Sep 12, 2015 at 08:42:15AM -0400, Gene Cumm via Syslinux wrote:
>> On Sat, Sep 12, 2015 at 7:37 AM, Gene Cumm <gene.cumm at gmail.com> wrote:
>> > On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote:
>> >> On Sat, Sep 12, 2015 at 5:54 AM,
2015 Jun 24
0
[Announce] Samba 4.1.19 Available for Download
Hello Ira,
Great! You are right!
Through Chrome browser on my win7 and win8.1 got size 90MB tarball,
through wget on my ubuntu got size 19MB gzipped file,
thank you Ira and Karolin,
great samba work!
[~] # wget https://download.samba.org/pub/samba/stable/samba-4.1.19.tar.gz
--no-check-certificate
...
[~] # file samba-4.1.19.tar.gz
samba-4.1.19.tar.gz: gzip compressed data, was
2015 Jan 10
0
PXE Booting EFI
On Sat, Jan 10, 2015 at 5:44 AM, Patrick Masotta <masottaus at yahoo.com> wrote:
>> I use Syslinux 6.03 EFI64 on a VMware Workstation 10 VM on
>> 10.0.2 on Linux.
>>
> w/o any problem?
Yes.
> Me too, I just send the ""corresponding"" syslinux.efi
>> Are they actually transferring the syslinux.efi files?
>
> sure
>
>> What
2015 Jun 24
2
[Announce] Samba 4.1.19 Available for Download
I show the file size as 19M on the FTP site.
95MB is the gunzipped size. I suspect something unzipped it as it
downloaded, I've seen browsers do that.
I also pulled the file personally, and found the sizes lined up:
ira at ira-t430:~/Downloads
[/dev/pts/1](64/0)$ ls -la samba-4.1.19.tar.gz
-rw-rw-r--. 1 ira ira 19558250 Jun 23 20:16 samba-4.1.19.tar.gz
ira at ira-t430:~/Downloads
2015 Oct 09
1
syslinux64.efi boot problems
Hi there,
I've been trying to boot some new machines via uEFI and it does not work, as you can see below. From my hunting around on the mailing list, there may have been a bunch of fixes that have been committed that have some bearing on uEFI, and even some on the mailing list that appear to be aimed at solving similar problems. However, I can't manage to build a new one based on the