Jump to content











Photo

Bug Reports, Requests, HowTo's about Tiny PXE Server

pxe network boot

  • Please log in to reply
835 replies to this topic

#176 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 06 September 2014 - 12:09 PM

Oki it seems my idea of renaming the boot file is not very popular :)

 

I will take this into account then probably with a parameter in the config.ini

Thinking of a section like the below :

[arch]
00006=bootia32.efi
00007=bootx64.efi

The arch=00000 case does not need to go thru a parameter since this is the default boot filename (or opt67).



#177 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 06 September 2014 - 01:28 PM

very good! thanks!
notice,permit use relative path as 00007=efi\boot\bootx64.efi

let the bootfile to decide which BCD will be used.

I'm very glad to test your new version! expect anxiously!

Edited by hhh333, 06 September 2014 - 01:35 PM.


#178 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 06 September 2014 - 02:23 PM

very good! thanks!
notice,permit use relative path as 00007=efi\boot\bootx64.efi

let the bootfile to decide which BCD will be used.

I'm very glad to test your new version! expect anxiously!

 

to point to a specific BCD, I advise to use option 252



#179 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 06 September 2014 - 06:19 PM

oh,this is a not clever method by rename bootfile name to XXX.@arch.please improve like this

if @arch=00000(or NULL or not define @arch) bootfilename=pxelinux.0
.......
if @arch=00006 bootfilename=efi\boot\bootia32.efi
if @arch=00007 bootfilename=efi\boot\bootx64.efi
.....

so,let user to define a independent bootfile for every @arch.

 

Ok, binary updated (redownload).

 

One can add the following section in the config.ini :

 
[arch]
00006=bootia32.efi
00007=bootx64.efi
 
This way when Tiny PXE Server detects a specific client architecture, it will over rule the default boot filename and replace it by the one specified in the ini file.
 
Not sure it supports relative path for now (did not test...).


#180 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 06 September 2014 - 06:55 PM

See below an example of booting over BIOS or UEFI.

 

Below Tiny PXE Server will send pxeboot.n12 as boot filename (which will chain to bootmgr) and will indicate 00000\bcd as BCD file in BIOS mode.

 

If UEFI x64 (00007) is detected, and [arch] section filled, it will send bootx64.efi as boot filename and will indicate 00007\bcd as BCD.

 

gHw9sxp.png



#181 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 09 September 2014 - 07:03 AM

I tested,but fail on boot EFI client.

this is my config.ini

[arch]
00006=efi\boot\bootia32.efi
00007=efi\boot\bootx64.efi
[dhcp]
httpd=1
binl=0
start=1
tftpd=0
proxydhcp=1
bind=1
smb=0
Root=c:
Opt17=c:\
Filename=pxelinux.0

this is my log (pxeclient is EFI):

14:36:46 ROOT=c:\
14:36:46 DHCPd:67 started...
14:36:46 DHCPd:4011 started...
14:36:46 TFPTd started...
14:36:46 HTTPd started...
14:37:05 DHCPd:DISCOVER received, MAC:00-0C-29-E3-62-A6, XID:2E3D6BED
14:37:05 DHCPd:OFFER sent, IP:0.0.0.0, XID:2E3D6BED
14:37:08 DHCPd:REQUEST discarded, MAC:00-0C-29-E3-62-A6, XID:2E3D6BED
14:37:08 PDHCPd:REQUEST received, MAC:00-0C-29-E3-62-A6, IP:192.168.10.116, XID:3556A5A1
14:37:09 Proxy boot filename empty?
14:37:09 PDHCPd:DHCP_ACK sent, IP:192.168.10.116:4011, xid:3556A5A1
14:37:09 TFTPd:DoReadFile:efi\boot\bootx64.efi B:1468 T:0

EFI client boot fail.the all need files is in C:\.then I move bootx64.efi to C:\,change config.ini,fail too.

 

in the same time,boot success from a bios client.the log like  this:

