Jump to content











Photo

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

pxe network boot

  • Please log in to reply
898 replies to this topic

#876 erwan.l

erwan.l

    Platinum Member

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

Posted 28 February 2021 - 05:17 PM

minor update : i have updated Tiny PXE Server package with latest iPxe 1.21.1 and Wimboot 2.7.2.

 

kKbyo3j.png



#877 wimb

wimb

    Platinum Member

  • Developer
  • 3749 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 01 March 2021 - 08:04 AM

minor update : i have updated Tiny PXE Server package with latest iPxe 1.21.1 and Wimboot 2.7.2.

 

kKbyo3j.png

 

I think Tiny PXE Server package is not yet updated at the reboot.pro download location and also not at your website or am I wrong  :unsure:

 

I think Tiny PXE Server package is not available at your GitHub site



#878 erwan.l

erwan.l

    Platinum Member

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

Posted 01 March 2021 - 01:19 PM

I think Tiny PXE Server package is not yet updated at the reboot.pro download location and also not at your website or am I wrong  :unsure:

 

I think Tiny PXE Server package is not available at your GitHub site

 

Strange (something i must be doing wrong when refreshing my uploads).

I have refreshed the download section : should be good to go.

 

Files are hosted on my private hosting here and mirrored on github here.

 

I have also updated the first page of this thread to include a link to the download section.



#879 wimb

wimb

    Platinum Member

  • Developer
  • 3749 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 01 March 2021 - 01:56 PM

Strange (something i must be doing wrong when refreshing my uploads).

I have refresh the download section : should be good to go.

 

Files are hosted on my private hosting here and mirrored on github here.

 

I have also updated the first page of this thread to include a link to the download section.

 

pxesrv.zip from GitHub is OK and is the New version.

pxesrv.zip from your website and from reboot.pro is still the old version ....



#880 erwan.l

erwan.l

    Platinum Member

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

Posted 02 March 2021 - 07:31 PM

minor update.

 

-ability to use https web sites as root (http was already supported) -

example : root=https://raw.githubus...rver/main/files

-ability to use js files as server side scripts (next to php, py, bvs)

-added vbs and php dynamic menus (drop a iso/wim file in the web server and use it straight away without adapting the ipxe files)

 

Example of an auto/dynamic generated menu listing all iso's.

 

SACxZk2.png

 

edBudIf.png

pxesrv.exe 
1.0.0.23
02/03/2021 13:52 
F5844CBA41FFEF4DDC8724C993B4E0A6


#881 wimb

wimb

    Platinum Member

  • Developer
  • 3749 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 03 March 2021 - 06:07 AM

How come that Tiny PXE Server from your website is NOT updated ?

 

What is the problem ?



#882 erwan.l

erwan.l

    Platinum Member

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

Posted 03 March 2021 - 10:36 AM

Not sure what you mean.

Could it be a cache issue on your side?

I do have this cache issue in chrome and when this happens, i try my link from another browser.

 

For me it as easy/simple as to upload to my ftp/http server and to github.

 

From there, all web sites pointing to one or the other (like reboot.pro) will/should be OK.

 

My http/ftp server  ( http://erwan.labalec...rver/pxesrv.zip )

 

uguRv9L.png

 

Github  ( https://raw.githubus...main/pxesrv.zip )

 

yhxHUtt.png

 

The content of the zip file (timestamp 02/03/2021 13:52).

 

g4vaciv.png



#883 wimb

wimb

    Platinum Member

  • Developer
  • 3749 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 03 March 2021 - 10:53 AM

The download links for Tiny PXE Server as given above do not work, since link is ending wrongly with ).

 

Tiny PXE Server from your website is 4632 kB and is Old and wrong

Tiny PXE Server from your GitHub  is 5158 kB and is New and OK

 

It is really very strange.

When I use other Windows 10 Or Win10XPE then the download from your website corresponds well to the Tiny PXE Server from GitHub.

I am using Miccrosoft Edge as browser and must see if I can find a way to refresh ....



#884 erwan.l

erwan.l

    Platinum Member

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

Posted 03 March 2021 - 11:10 AM

The download links for Tiny PXE Server as given above do not work, since link is ending wrongly with ).

 

