Jump to content











Photo

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

pxe network boot

  • Please log in to reply
909 replies to this topic

#901 Biatu

Biatu

    Member

  • Members
  • 76 posts
  •  
    United Kingdom

Posted 18 November 2022 - 01:04 AM

Can we have an option to not modify the root path to that of the bootfile?
ie, when I set the root path to "RemoteInstall" and set the bootfile to "smsboot\x64\wdsmgfw.efi" and ROOT gets modified "RemoteInstall\smsboot\x64\"
 

Also I don't see any option to set BINL\WDS filename via config.ini



#902 erwan.l

erwan.l

    Platinum Member

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

Posted 18 November 2022 - 05:29 PM

Can we have an option to not modify the root path to that of the bootfile?
ie, when I set the root path to "RemoteInstall" and set the bootfile to "smsboot\x64\wdsmgfw.efi" and ROOT gets modified "RemoteInstall\smsboot\x64\"
 

Also I don't see any option to set BINL\WDS filename via config.ini

 

you mean you have a subfolder in the running directory of PXE named remoteinstall and within remoteinstall you have smsboot\x64 ?

For clarity can you post a screenshot of your file structure?

We can surely sort this out.

 

As of BINL\WDS, let me review that this week end.

 

Cheers,

Erwan



#903 Biatu

Biatu

    Member

  • Members
  • 76 posts
  •  
    United Kingdom

Posted 18 November 2022 - 05:51 PM

Config:

[dhcp]
root=RemoteInstall
filename=smsboot\x64\wdsmgfw.efi

Dir:

pxesrv\RemoteInstall
pxesrv\RemoteInstall\smsboot\x64
pxesrv\RemoteInstall\smsboot\x64\wdsmgfw.efi
pxesrv\RemoteInstall\smsboot\x64\bootmgfw.efi

Also, can you implement an option to proxy/forward tftp/BINL/WDS requests to another machine?

ie, when client requests tftp://<pxesrv>/boot.efi pxesrv requests tftp://<ip>/boot.efi


Edited by Biatu, 18 November 2022 - 05:56 PM.


#904 erwan.l

erwan.l

    Platinum Member

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

Posted 18 November 2022 - 05:55 PM

 

Config:

[dhcp]
root=RemoteInstall
filename=smsboot\x64\wdsmgfw.efi

Dir:

pxesrv\RemoteInstall
pxesrv\RemoteInstall\smsboot\x64
pxesrv\RemoteInstall\smsboot\x64\wdsmgfw.efi
pxesrv\RemoteInstall\smsboot\x64\bootmgfw.efi

Perfect.

 

I should have asked as well : post a log file when booting with this setup.

 

And i also assume you are using latest version.



#905 erwan.l

erwan.l

    Platinum Member

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

Posted 19 November 2022 - 12:03 PM

As of BINL\WDS, let me review that this week end.

 

Cheers,

Erwan

 

in config.ini :

opt252 to set the option 252.

proxybootfilename to set the proxy boot filename.

 

Aka the last 2 fields at the bottom of pxesrv window.



#906 erwan.l

erwan.l

    Platinum Member

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

Posted 19 November 2022 - 12:05 PM

Also, can you implement an option to proxy/forward tftp/BINL/WDS requests to another machine?

ie, when client requests tftp://<pxesrv>/boot.efi pxesrv requests tftp://<ip>/boot.efi

 

is not this what option 66 is supposed to do?



#907 Biatu

Biatu

    Member

  • Members
  • 76 posts
  •  
    United Kingdom

Posted 20 November 2022 - 01:05 AM

is not this what option 66 is supposed to do?

I think option 66 just tell client to connect directly to remote server. Im checking if pxesrv can act as a reverse proxy.


Edited by Biatu, 20 November 2022 - 01:12 AM.


#908 Biatu

Biatu

    Member

  • Members
  • 76 posts
  •  
    United Kingdom

Posted 20 November 2022 - 01:17 AM

To explain further:

192.168.1.10: WDS Server
192.168.1.2: Host running pxesrv /w proxydhcp