14:50:19 ROOT=c:\
14:50:19 DHCPd:67 started...
14:50:19 DHCPd:4011 started...
14:50:19 TFPTd started...
14:50:19 HTTPd started...
14:50:33 DHCPd:DISCOVER received, MAC:00-0C-29-57-59-93, XID:2A575993
14:50:34 DHCPd:OFFER sent, IP:0.0.0.0, XID:2A575993
14:50:35 DHCPd:REQUEST discarded, MAC:00-0C-29-57-59-93, XID:2A575993
14:50:36 PDHCPd:REQUEST received, MAC:00-0C-29-57-59-93, IP:192.168.10.124, XID:2A575993
14:50:36 Proxy boot filename empty?
14:50:36 PDHCPd:DHCP_ACK sent, IP:192.168.10.124:68, xid:2A575993
14:50:36 TFTPd:DoReadFile:pxelinux.0 B:1456 T:0
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\564dbb9b-1a82-6e90-b539-ec79fb575993". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\01-00-0c-29-57-59-93". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A80A7C". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A80A7". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A80A". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A80". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A8". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C". 系统找不到指定的文件。
14:50:36 TFTPd:DoReadFile:BOOT/LNX.CFG/default B:1408 T:1549
14:50:36 TFTPd:DoReadFile:/boot/isolinux/vesamenu.c32 B:1408 T:154128
14:50:36 TFTPd:DoReadFile:BOOT/LNX.CFG/default B:1408 T:1549
14:50:36 TFTPd:DoReadFile:/BOOT/LNX.CFG/BACK.JPG B:1408 T:68256

and in same case,use Hanewin,bios and efi can boot success.



#182 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 09 September 2014 - 07:12 AM

I tested,but fail on boot EFI client.

this is my config.ini

[arch]
00006=efi\boot\bootia32.efi
00007=efi\boot\bootx64.efi
[dhcp]
httpd=1
binl=0
start=1
tftpd=0
proxydhcp=1
bind=1
smb=0
Root=c:
Opt17=c:\
Filename=pxelinux.0

this is my log (pxeclient is EFI):

14:36:46 ROOT=c:\
14:36:46 DHCPd:67 started...
14:36:46 DHCPd:4011 started...
14:36:46 TFPTd started...
14:36:46 HTTPd started...
14:37:05 DHCPd:DISCOVER received, MAC:00-0C-29-E3-62-A6, XID:2E3D6BED
14:37:05 DHCPd:OFFER sent, IP:0.0.0.0, XID:2E3D6BED
14:37:08 DHCPd:REQUEST discarded, MAC:00-0C-29-E3-62-A6, XID:2E3D6BED
14:37:08 PDHCPd:REQUEST received, MAC:00-0C-29-E3-62-A6, IP:192.168.10.116, XID:3556A5A1
14:37:09 Proxy boot filename empty?
14:37:09 PDHCPd:DHCP_ACK sent, IP:192.168.10.116:4011, xid:3556A5A1
14:37:09 TFTPd:DoReadFile:efi\boot\bootx64.efi B:1468 T:0

EFI client boot fail.the all need files is in C:\.then I move bootx64.efi to C:\,change config.ini,fail too.

 

in the same time,boot success from a bios client.the log like  this:

