There is a bug in gPXE though.
This works in 1.0.0: chain http://www.netboot.me/
17:17 < Docteh> chain http://192.168.0.10 vs chain
http://192.168.0.10/ aren't sending the same GET / request
0000 ? 00 0e 0c da 6d 61 08 00 27 5c 9b 8b 08 00 45 00 ?....ma..'\....E.
0010 ? 00 79 00 09 00 00 40 06 f8 b4 c0 a8 00 67 c0 a8 ?.y.... at ......g..
0020 ? 00 0a 04 00 00 50 09 1d 54 aa a3 f0 5a be 80 18 ?.....P..T...Z...
0030 ? 10 00 e0 9c 00 00 01 01 08 0a 00 11 41 68 10 b3 ?............Ah..
0040 ? af 88 47 45 54 20 af c9 04 20 48 54 54 50 2f 31 ?..GET ... HTTP/1
0050 ? 2e 30 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a 20 ?.0..User-Agent:
0060 ? 67 50 58 45 2f 31 2e 30 2e 30 2d 72 63 31 2b 0d ?gPXE/1.0.0-rc1+.
0070 ? 0a 48 6f 73 74 3a 20 31 39 32 2e 31 36 38 2e 30 ?.Host: 192.168.0
0080 ? 2e 31 30 0d 0a 0d 0a ? ? ? ? ? ? ? ? ? ? ? ? ? ? .10....
10584 1496.479725 192.168.0.103 192.168.0.10 HTTP GET \257\311\004 HTTP/1.0
On Tue, Jan 26, 2010 at 5:11 PM, Shao Miller
Post by Kyle KienapfelThe problem is probably all in the user agent that gets sent out.
gPXE/0.9.7+ (netboot.me/0.1.1)\r\nHost: www.netboot.me\r\n\r\n' | nc
www.netboot.me 80
vs just: User-Agent: gPXE/0.9.7+
Agreed.? It's quite possible that netboot.me is expecting a certain range of
possibilities and did not anticipate this gPXE user-agent.? For example, the
change from a zero and a nine to a one and a zero in 0.9.X versus 1.0.X...
We could ask Nick (I think it's Nick).
- Shao Miller