1. Client get dhcp response with option 66=192.168.1.2, bootfile=smsboot/x64/wdsmgfw.efi
2. Client requests tftp://192.168.1.2/smsboot/x64/wdsmgfw.efi
3. pxesrv requests tftp://192.168.1.10/smsboot/x64/wdsmgfw.efi
4. pxesrv relays bytes to client.

Edited by Biatu, 20 November 2022 - 01:19 AM.


#909 erwan.l

erwan.l

    Platinum Member

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

Posted 20 November 2022 - 02:25 PM

Can we have an option to not modify the root path to that of the bootfile?
ie, when I set the root path to "RemoteInstall" and set the bootfile to "smsboot\x64\wdsmgfw.efi" and ROOT gets modified "RemoteInstall\smsboot\x64\"

 

I believe I have identified the issue you are referring to.

15:21:19 ROOT=C:\Users\erwan\Documents\-= SOURCES =-\delphi\network\sniffer_w2k\pxesrv\RemoteInstall\smsboot\x64\
15:21:32 DHCPd:DISCOVER received, MAC:00-0C-29-63-45-97, XID:A8875A1C
15:21:32 DHCPd:OFFER sent, IP:0.0.0.0, XID:A8875A1C
15:21:35 DHCPd:REQUEST discarded - ProxyDHCP, MAC:00-0C-29-63-45-97, XID:A8875A1C
15:21:35 PDHCPd:REQUEST received, MAC:00-0C-29-63-45-97, IP:192.168.1.154, XID:E6A9843C
15:21:36 PDHCPd:DHCP_ACK sent, IP:192.168.1.154:4011, xid:E6A9843C
15:21:36 TFTPd:DoReadFile OpenError:smsboot\x64\wdsmgfw.efi Cannot open file "C:\Users\erwan\Documents\-= SOURCES =-\delphi\network\sniffer_w2k\pxesrv\RemoteInstall\smsboot\x64\smsboot\x64\wdsmgfw.efi". Le chemin d’accès spécifié est introuvable

Seems TPS does not like a path in the boot filename...

That bug occurs only when specifying the filename in config.ini.

If you select it from the GUI, bug does not occur : that is the workaround I can propose for now until I fix this issue.



#910 erwan.l

erwan.l

    Platinum Member

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

Posted 20 November 2022 - 02:35 PM

 

To explain further:

192.168.1.10: WDS Server
192.168.1.2: Host running pxesrv /w proxydhcp

1. Client get dhcp response with option 66=192.168.1.2, bootfile=smsboot/x64/wdsmgfw.efi
2. Client requests tftp://192.168.1.2/smsboot/x64/wdsmgfw.efi
3. pxesrv requests tftp://192.168.1.10/smsboot/x64/wdsmgfw.efi
4. pxesrv relays bytes to client.

Option 66 will tell your client to download the file from another host.

It will not tell your server to act a proxy.

 

If you really want to proxy (not sure why you would do that unless your client and tftp server sits on different networks), do not fill option 66 and use a proxy software.

I never tried this scenario but you can try with this piece of software (of mine) : here.

 


  • Biatu likes this

#911 netix

netix
  • Members
  • 0 posts
  •  
    Serbia

Posted 2 days ago

Hi,

I cant load any live linux *ubuntu,lubuntu,mint) from nfs.

I try with winnfs v2.0 and v2.4,

It load load vmlinuz and initrd.lz via http.

access nfs via winnfs

PORTMAP GETPORT 100003 2049
PORTMAP GETPORT 100005 1058
MOUNT MNT d:\pxeserv\files\iso\ubuntu\ from xx.xx.xx.xx

 

 

I get error "Unable find a live file system on the network"

#!ipxe
	
set boot-url http://${next-server}
initrd ${boot-url}/iso/ubuntu/casper/initrd.lz
kernel ${boot-url}/iso/ubuntu/casper/vmlinuz root=/dev/nfs  boot=casper netboot=nfs ro ip=dhcp noswap nolocales nomodeset noeject noprompt nosplash vga=788 nfsroot=xx.xx.xx.xx:/d/pxeserv/files/iso/ubuntu/
boot || goto failed
goto start

where I am wrong ?
 







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

2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users