14:50:19 ROOT=c:\
14:50:19 DHCPd:67 started...
14:50:19 DHCPd:4011 started...
14:50:19 TFPTd started...
14:50:19 HTTPd started...
14:50:33 DHCPd:DISCOVER received, MAC:00-0C-29-57-59-93, XID:2A575993
14:50:34 DHCPd:OFFER sent, IP:0.0.0.0, XID:2A575993
14:50:35 DHCPd:REQUEST discarded, MAC:00-0C-29-57-59-93, XID:2A575993
14:50:36 PDHCPd:REQUEST received, MAC:00-0C-29-57-59-93, IP:192.168.10.124, XID:2A575993
14:50:36 Proxy boot filename empty?
14:50:36 PDHCPd:DHCP_ACK sent, IP:192.168.10.124:68, xid:2A575993
14:50:36 TFTPd:DoReadFile:pxelinux.0 B:1456 T:0
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\564dbb9b-1a82-6e90-b539-ec79fb575993". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\01-00-0c-29-57-59-93". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A80A7C". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A80A7". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A80A". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A80". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A8". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0A". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C0". 系统找不到指定的文件。
14:50:36 TFTPd:OpenError:Cannot open file "c:\BOOT\LNX.CFG\C". 系统找不到指定的文件。
14:50:36 TFTPd:DoReadFile:BOOT/LNX.CFG/default B:1408 T:1549
14:50:36 TFTPd:DoReadFile:/boot/isolinux/vesamenu.c32 B:1408 T:154128
14:50:36 TFTPd:DoReadFile:BOOT/LNX.CFG/default B:1408 T:1549
14:50:36 TFTPd:DoReadFile:/BOOT/LNX.CFG/BACK.JPG B:1408 T:68256

anY in same case,use Hanewin,bios and efi can boot success.

 

I am not sure about relative paths... (i.e I am pretty sure this is the issue...).

Can you put bootx64.efi in the root folder (next to pxelinux.0) rather than root_folder\efi\boot\bootx64.efi ?

 

OPT17=c:\ is wrong as well : it should be a dhcp root path (for iscsi, aoe, etc) not a file root path.

Yeave it empty, you dont need it.

 

And I would advise tftpd=1 instead of tftpd=0.

You can of course use another tftp daemon but Tiny PXE Server can do it fine.



#183 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 09 September 2014 - 07:44 AM

Yes,I place bootx64.efi to root folder(as pxelinux.0,all in C:\ on my server) and in config.ini changed like so:

[arch]
00006=bootia32.efi
00007=bootx64.efi
......

 

but fail too!



#184 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 09 September 2014 - 07:55 AM

Have you config.ini  look like below (exactly, with the lines in that order).

Notice root=c:\ instead of c:.

 

Test it from BIOS and UEFI and copy paste each log here please.

 

If arch 00007 is detected, the boot sequence should be as is : uefi->bootx64.efi->bcd->[boot.wim]\winload.efi.

 

Make sure that no other tftp/dhcp daemon runs on your system.

 

Thanks.

[arch]
00006=bootia32.efi
00007=bootx64.efi
[dhcp]
Root=c:\
Filename=pxelinux.0
httpd=1
binl=0
tftpd=1
proxydhcp=1
bind=1
smb=0
start=1
;Opt17=


#185 ljycslg

ljycslg

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 09 September 2014 - 08:48 AM

manual select other efi bootfile(such as ipxe.efi)  is invaild use the [arch] section



#186 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 09 September 2014 - 09:03 AM

manual select other efi bootfile(such as ipxe.efi)  is invaild use the [arch] section

 

Hi ljycslg,

 

The [arch] section, if exists, over rules any other filename parameter (in the config.ini or manual).

 

If no [arch] section, one can select any filename (efi or not), and Tiny PXE Server will then send the selected filename.

 

Regards,

Erwan



#187 ljycslg

ljycslg

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 09 September 2014 - 09:16 AM

Hi ljycslg,

 

The [arch] section, if exists, over rules any other filename parameter (in the config.ini or manual).

 

If no [arch] section, one can select any filename (efi or not), and Tiny PXE Server will then send the selected filename.

 

Regards,

Erwan

manual  should have highest rules



#188 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 09 September 2014 - 09:27 AM

manual  should have highest rules

 

I dont know if it should but it definitely could.

 

My issue is the following :

-I try to make the GUI as simple as possible so that PXE booting is made easy

-I try to offer as many parameters possible with a logic comparable to "if this then that" which you can find in linux dhcp daemons such as dnsmasq.

 

In short :

-a basic user should just have to click "online" and it should work

-an advanced user should be able to customize at will his PXE booting process (support ipxe/gpxe user class, support for client architecture, etc).

 