Tiny PXE Server from your website is 4632 kB and is Old and wrong

Tiny PXE Server from your GitHub  is 5158 kB and is New and OK

 

Try yourself to download from your website Tiny PXE Server

 

It is really very strange.

When I use other Windows 10 Or Win10XPE then the download from your website corresponds well to the Tiny PXE Server from GitHub.

I am using Miccrosoft Edge as browser and must see if I can find a way to refresh ....

 

I fixed the links, thanks !

 

I googled a bit and it looks like OVH (my hosting provider) may be the faulty part here.

There is some sort of caching which interferes with fresh uploads.

Some guys out there report that they have to upload the file a dozen times before ovh servers are finally serving the latest version : does not look very square to me :(

If issue remain, I may use github as the unique serving point.

 

The pxesrv.zip you are getting (4632kb) is the old one (before this week).

I am getting a zip file from march 1st...

Latest one should be the one from march 2nd.

And to add some more "strangeness" to this, I am getting different behaviors in different browsers  :wacko:

 

Ultimately, files should be synced everywhere pretty soon .

 

/Erwan



#885 wimb

wimb

    Platinum Member

  • Developer
  • 3749 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 03 March 2021 - 11:18 AM

Clear the Edge Download History solved the issue and Tiny PXE Server from your website is now OK and new version.

 

Ctrl + Shift + Delete in Edge gives dialogue to remove download history



#886 erwan.l

erwan.l

    Platinum Member

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

Posted 03 March 2021 - 11:19 AM

Clear the Edge Download History solved the issue.

 

Ctrl + Shift + Delete in Edge gives dialogue to remove download history

 

I indeed suspect a cache issue somewhere either on the server side (ovh seems to have issues to quickly replicate datas between their servers) and/or on the client side.

 

Glad this is finally sorted out for you :)

 

As always, many thanks for your constructive feedback!


  • wimb likes this

#887 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 03 March 2021 - 01:15 PM

:whistling: ... and - as often happens - something that could have been avoided  :whistling: :

http://reboot.pro/in...c=8480&p=187928

 

Something else to remind for our conversations on the public park bench ;)

http://reboot.pro/in...e=3#entry210530

 

:cheers:

Wonko


  • wimb likes this

#888 erwan.l

erwan.l

    Platinum Member

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

Posted 03 March 2021 - 06:02 PM

:whistling: ... and - as often happens - something that could have been avoided  :whistling: :

http://reboot.pro/in...c=8480&p=187928

 

Something else to remind for our conversations on the public park bench ;)

http://reboot.pro/in...e=3#entry210530

 

:cheers:

Wonko

 

Ah Wonko, long time no speak :)

The public park bench : i'd love to see that happen!

And preferably at your place where the weather (and food, and lots of other things...) is much better (to my taste).

And we dont need to wait to be old for this.

 

Versionning is / has always been my weak point.

And actually I am thinking to use github for this as it does it all for you : versionning, archiving, keeping tracks of changes (when open source), etc.

 

In the meantime, lets blame "caching" :)

 

Take care,

Erwan



#889 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 04 March 2021 - 11:14 AM

In the meantime, lets blame "caching"  :)

 

Take care,

Erwan

Sure :thumbsup: , bad, bad, bad "caching" :chair: or - even better - "voodoo" :wodoo: 

 

:cheers:

Wonko



#890 josywong

josywong
  • Members
  • 5 posts
  •  
    Malaysia

Posted 11 February 2022 - 03:28 AM

thanks for this software.

 

is there any way to manually set tag base on mac address with diff boot file? like how dnsmasq tagging diff bootfile for diff mac add.

 

some problematic "driver" can only boot through ipxe snponly. with manual mac address bootfile, i can simply copy mac address and have it boot through snponly



#891 erwan.l

erwan.l

    Platinum Member

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

