Displaying 3 results from an estimated 3 matches for "darkhttpd".
2013 Jul 05
3
[5.xx-6.01] broken PXE with HTTP
...ort=0 \
--dhcp-range=192.168.0.2,192.168.0.254,86400 \
--dhcp-boot=http://192.168.0.218/arch/boot/syslinux/lpxelinux.0 \
--dhcp-option-force=209,boot/syslinux/archiso.cfg \
--dhcp-option-force=210,http://192.168.0.218/arch/
(Same effects using pxelinux.0)
# darkhttpd /run/archiso/bootmnt
Only lpxelinux.0 files is retrived:
1372995737 192.168.0.90 "GET /arch/boot/syslinux/lpxelinux.0" 200 84517
"" "iPXE/1.0.0+ (09c5)"
Both server/cliente runing under qemu-1.5.1 on x86_64.
Packet capture is here:
https://dl.dropboxusercontent.com...
2013 Jul 05
0
[5.xx-6.01] broken PXE with HTTP
...8.0.2,192.168.0.254,86400 \
> --dhcp-boot=http://192.168.0.218/arch/boot/syslinux/lpxelinux.0 \
> --dhcp-option-force=209,boot/syslinux/archiso.cfg \
> --dhcp-option-force=210,http://192.168.0.218/arch/
>
> (Same effects using pxelinux.0)
>
> # darkhttpd /run/archiso/bootmnt
>
> Only lpxelinux.0 files is retrived:
>
> 1372995737 192.168.0.90 "GET /arch/boot/syslinux/lpxelinux.0" 200 84517
> "" "iPXE/1.0.0+ (09c5)"
>
> Both server/cliente runing under qemu-1.5.1 on x86_64.
>
> Packet captu...
2013 Jun 06
7
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
...syslinux/archiso_tail.cfg to 192.168.0.90
dnsmasq-tftp: sent /run/archiso/bootmnt/arch/boot/syslinux/splash.png to
192.168.0.90
------------------------------------------------------------------------
------------------------------------------------------------------------
This is when using http (darkhttpd) instead of tftp for retriving files
(syslinux-4.06). Note how each retrieved entry is "perfect", no double
//, no paths error, and things looks good.
dnsmasq --port=0 \
--dhcp-range=192.168.0.2,192.168.0.254,86400 \
--dhcp-boot=http://192.168.0.218/arch/boot/syslinu...