Regards,

Erwan



#189 ljycslg

ljycslg

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 09 September 2014 - 09:45 AM

the newest version 

use filename=boot.@arch  can not boot

17:41:31 ROOT=E:\pe\AMD64\media\\
17:41:31 DHCPd:67 started...
17:41:31 DHCPd:4011 started...
17:41:31 TFPTd started...
17:41:31 HTTPd started...
17:41:36 DHCPd:DISCOVER received, MAC:00-15-5D-03-13-03, XID:5E031303
17:41:36 DHCPd:OFFER sent, IP:0.0.0.0, XID:5E031303
17:41:40 DHCPd:REQUEST discarded, MAC:00-15-5D-03-13-03, XID:5E031303
17:41:40 PDHCPd:REQUEST received, MAC:00-15-5D-03-13-03, IP:192.168.3.107, XID:5E031303
17:41:40 analysedata4011:Access violation at address 004C37F7 in module 'pxesrv.exe'. Read of address 00000008
17:41:48 DHCPd:RELEASE received, MAC:00-15-5D-03-13-03, XID:5E031303
17:41:48 DHCPd:DISCOVER received, MAC:00-15-5D-03-13-03, XID:5F031303
17:41:48 DHCPd:OFFER sent, IP:0.0.0.0, XID:5F031303
17:41:56 DHCPd:REQUEST discarded, MAC:00-15-5D-03-13-03, XID:5F031303
17:41:56 PDHCPd:REQUEST received, MAC:00-15-5D-03-13-03, IP:192.168.3.107, XID:5F031303
17:41:56 analysedata4011:Access violation at address 004C37F7 in module 'pxesrv.exe'. Read of address 00000008



#190 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 09 September 2014 - 09:54 AM

My issue is the following :

-I try to make the GUI as simple as possible so that PXE booting is made easy

-I try to offer as many parameters possible with a logic comparable to "if this then that" which you can find in linux dhcp daemons such as dnsmasq.

 

In short :

-a basic user should just have to click "online" and it should work

-an advanced user should be able to customize at will his PXE booting process (support ipxe/gpxe script, support for client architecture, etc).

erwan.l, you do know how I personally hold you in the highest esteem :), but the above makes no sense :w00t: :ph34r:.

 

That usage paradigm is valid for something that has ONLY basic and advanced users, but this is NOT the case for users of a pxe server program.

 

I just invented   :w00t: these poll statistics for your use:

Which kind of user would you define yourself (related with your experience with pxe servers and speciifically with Tiny Pxe Server)?

  • Basic user 2.18%
  • Intermediate user 61.89%
  • Advanced user 35.93%

 

Upon verification of the data, the corrected data are:

 

  • Basic user 2.15%
  • Intermediate user 88.49%
  • Advanced user 9.36%

The corrections were needed because 0.03% of responders underestimated their level answering "Basic user" while they actually belonged to "Intermediate" and because a mere 26,57% of "Advanced users" were plainly lying. ;)

 

The most voted answers to the question "What do you think Tiny Pxe Server is missing currently/Which feature would you like to have added to it?" were different by User level:

  • Basic user: Nothing, it's really fine, LOL.  :P
  • Intermediate user: A friggin' manual, what else? There are a ziliion options and each one needs hours of §@ç#ing reading across half the internet to be made actually usable/working. :frusty:
  • Advanced user: Tele-para-mega cross-compatibility between Solaris 9 and tethered Android devices autodetection when initiated through a peer-to-peer network by means of asynchronous encrypted packets sent through a VPN.  :smiling9:

 

:duff:

Wonko



#191 hhh333

hhh333

    Newbie

  • Members
  • 26 posts
  •  
    China

Posted 09 September 2014 - 03:39 PM

 

Have you config.ini  look like below (exactly, with the lines in that order).

Notice root=c:\ instead of c:.

 

Test it from BIOS and UEFI and copy paste each log here please.

 