Posted 11 February 2022 - 09:34 PM

thanks for this software.
 
is there any way to manually set tag base on mac address with diff boot file? like how dnsmasq tagging diff bootfile for diff mac add.
 
some problematic "driver" can only boot through ipxe snponly. with manual mac address bootfile, i can simply copy mac address and have it boot through snponly


It has been a while and i am not on my computer right now but look at @mac as a variable in your boot filename.
More info in the pxe text file in the zip file.

Cheers,
Erwan

#892 josywong

josywong
  • Members
  • 5 posts
  •  
    Malaysia

Posted 12 February 2022 - 09:25 AM

It has been a while and i am not on my computer right now but look at @mac as a variable in your boot filename.
More info in the pxe text file in the zip file.

Cheers,
Erwan

thanks for the reply.

i checked changelog and this thread.

tried altfilename=@mac.ipxe

and it doesnt work. im stil getting undionly.kpxe from [arch] 00000=undionly.kpxe

 

have not tried to put @mac in [arch] as i need to create every file for every mac.

or am i missing something? mayb folder with bootfile ... ?



#893 erwan.l

erwan.l

    Platinum Member

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

Posted 12 February 2022 - 11:33 AM

thanks for the reply.

i checked changelog and this thread.

tried altfilename=@mac.ipxe

and it doesnt work. im stil getting undionly.kpxe from [arch] 00000=undionly.kpxe

 

have not tried to put @mac in [arch] as i need to create every file for every mac.

or am i missing something? mayb folder with bootfile ... ?

 

example.

I am using @mac in my script filename (file does not exist here hence TPS reporting an error but this is irrelevant here).

You can make @mac part of the filename or part of the path.

 

Qz2y7rn.png


  • josywong likes this

#894 josywong

josywong
  • Members
  • 5 posts
  •  
    Malaysia

Posted 12 February 2022 - 12:18 PM

example.

I am using @mac in my script filename (file does not exist here hence TPS reporting an error but this is irrelevant here).

You can make @mac part of the filename or part of the path.

 

Qz2y7rn.png

thanks. now it worked.

but what happened to other mac address? i have to create new folder for each of them?

 

i dont use undi ipxe, which is why i was asking for one specific mac address to tag for undi ipxe bootfile.

everything else will use [arch] -> bootfile

 

edit: i have some other suggestion. might nt b possible. tag that mac into specific arch, eg. abcdef -> 00000 only.

sometimes there is tat one specific nic tat is nt able to efi boot.


Edited by josywong, 12 February 2022 - 12:35 PM.


#895 erwan.l

erwan.l

    Platinum Member

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

Posted 12 February 2022 - 01:17 PM

thanks. now it worked.

but what happened to other mac address? i have to create new folder for each of them?

 

i dont use undi ipxe, which is why i was asking for one specific mac address to tag for undi ipxe bootfile.

everything else will use [arch] -> bootfile

 

edit: i have some other suggestion. might nt b possible. tag that mac into specific arch, eg. abcdef -> 00000 only.

sometimes there is tat one specific nic tat is nt able to efi boot.

 

Using this @mac variable, you then need to have a script filename for each mac address.

In a small/controlled environement, that may be handy.

In a bigger/not controlled environement, this is probably not practical.

 

Reading you, you need a logic/conditional behavior which only the pxe scripting will achieve i.e : for a specific mac address do this, for everything else do that.

 

Note that instead of @mac, you can also use @arch but I am not sure it will work in your case.

 

/Erwan



#896 josywong

josywong
  • Members
  • 5 posts
  •  
    Malaysia

Posted 13 February 2022 - 03:10 AM

Using this @mac variable, you then need to have a script filename for each mac address.

In a small/controlled environement, that may be handy.

In a bigger/not controlled environement, this is probably not practical.

 

Reading you, you need a logic/conditional behavior which only the pxe scripting will achieve i.e : for a specific mac address do this, for everything else do that.

 

Note that instead of @mac, you can also use @arch but I am not sure it will work in your case.

 