If arch 00007 is detected, the boot sequence should be as is : uefi->bootx64.efi->bcd->[boot.wim]\winload.efi.

 

Make sure that no other tftp/dhcp daemon runs on your system.

 

Thanks.

[arch]
00006=bootia32.efi
00007=bootx64.efi
[dhcp]
Root=c:\
Filename=pxelinux.0
httpd=1
binl=0
tftpd=1
proxydhcp=1
bind=1
smb=0
start=1
;Opt17=

 root=c:\ instead of c:, the log display "root=c:\\,and then boot fail,too.



#192 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 09 September 2014 - 04:21 PM

 

 

Have you config.ini  look like below (exactly, with the lines in that order).

Notice root=c:\ instead of c:.

 

Test it from BIOS and UEFI and copy paste each log here please.

 

If arch 00007 is detected, the boot sequence should be as is : uefi->bootx64.efi->bcd->[boot.wim]\winload.efi.

 

Make sure that no other tftp/dhcp daemon runs on your system.

 

Thanks.

[arch]
00006=bootia32.efi
00007=bootx64.efi
[dhcp]
Root=c:\
Filename=pxelinux.0
httpd=1
binl=0
tftpd=1
proxydhcp=1
bind=1
smb=0
start=1
;Opt17=

 root=c:\ instead of c:, the log display "root=c:\\,and then boot fail,too.

 

 

ok.

please send me the entire output of the log window.

just got home : trying to reproduce this bug.



#193 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 09 September 2014 - 04:57 PM

Well I could not reproduce your bug :(
Could it be a permission issue on your side on files? root of C drive is may be not the right place?

See below a screenshot (E:\ is an imdisk)

4KD1CMo.png

Below my log file.
Dont pay attention to the "cannot open file" : these are not necessary to boot.

19:20:55 ROOT=e:\\
19:20:55 DHCPd:67 started...
19:20:55 DHCPd:4011 started...
19:20:55 TFPTd started...
19:20:56 HTTPd started...
19:20:56 DHCPd:DISCOVER received, MAC:28-D2-44-82-B7-02, XID:5E883711
19:20:57 DHCPd:OFFER sent, IP:0.0.0.0, XID:5E883711
19:21:04 DHCPd:REQUEST discarded, MAC:28-D2-44-82-B7-02, XID:5E883711
19:21:04 PDHCPd:REQUEST received, MAC:28-D2-44-82-B7-02, IP:192.168.1.115, XID:430B15A1
19:21:05 Proxy boot filename empty?
19:21:05 PDHCPd:DHCP_ACK sent, IP:192.168.1.115:4011, xid:430B15A1
19:21:05 TFTPd:DoReadFile:bootx64.efi B:1468 T:0
19:21:06 TFTPd:DoReadFile:bootx64.efi B:1468 T:0
19:21:06 TFTPd:OpenError:Cannot open file "e:\BCD". Le fichier spécifié est introuvable
19:21:06 TFTPd:DoReadFile:\00007\bcd B:0 T:262144
19:21:06 TFTPd:DoReadFile:\00007\bcd B:1456 T:262144
19:21:06 TFTPd:OpenError:Cannot open file "e:\en-US\bootx64.efi.MUI". Le chemin d’accès spécifié est introuvable
19:21:06 TFTPd:DoReadFile:\bootx64.efi B:0 T:1616728
19:21:06 TFTPd:DoReadFile:\bootx64.efi B:1456 T:1616728
19:21:08 TFTPd:DoReadFile:\sources\boot.wim B:0 T:237224692
19:21:08 TFTPd:DoReadFile:\boot\boot.sdi B:0 T:3170304
19:21:08 TFTPd:OpenError:Cannot open file "e:\EFI\Microsoft\Boot\fonts\segoe_slboot.ttf". Le chemin d’accès spécifié est introuvable
19:21:08 TFTPd:OpenError:Cannot open file "e:\EFI\Microsoft\Boot\fonts\segmono_boot.ttf". Le chemin d’accès spécifié est introuvable
19:21:08 TFTPd:OpenError:Cannot open file "e:\EFI\Microsoft\Boot\resources\bootres.dll". Le chemin d’accès spécifié est introuvable
19:21:08 TFTPd:OpenError:Cannot open file "e:\EFI\Microsoft\Boot\fonts\wgl4_boot.ttf". Le chemin d’accès spécifié est introuvable
19:21:08 TFTPd:OpenError:Cannot open file "e:\EFI\Microsoft\Boot\fonts\wgl4_boot.ttf". Le chemin d’accès spécifié est introuvable
19:21:08 TFTPd:DoReadFile:\boot\boot.sdi B:1456 T:3170304
19:21:10 TFTPd:OpenError:Cannot open file "e:\EFI\Microsoft\Boot\resources\bootres.dll". Le chemin d’accès spécifié est introuvable
19:21:10 TFTPd:DoReadFile:\sources\boot.wim B:1456 T:237224692


#194 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 09 September 2014 - 05:41 PM

erwan.l, you do know how I personally hold you in the highest esteem :), but the above makes no sense :w00t: :ph34r:.

 

That usage paradigm is valid for something that has ONLY basic and advanced users, but this is NOT the case for users of a pxe server program.

 

I just invented   :w00t: these poll statistics for your use:

Which kind of user would you define yourself (related with your experience with pxe servers and speciifically with Tiny Pxe Server)?

  • Basic user 2.18%
  • Intermediate user 61.89%
  • Advanced user 35.93%

 

Upon verification of the data, the corrected data are:

 

  • Basic user 2.15%
  • Intermediate user 88.49%
  • Advanced user 9.36%

The corrections were needed because 0.03% of responders underestimated their level answering "Basic user" while they actually belonged to "Intermediate" and because a mere 26,57% of "Advanced users" were plainly lying. ;)

 

The most voted answers to the question "What do you think Tiny Pxe Server is missing currently/Which feature would you like to have added to it?" were different by User level:

  • Basic user: Nothing, it's really fine, LOL.  :P
  • Intermediate user: A friggin' manual, what else? There are a ziliion options and each one needs hours of §@ç#ing reading across half the internet to be made actually usable/working. :frusty:
  • Advanced user: Tele-para-mega cross-compatibility between Solaris 9 and tethered Android devices autodetection when initiated through a peer-to-peer network by means of asynchronous encrypted packets sent through a VPN.  :smiling9:

 

:duff:

Wonko

 

A compliment should never be followed by a "but  B)

Kindof saying to your wife "you have a nice pant but it makes your ass big"  :ph34r:

 

Coming back to your statement, allow me to discuss your numbers.

Not on the ratio but on your logic :

-majority of pxe users are intermediate users

-intermediate users want a documentation

-therefore, i shall do a documentation

 

I may be wrong but this logic may fall into the "sophism" category.

 

Or I might simply be lazy and try to escape writing a documentation :)



#195 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 09 September 2014 - 06:12 PM

A compliment should never be followed by a "but  B)

Kindof saying to your wife "you have a nice pant but it makes your ass big"  :ph34r:

 

Well, that isn't something you should mention, not even joking,  as the consequences (if overheard/overread by a wife, anyone's wife) may be terrible. :w00t:

 

A good rule of the thumb is to NOT EVEN THINK about something like that, as if she has her ESP receiver on you would get in trouble in no time ;).

 

 

 

Or I might simply be lazy and try to escape writing a documentation  :)

Yep, that would be a possibility. :)

 

On the concept behind the fake percentages, however, I am serious, I am pretty sure that a number of people that want to go a bit beyond the "plain settings" BUT that don't want to get familiar with the whole set of:

 

RFC 2132: http://datatracker.i...rg/doc/rfc2132/
RFC 3046: http://datatracker.i...rg/doc/rfc3046/
RFC 3495: http://datatracker.i...rg/doc/rfc3495/
RFC 3646: http://datatracker.i...rg/doc/rfc3646/