/Erwan

exactly hw u described as nt controlled environment.

i get random hardware(random mac), pxe for diag/deploy os.

some freeze on efi pxe, some need snponly ipxe, some undionly bios.

 

its all good without any better work around available. thanks for reply and tinypxeserver



#897 erwan.l

erwan.l

    Platinum Member

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

Posted 13 February 2022 - 01:54 PM

Well clearly, you should already have TinyPXE Server configured so that it switches between pcbios and efi based on arch.

 

Then you could run some script like below but as is this is not scalable.

 

Thus at this stage, i.e loading an ipxe script, ipxe bootloader is already loaded and your computer could freeze there (while loading the bootloader) hence this is convenient to have TPS choose your bootloader based on some conditions before the boot loader gets loaded.

Unfortunately, while still at the early dhcp stage, there are only a few informations about the client we are being provided with (mac, arch, ip, etc).

 

Rather, I'd say find the proper bootloader, for each arch, that suits them all (undionly and snponly should in theory works mostly everywhere?).

For efi, remember that secureboot is a near "no go" with ipxe (unless you find a signed version).

 

What would help is you telling us where you are encountering issues :

-while loading the bootloader?

-while loading an ipxe script?

-while chaining to wimboot or any other further steps?

#!ipxe
#echo ${mac}
#read test
goto ${mac} || goto start

:00:0c:29:63:45:97
chain custom.ipxe
goto end

:start
chain menu.ipxe
goto end

:end
echo this is the end...

  • josywong likes this

#898 josywong

josywong
  • Members
  • 5 posts
  •  
    Malaysia

Posted 14 February 2022 - 12:45 PM

 

Well clearly, you should already have TinyPXE Server configured so that it switches between pcbios and efi based on arch.

 

Then you could run some script like below but as is this is not scalable.

 

Thus at this stage, i.e loading an ipxe script, ipxe bootloader is already loaded and your computer could freeze there (while loading the bootloader) hence this is convenient to have TPS choose your bootloader based on some conditions before the boot loader gets loaded.

Unfortunately, while still at the early dhcp stage, there are only a few informations about the client we are being provided with (mac, arch, ip, etc).

 

Rather, I'd say find the proper bootloader, for each arch, that suits them all (undionly and snponly should in theory works mostly everywhere?).

For efi, remember that secureboot is a near "no go" with ipxe (unless you find a signed version).

 

What would help is you telling us where you are encountering issues :

-while loading the bootloader?

-while loading an ipxe script?

-while chaining to wimboot or any other further steps?

#!ipxe
#echo ${mac}
#read test
goto ${mac} || goto start

:00:0c:29:63:45:97
chain custom.ipxe
goto end

:start
chain menu.ipxe
goto end

:end
echo this is the end...

yup had been using arch. just came by to say thanks for this piece of software.

might switch to snponly/undionly as u suggest.

[arch]
#00000=undionly.kpxe
00000=grldr
00006=ipxe.efi
#00007=snponly.efi
00007=ipxe64.efi
00009=snponly.efi

this is my current config. edit out arch and restart tinypxeserver when needed



#899 fusionx9

fusionx9
  • Members
  • 1 posts
  •  
    United States

Posted 4 weeks ago

Hi Erwan,

 

I have done my best to read through the various topics at:

 

http://mistyprojects...rver/index.html

 

I have also spent multiple hours reading forums/threads.  I have only gotten Tiny PXE to work with the following settings to boot clients for my WDS server.  I've tried direct booting to my Boot.wim and my test machines just skips PXE booting and goes right to the drive OS.  My transfer speeds are abysmal (Gig Ubitquiti Switches througout) and I can only boot EFI machines.  It would be helpful to boot older machines that are BIOS as well as EFI/Secureboot.  I get an error about how the boot file is too large to fit in memory on BIOS machines.

 

Config.ini:

[arch]
;will over rule the bootp filename or opt67 if the client arch matches one of the below
;00006=bootia32.efi
;00007=bootx64.efi
;00009=bootx64.efi
[dhcp]
;below is applicable only if proxydhcp=0
proxydhcp=1
rfc951=1
;needed to tell TFTPd where is the root folder
root=files
;bootp filename as in http://tools.ietf.org/html/rfc951
;filename=ipxe-undionly.kpxe
filename=ipxe-x86_64.efi
;alternative bootp filename if request comes from ipxe or gpxe
altfilename=ipxe_menu.txt
;start HTTPd
httpd=1
binl=1
start=1
dnsd=0
;if you have a dhcp server on your lan, set proxydhcp=1
proxydhcp=1
;default=1
bind=0
;tftpd=1 by default
;will share (netbios) the root folder as PXE
smb=0
;will log to log.txt
log=1
;opt1=
;opt3=
;opt6=
;opt28=
;opt15=
;opt17=
;opt43=
;opt51=
;opt54=
;opt67=
;opt66=
;opt252=
;poolstart=
;poolsize=
;alternative bootp filename if request comes thru proxydhcp (udp:4011)
;proxybootfilename=
;any extra dhcp options
;my gpxe / ipxe dhcp options
optextra=175.6.1.1.1.8.1.1
;the below will be executed when clicking on the online button
;online=online.bat
;offline=offline.bat
;if log=1, will log to log.txt - not recommended, rather, use the syslog feature
log=0
;syslog=127.0.0.1
[web]
port=80
;php.exe file.php param1=value1
;php-5.6.38-nts-Win32-VC11-x86 tested with success
php=c:\php\php.exe
;cscript.exe file.vbs param1=value1 //nologo
vbs=C:\Windows\System32\cscript.exe
js=C:\Windows\System32\cscript.exe
;python.exe file.py param1=value1
py=C:\Python27\python.exe
;the below will be used if you turn on dnsd
[mydomain.fr]
ip=10.0.0.254
[10.0.0.253]
host=mydomain2.fr
[frmDHCPServer]
top=74
left=1240
[frmAbout]
top=486
left=509

 

Below is my ipxe_menu.txt.

 

#!ipxe
 
#============== Set Variables ===============
set boot-url http://${dhcp-server}
 
#================ Main Menu =================
menu iPXE boot menu
item winpe_iso    WinPE MDTShare_x64 (SANBOOT)
item MemTest86    MemTest86 (SANBOOT)
item wimboot1     Wimboot
choose target && goto ${target}
 
#============ Main Menu Options =============
:winpe_iso
sanboot ${boot-url}/iso/MDTShare_x64.iso
boot
:MemTest86
sanboot ${boot-url}/iso/MemTest86.iso
boot
:wimboot1
kernel ${boot-url}/wimboot pause
initrd -n bootmgr.exe   ${boot-url}/BOOTMGR.EXE     bootmgr.exe ||
initrd -n bootx64.efi   ${boot-url}/BOOTX64.EFI     bootx64.efi ||      
initrd -n bcd           ${boot-url}/BOOT/BCD        bcd
initrd -n boot.sdi      ${boot-url}/BOOT/BOOT.SDI   boot.sdi   
initrd -n boot.wim      ${boot-url}/BOOT/BOOT.WIM   boot.wim
boot
 
When I load my boot.wim using the above menu, it takes forever to load the wim file.  Then once it finally completes after about 100 seconds, I have to hit enter on the keyboard to get it to finishing loading.  This would be nice if it was automatic.  I have used Serva in the past but I am quite fed up with the 4.x iteration and what is now a yearly subscription.  I am hoping to get Tiny PXE to just boot my boot.wim file and maybe a couple ISOs for diagnostics on clients.  Any help is welcome.  
 
Files is my root directory, and it is shared out per instructions in the documentation.  Boot folder has the following:

 

Sources also has theBoot.wim in it under C:\PXESRV\files\Sources and I have some ISO files under C:\PXESRV\files\iso.

 

Any insights are welcome.  I  really appreciate your time, and I am grateful for this tool.

 

Thanks,

FusionX9

 







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