RFC 4578: http://datatracker.i...rg/doc/rfc4578/
RFC 4704: http://datatracker.i...rg/doc/rfc4704/

 

(and who knows what else :w00t: :ph34r:)

 

A simple table (but dedicated to Tiny Pxe Server) similar in layout to this page:

http://www.incognito...-plain-english/

would IMHO be useful, as well as a few, selected, examples of use.

 

:duff:

Wonko



#196 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 09 September 2014 - 07:55 PM

Well, that isn't something you should mention, not even joking,  as the consequences (if overheard/overread by a wife, anyone's wife) may be terrible. :w00t:

 

A good rule of the thumb is to NOT EVEN THINK about something like that, as if she has her ESP receiver on you would get in trouble in no time ;).

 

 

 

Yep, that would be a possibility. :)

 

On the concept behind the fake percentages, however, I am serious, I am pretty sure that a number of people that want to go a bit beyond the "plain settings" BUT that don't want to get familiar with the whole set of:

 

RFC 2132: http://datatracker.i...rg/doc/rfc2132/
RFC 3046: http://datatracker.i...rg/doc/rfc3046/
RFC 3495: http://datatracker.i...rg/doc/rfc3495/
RFC 3646: http://datatracker.i...rg/doc/rfc3646/

RFC 4578: http://datatracker.i...rg/doc/rfc4578/
RFC 4704: http://datatracker.i...rg/doc/rfc4704/

 

(and who knows what else :w00t: :ph34r:)

 

A simple table (but dedicated to Tiny Pxe Server) similar in layout to this page:

http://www.incognito...-plain-english/

would IMHO be useful, as well as a few, selected, examples of use.

 

:duff:

Wonko

 

A file summing all dhcp options handled by Tiny PXE Server is a good idea : job done, now included in the zip file.

And also here.

 

Note that the first post in this thread indicates :

-where to find documentation around the config.ini (also in the zip file thru a config.sample)

-where to find practical examples (also in the zip file)

-and now where to find doc around the dhcp options (also in the zip file)



#197 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 09 September 2014 - 10:00 PM

the newest version 
use filename=boot.@arch  can not boot

17:41:31 ROOT=E:\pe\AMD64\media\\
17:41:31 DHCPd:67 started...
17:41:31 DHCPd:4011 started...
17:41:31 TFPTd started...
17:41:31 HTTPd started...
17:41:36 DHCPd:DISCOVER received, MAC:00-15-5D-03-13-03, XID:5E031303
17:41:36 DHCPd:OFFER sent, IP:0.0.0.0, XID:5E031303
17:41:40 DHCPd:REQUEST discarded, MAC:00-15-5D-03-13-03, XID:5E031303
17:41:40 PDHCPd:REQUEST received, MAC:00-15-5D-03-13-03, IP:192.168.3.107, XID:5E031303
17:41:40 analysedata4011:Access violation at address 004C37F7 in module 'pxesrv.exe'. Read of address 00000008
17:41:48 DHCPd:RELEASE received, MAC:00-15-5D-03-13-03, XID:5E031303
17:41:48 DHCPd:DISCOVER received, MAC:00-15-5D-03-13-03, XID:5F031303
17:41:48 DHCPd:OFFER sent, IP:0.0.0.0, XID:5F031303
17:41:56 DHCPd:REQUEST discarded, MAC:00-15-5D-03-13-03, XID:5F031303
17:41:56 PDHCPd:REQUEST received, MAC:00-15-5D-03-13-03, IP:192.168.3.107, XID:5F031303
17:41:56 analysedata4011:Access violation at address 004C37F7 in module 'pxesrv.exe'. Read of address 00000008


Access violation is not good.
I may have introduced a bug under certain circumstances in latest version.
Let me come back to that one very soon.

#198 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 10 September 2014 - 07:15 AM

A file summing all dhcp options handled by Tiny PXE Server is a good idea : job done, now included in the zip file.

 

Good :thumbsup:, BUT not enough :whistling:.

 

You cannot post here:

http://reboot.pro/to...e-7#entry186669

a reference to RFC4578 (that if I get it right is about options #93 #94 and #97 :unsure:),

 

then put in the GUI "Option 252 Private" in the "BINL" part with the @arch "variable"

 

and then get away in the "DHCP options that can be set in config.ini" table with a simple:

 

252 Private Individual vendors can define different pieces of data that may be found in this option,

 

 

That is exactly the kind of "scatttering" of the info that I was trying to highlight :frusty:.

 

If you could make a table similar to the "DHCP options table" with a few added columns on the right *like*:

  1. How this is used in tinyPXE
  2. Example values for ( a few examples as in the post here http://reboot.pro/to...iny-pxe-server/ )

it would IMHO represent a compact resource, easy to follow and easy to visually compare for the various possibilities.

 

:duff:

Wonko



#199 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 12 September 2014 - 06:29 PM

Good :thumbsup:, BUT not enough :whistling:.

 

You cannot post here:

http://reboot.pro/to...e-7#entry186669

a reference to RFC4578 (that if I get it right is about options #93 #94 and #97 :unsure:),

 

then put in the GUI "Option 252 Private" in the "BINL" part with the @arch "variable"

 

and then get away in the "DHCP options that can be set in config.ini" table with a simple:

 

 

That is exactly the kind of "scatttering" of the info that I was trying to highlight :frusty:.

 

If you could make a table similar to the "DHCP options table" with a few added columns on the right *like*:

  1. How this is used in tinyPXE
  2. Example values for ( a few examples as in the post here http://reboot.pro/to...iny-pxe-server/ )

it would IMHO represent a compact resource, easy to follow and easy to visually compare for the various possibilities.

 

:duff:

Wonko

 

Good thing  you are pushing me.

I will review it all and will come with a documentation (probably online) summing all docs and informations provided so far.



#200 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2756 posts
  • Location:Nantes - France
  •  
    France

Posted 12 September 2014 - 06:37 PM

 

the newest version 

use filename=boot.@arch  can not boot

17:41:31 ROOT=E:\pe\AMD64\media\\
17:41:31 DHCPd:67 started...
17:41:31 DHCPd:4011 started...
17:41:31 TFPTd started...
17:41:31 HTTPd started...
17:41:36 DHCPd:DISCOVER received, MAC:00-15-5D-03-13-03, XID:5E031303
17:41:36 DHCPd:OFFER sent, IP:0.0.0.0, XID:5E031303
17:41:40 DHCPd:REQUEST discarded, MAC:00-15-5D-03-13-03, XID:5E031303
17:41:40 PDHCPd:REQUEST received, MAC:00-15-5D-03-13-03, IP:192.168.3.107, XID:5E031303
17:41:40 analysedata4011:Access violation at address 004C37F7 in module 'pxesrv.exe'. Read of address 00000008
17:41:48 DHCPd:RELEASE received, MAC:00-15-5D-03-13-03, XID:5E031303
17:41:48 DHCPd:DISCOVER received, MAC:00-15-5D-03-13-03, XID:5F031303
17:41:48 DHCPd:OFFER sent, IP:0.0.0.0, XID:5F031303
17:41:56 DHCPd:REQUEST discarded, MAC:00-15-5D-03-13-03, XID:5F031303
17:41:56 PDHCPd:REQUEST received, MAC:00-15-5D-03-13-03, IP:192.168.3.107, XID:5F031303
17:41:56 analysedata4011:Access violation at address 004C37F7 in module 'pxesrv.exe'. Read of address 00000008

 

 

bug fix in latest version.

 

tiny pxe server was crashing in the [arch] section was missing in config.ini.

 

below the setup to boot over BIOS and/or UEFI.

 

;in config.ini

[arch]
00006=bootia32.efi
00007=bootx64.efi

 

gHw9sxp.png







Also tagged with one or more of these keywords: pxe, network boot

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users