无忧启动论坛

 找回密码
 注册
搜索
【招募】优秀技术员,装机赚钱!最纯净的「微PE装机优盘」UEPON大师作品广告位出租 QQ:184822951
楼主: hhh333

[发布] Tiny PXE Server 可以用了

    [复制链接]
发表于 2015-3-16 10:29:49 | 显示全部楼层
经反复测试,传输效率不高呀,在一个机房全部通过PXE启动时,TFTPD32能正常传输完成,而这个软件导致大部分电脑不能正常获取引导文件(同时少开几台电脑还正常),用的最新.19的版本,仍然没有保存参数功能,希继续向开发者反馈提升。

点评

1、在窗口中点右键有保存参数的功能 2、多台机器启动能力的问题,你可以详细测试一下,如用没用到ProxyDhcp功能等,是用ipxe还是pxe功能等。我这里无条件测试。  详情 回复 发表于 2015-3-17 08:18
 楼主| 发表于 2015-3-17 08:18:15 | 显示全部楼层
xiaoy 发表于 2015-3-16 10:29
经反复测试,传输效率不高呀,在一个机房全部通过PXE启动时,TFTPD32能正常传输完成,而这个软件导致大部分 ...

1、在窗口中点右键有保存参数的功能
2、多台机器启动能力的问题,你可以详细测试一下,如用没用到ProxyDhcp功能等,是用ipxe还是pxe功能等。我这里无条件测试。

点评

今天针我对TinyPXEServer多台机器启动能力的问题做了个并不严谨的测试。 1. 以ThinkPad X201+Win10+TinyPXEServer作为启动服务器,两台兼容台式机作为客户机。 2. TinyPXEServer的设置: [attachimg]226208[/at  详情 回复 发表于 2015-8-28 17:31
发表于 2015-5-12 10:22:11 | 显示全部楼层
找了好久 感谢分享
发表于 2015-5-14 21:52:51 | 显示全部楼层
我去,这玩意怎么回事啊,在虚拟机里正常的,但是在实机上就不行啊,不断滚动连接的消息,但是就是不能启动,视乎根本就不能传送启动文件过去,我在机房试的,怎么更改配置都不行???什么歌意思啊!!一直用的HaneWin完全无问题!!!
发表于 2015-7-25 15:02:53 | 显示全部楼层
楼主 这个程序自带的DHCP 服务无法为多台联网的PE分配IP,我试过,只有一台联网的PE能得到IP,其他的都获取不到,请问有什么方法解决此问题?
发表于 2015-8-28 17:31:21 | 显示全部楼层
本帖最后由 notepad 于 2015-8-28 17:39 编辑
hhh333 发表于 2015-3-17 08:18
1、在窗口中点右键有保存参数的功能
2、多台机器启动能力的问题,你可以详细测试一下,如用没用到ProxyD ...


今天针我对TinyPXEServer多台机器启动能力的问题做了个并不严谨的测试。
这个测试的结论我分析不出来,只知道在最后阶段的PE文件传输时是可以多设备同时进行的。

1. 以ThinkPad X201+Win10+TinyPXEServer作为启动服务器,两台兼容台式机作为客户机。
2. TinyPXEServer的设置:
Config.ini
  1. [arch]
  2. 00006=efi\boot\iPXE32.efi
  3. 00007=efi\boot\iPXE64.efi

  4. [dhcp]
  5. root=
  6. altfilename=iPXE.menu
  7. start=1
  8. tftpd=1
  9. httpd=1
  10. bind=1
  11. binl=0
  12. dnsd=0
  13. proxydhcp=1
  14. smb=0
  15. verbose=1
  16. optextra=175.6.1.1.1.8.1.1
复制代码

2015-08-28_171109.jpg
3. 两台客户机都选择PXE启动:选定“Realtek PXE...”后同时回车。
接下来可以清楚地看到两台客户机同时加载同一个WIM文件,只是加载进度不同而已。
IMG_9057.JPG
4. 附上日志供大大们分析:
  1. 16:56:03 ROOT=F:\OS\iPXE\
  2. 16:56:03 DHCPd:67 started...
  3. 16:56:03 DHCPd:4011 started...
  4. 16:56:03 TFPTd started...
  5. 16:56:03 HTTPd started...
  6. 16:56:34 DHCPd:DISCOVER received, MAC:D0-50-99-17-28-F9, XID:9A1728F9
  7. 16:56:35 DHCPd:OFFER sent, IP:0.0.0.0, XID:9A1728F9
  8. 16:56:38 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:9A1728F9
  9. 16:56:38 PDHCPd:REQUEST received, MAC:D0-50-99-17-28-F9, IP:192.168.16.180, XID:9A1728F9
  10. 16:56:39 DHCPd:Arch=00000
  11. 16:56:39 Proxy boot filename empty?
  12. 16:56:39 PDHCPd:DHCP_ACK sent, IP:192.168.16.180:68, xid:9A1728F9
  13. 16:56:39 TFTPd:DoReadFile:Undionly.kpxe B:1456 T:0
  14. 16:56:39 TFTPd:TransferComplete=True (192.168.16.180:2070)
  15. 16:56:44 DHCPd:DISCOVER received, MAC:D0-50-99-17-28-F9, XID:92939215
  16. 16:56:44 DHCPd:iPXE user-class detected
  17. 16:56:44 DHCPd:OFFER sent, IP:0.0.0.0, XID:92939215
  18. 16:56:44 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:92939215
  19. 16:56:44 TFTPd:DoReadFile:iPXE.menu B:1432 T:9304
  20. 16:56:44 TFTPd:TransferComplete=True (192.168.16.181:44383)
  21. 16:56:48 HTTPd:Connect: 192.168.16.181, TID=10992
  22. 16:56:48 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/wimboot
  23. 16:56:48 HTTPd:Server : Returning /EFI/Boot/wimboot
  24. 16:56:48 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/bootmgr
  25. 16:56:48 HTTPd:Server : Returning /EFI/Boot/bootmgr
  26. 16:56:48 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/bcd
  27. 16:56:48 HTTPd:Server : Returning /EFI/Boot/bcd
  28. 16:56:48 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/boot.sdi
  29. 16:56:48 HTTPd:Server : Returning /EFI/Boot/boot.sdi
  30. 16:56:48 HTTPd:Client: 192.168.16.181 [GET] /Boot/WinPE2008X86.wim
  31. 16:56:48 HTTPd:Server : Returning /Boot/WinPE2008X86.wim
  32. 16:57:03 HTTPd:Exception: , Connection Closed Gracefully.
  33. 16:57:03 HTTPd:DisConnect: TID=10992
  34. 16:57:21 DHCPd:DISCOVER received, MAC:D0-50-99-17-28-F9, XID:9A1728F9
  35. 16:57:22 DHCPd:OFFER sent, IP:0.0.0.0, XID:9A1728F9
  36. 16:57:26 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:9A1728F9
  37. 16:57:26 PDHCPd:REQUEST received, MAC:D0-50-99-17-28-F9, IP:192.168.16.180, XID:9A1728F9
  38. 16:57:26 DHCPd:Arch=00000
  39. 16:57:26 Proxy boot filename empty?
  40. 16:57:26 PDHCPd:DHCP_ACK sent, IP:192.168.16.180:68, xid:9A1728F9
  41. 16:57:26 TFTPd:DoReadFile:Undionly.kpxe B:1456 T:0
  42. 16:57:26 TFTPd:TransferComplete=True (192.168.16.180:2070)
  43. 16:57:31 DHCPd:DISCOVER received, MAC:D0-50-99-17-28-F9, XID:2A651466
  44. 16:57:31 DHCPd:iPXE user-class detected
  45. 16:57:31 DHCPd:OFFER sent, IP:0.0.0.0, XID:2A651466
  46. 16:57:31 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:2A651466
  47. 16:57:31 TFTPd:DoReadFile:iPXE.menu B:1432 T:9304
  48. 16:57:31 TFTPd:TransferComplete=True (192.168.16.181:52799)
  49. 16:57:38 HTTPd:Connect: 192.168.16.181, TID=4704
  50. 16:57:38 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/wimboot
  51. 16:57:38 HTTPd:Server : Returning /EFI/Boot/wimboot
  52. 16:57:38 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/bootmgr
  53. 16:57:38 HTTPd:Server : Returning /EFI/Boot/bootmgr
  54. 16:57:38 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/bcd
  55. 16:57:38 HTTPd:Server : Returning /EFI/Boot/bcd
  56. 16:57:38 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/boot.sdi
  57. 16:57:38 HTTPd:Server : Returning /EFI/Boot/boot.sdi
  58. 16:57:38 HTTPd:Client: 192.168.16.181 [GET] /Boot/Win8PEX64.wim
  59. 16:57:38 HTTPd:Server : Returning /Boot/Win8PEX64.wim
  60. 16:58:13 HTTPd:Exception: , Connection Closed Gracefully.
  61. 16:58:13 HTTPd:DisConnect: TID=4704
  62. 16:58:35 DHCPd:DISCOVER discarded, MAC:D0-50-99-17-28-F9, XID:2B9B5F61
  63. 16:58:35 DHCPd:DISCOVER discarded, MAC:D0-50-99-17-28-F9, XID:4B0552CA
  64. 16:58:35 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:4B0552CA
  65. 17:01:03 WorkingSetSize=12672 KB
  66. 17:01:03 PagedPool=211KB
  67. 17:01:03 Pagefile=211KB
  68. 17:04:45 DHCPd:DISCOVER received, MAC:D0-50-99-17-28-F9, XID:9A1728F9
  69. 17:04:46 DHCPd:OFFER sent, IP:0.0.0.0, XID:9A1728F9
  70. 17:04:49 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:9A1728F9
  71. 17:04:49 PDHCPd:REQUEST received, MAC:D0-50-99-17-28-F9, IP:192.168.16.180, XID:9A1728F9
  72. 17:04:50 DHCPd:Arch=00000
  73. 17:04:50 Proxy boot filename empty?
  74. 17:04:50 PDHCPd:DHCP_ACK sent, IP:192.168.16.180:68, xid:9A1728F9
  75. 17:04:50 TFTPd:DoReadFile:Undionly.kpxe B:1456 T:0
  76. 17:04:50 TFTPd:TransferComplete=True (192.168.16.180:2070)
  77. 17:04:55 DHCPd:DISCOVER received, MAC:D0-50-99-17-28-F9, XID:36DECD75
  78. 17:04:55 DHCPd:iPXE user-class detected
  79. 17:04:55 DHCPd:OFFER sent, IP:0.0.0.0, XID:36DECD75
  80. 17:04:55 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:36DECD75
  81. 17:04:55 TFTPd:DoReadFile:iPXE.menu B:1432 T:9304
  82. 17:04:55 TFTPd:TransferComplete=True (192.168.16.181:24534)
  83. 17:04:57 HTTPd:Connect: 192.168.16.181, TID=11160
  84. 17:04:57 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/wimboot
  85. 17:04:57 HTTPd:Server : Returning /EFI/Boot/wimboot
  86. 17:04:57 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/bootmgr
  87. 17:04:57 HTTPd:Server : Returning /EFI/Boot/bootmgr
  88. 17:04:57 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/bcd
  89. 17:04:57 HTTPd:Server : Returning /EFI/Boot/bcd
  90. 17:04:57 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/boot.sdi
  91. 17:04:57 HTTPd:Server : Returning /EFI/Boot/boot.sdi
  92. 17:04:57 HTTPd:Client: 192.168.16.181 [GET] /Boot/Win8PEX64.wim
  93. 17:04:57 HTTPd:Server : Returning /Boot/Win8PEX64.wim
  94. 17:05:03 DHCPd:DISCOVER received, MAC:00-E0-66-4B-37-F1, XID:674B37F1
  95. 17:05:03 DHCPd:OFFER sent, IP:0.0.0.0, XID:674B37F1
  96. 17:05:07 DHCPd:REQUEST discarded, MAC:00-E0-66-4B-37-F1, XID:674B37F1
  97. 17:05:07 PDHCPd:REQUEST received, MAC:00-E0-66-4B-37-F1, IP:192.168.16.132, XID:674B37F1
  98. 17:05:07 DHCPd:Arch=00000
  99. 17:05:07 Proxy boot filename empty?
  100. 17:05:07 PDHCPd:DHCP_ACK sent, IP:192.168.16.132:68, xid:674B37F1
  101. 17:05:07 TFTPd:DoReadFile:Undionly.kpxe B:1456 T:0
  102. 17:05:07 TFTPd:TransferComplete=True (192.168.16.132:2070)
  103. 17:05:11 DHCPd:DISCOVER received, MAC:00-E0-66-4B-37-F1, XID:FEC95624
  104. 17:05:12 DHCPd:iPXE user-class detected
  105. 17:05:12 DHCPd:OFFER sent, IP:0.0.0.0, XID:FEC95624
  106. 17:05:12 DHCPd:REQUEST discarded, MAC:00-E0-66-4B-37-F1, XID:FEC95624
  107. 17:05:12 TFTPd:DoReadFile:iPXE.menu B:1432 T:9304
  108. 17:05:12 TFTPd:TransferComplete=True (192.168.16.132:3823)
  109. 17:05:12 HTTPd:Connect: 192.168.16.132, TID=10044
  110. 17:05:12 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/wimboot
  111. 17:05:12 HTTPd:Server : Returning /EFI/Boot/wimboot
  112. 17:05:12 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/bootmgr
  113. 17:05:12 HTTPd:Server : Returning /EFI/Boot/bootmgr
  114. 17:05:13 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/bcd
  115. 17:05:13 HTTPd:Server : Returning /EFI/Boot/bcd
  116. 17:05:13 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/boot.sdi
  117. 17:05:13 HTTPd:Server : Returning /EFI/Boot/boot.sdi
  118. 17:05:13 HTTPd:Client: 192.168.16.132 [GET] /Boot/WePEX64.wim
  119. 17:05:13 HTTPd:Server : Returning /Boot/WePEX64.wim
  120. 17:05:52 HTTPd:Exception: , Connection Closed Gracefully.
  121. 17:05:52 HTTPd:DisConnect: TID=11160
  122. 17:05:53 HTTPd:Exception: , Connection Closed Gracefully.
  123. 17:05:53 HTTPd:DisConnect: TID=10044
  124. 17:06:03 WorkingSetSize=12760 KB
  125. 17:06:03 PagedPool=211KB
  126. 17:06:03 Pagefile=211KB
  127. 17:06:13 DHCPd:DISCOVER discarded, MAC:D0-50-99-17-28-F9, XID:8DC4A784
  128. 17:06:13 DHCPd:DISCOVER discarded, MAC:D0-50-99-17-28-F9, XID:F13B9A21
  129. 17:06:14 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:F13B9A21
  130. 17:07:04 DHCPd:DISCOVER received, MAC:D0-50-99-17-28-F9, XID:9A1728F9
  131. 17:07:04 DHCPd:OFFER sent, IP:0.0.0.0, XID:9A1728F9
  132. 17:07:06 DHCPd:DISCOVER received, MAC:00-E0-66-4B-37-F1, XID:674B37F1
  133. 17:07:07 DHCPd:OFFER sent, IP:0.0.0.0, XID:674B37F1
  134. 17:07:08 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:9A1728F9
  135. 17:07:08 PDHCPd:REQUEST received, MAC:D0-50-99-17-28-F9, IP:192.168.16.180, XID:9A1728F9
  136. 17:07:08 DHCPd:Arch=00000
  137. 17:07:08 Proxy boot filename empty?
  138. 17:07:08 TFTPd:DoReadFile:Undionly.kpxe B:1456 T:0
  139. 17:07:08 PDHCPd:DHCP_ACK sent, IP:192.168.16.180:68, xid:9A1728F9
  140. 17:07:08 TFTPd:TransferComplete=True (192.168.16.180:2070)
  141. 17:07:10 DHCPd:REQUEST discarded, MAC:00-E0-66-4B-37-F1, XID:674B37F1
  142. 17:07:10 PDHCPd:REQUEST received, MAC:00-E0-66-4B-37-F1, IP:192.168.16.132, XID:674B37F1
  143. 17:07:10 DHCPd:Arch=00000
  144. 17:07:10 Proxy boot filename empty?
  145. 17:07:10 PDHCPd:DHCP_ACK sent, IP:192.168.16.132:68, xid:674B37F1
  146. 17:07:10 TFTPd:DoReadFile:Undionly.kpxe B:1456 T:0
  147. 17:07:10 TFTPd:TransferComplete=True (192.168.16.132:2070)
  148. 17:07:13 DHCPd:DISCOVER received, MAC:D0-50-99-17-28-F9, XID:AA93D332
  149. 17:07:14 DHCPd:iPXE user-class detected
  150. 17:07:14 DHCPd:OFFER sent, IP:0.0.0.0, XID:AA93D332
  151. 17:07:14 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:AA93D332
  152. 17:07:14 TFTPd:DoReadFile:iPXE.menu B:1432 T:9304
  153. 17:07:14 TFTPd:TransferComplete=True (192.168.16.181:12572)
  154. 17:07:15 DHCPd:DISCOVER received, MAC:00-E0-66-4B-37-F1, XID:29E19535
  155. 17:07:16 DHCPd:iPXE user-class detected
  156. 17:07:16 DHCPd:OFFER sent, IP:0.0.0.0, XID:29E19535
  157. 17:07:16 DHCPd:REQUEST discarded, MAC:00-E0-66-4B-37-F1, XID:29E19535
  158. 17:07:16 TFTPd:DoReadFile:iPXE.menu B:1432 T:9304
  159. 17:07:16 TFTPd:TransferComplete=True (192.168.16.132:20569)
  160. 17:07:20 HTTPd:Connect: 192.168.16.181, TID=7632
  161. 17:07:20 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/wimboot
  162. 17:07:20 HTTPd:Server : Returning /EFI/Boot/wimboot
  163. 17:07:20 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/bootmgr
  164. 17:07:20 HTTPd:Server : Returning /EFI/Boot/bootmgr
  165. 17:07:20 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/bcd
  166. 17:07:20 HTTPd:Server : Returning /EFI/Boot/bcd
  167. 17:07:20 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/boot.sdi
  168. 17:07:20 HTTPd:Server : Returning /EFI/Boot/boot.sdi
  169. 17:07:20 HTTPd:Client: 192.168.16.181 [GET] /Boot/WePEX64.wim
  170. 17:07:20 HTTPd:Server : Returning /Boot/WePEX64.wim
  171. 17:07:22 HTTPd:Connect: 192.168.16.132, TID=9680
  172. 17:07:22 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/wimboot
  173. 17:07:22 HTTPd:Server : Returning /EFI/Boot/wimboot
  174. 17:07:22 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/bootmgr
  175. 17:07:22 HTTPd:Server : Returning /EFI/Boot/bootmgr
  176. 17:07:22 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/bcd
  177. 17:07:22 HTTPd:Server : Returning /EFI/Boot/bcd
  178. 17:07:22 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/boot.sdi
  179. 17:07:22 HTTPd:Server : Returning /EFI/Boot/boot.sdi
  180. 17:07:22 HTTPd:Client: 192.168.16.132 [GET] /Boot/WePEX64.wim
  181. 17:07:22 HTTPd:Server : Returning /Boot/WePEX64.wim
  182. 17:07:59 HTTPd:Exception: , Connection Closed Gracefully.
  183. 17:07:59 HTTPd:DisConnect: TID=7632
  184. 17:08:02 HTTPd:Exception: , Connection Closed Gracefully.
  185. 17:08:02 HTTPd:DisConnect: TID=9680
  186. 17:11:04 WorkingSetSize=12824 KB
  187. 17:11:04 PagedPool=211KB
  188. 17:11:04 Pagefile=211KB
  189. 17:14:18 DHCPd:DISCOVER received, MAC:00-E0-66-4B-37-F1, XID:674B37F1
  190. 17:14:19 DHCPd:OFFER sent, IP:0.0.0.0, XID:674B37F1
  191. 17:14:22 DHCPd:REQUEST discarded, MAC:00-E0-66-4B-37-F1, XID:674B37F1
  192. 17:14:22 PDHCPd:REQUEST received, MAC:00-E0-66-4B-37-F1, IP:192.168.16.132, XID:674B37F1
  193. 17:14:22 DHCPd:Arch=00000
  194. 17:14:22 Proxy boot filename empty?
  195. 17:14:22 PDHCPd:DHCP_ACK sent, IP:192.168.16.132:68, xid:674B37F1
  196. 17:14:22 TFTPd:DoReadFile:Undionly.kpxe B:1456 T:0
  197. 17:14:22 TFTPd:TransferComplete=True (192.168.16.132:2070)
  198. 17:14:25 DHCPd:DISCOVER received, MAC:00-E0-66-4B-37-F1, XID:65788C73
  199. 17:14:26 DHCPd:iPXE user-class detected
  200. 17:14:26 DHCPd:OFFER sent, IP:0.0.0.0, XID:65788C73
  201. 17:14:26 DHCPd:REQUEST discarded, MAC:00-E0-66-4B-37-F1, XID:65788C73
  202. 17:14:26 TFTPd:DoReadFile:iPXE.menu B:1432 T:9304
  203. 17:14:26 TFTPd:TransferComplete=True (192.168.16.132:5139)
  204. 17:14:26 HTTPd:Connect: 192.168.16.132, TID=12948
  205. 17:14:26 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/wimboot
  206. 17:14:26 HTTPd:Server : Returning /EFI/Boot/wimboot
  207. 17:14:26 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/bootmgr
  208. 17:14:26 HTTPd:Server : Returning /EFI/Boot/bootmgr
  209. 17:14:26 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/bcd
  210. 17:14:26 HTTPd:Server : Returning /EFI/Boot/bcd
  211. 17:14:26 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/boot.sdi
  212. 17:14:26 HTTPd:Server : Returning /EFI/Boot/boot.sdi
  213. 17:14:26 HTTPd:Client: 192.168.16.132 [GET] /Boot/WinPE2008X86.wim
  214. 17:14:26 HTTPd:Server : Returning /Boot/WinPE2008X86.wim
  215. 17:14:46 HTTPd:Exception: , Connection Closed Gracefully.
  216. 17:14:46 HTTPd:DisConnect: TID=12948
  217. 17:16:04 WorkingSetSize=12816 KB
  218. 17:16:04 PagedPool=211KB
  219. 17:16:04 Pagefile=211KB
  220. 17:17:20 DHCPd:DISCOVER received, MAC:D0-50-99-17-28-F9, XID:9A1728F9
  221. 17:17:20 DHCPd:OFFER sent, IP:0.0.0.0, XID:9A1728F9
  222. 17:17:20 DHCPd:DISCOVER received, MAC:00-E0-66-4B-37-F1, XID:674B37F1
  223. 17:17:20 DHCPd:OFFER sent, IP:0.0.0.0, XID:674B37F1
  224. 17:17:24 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:9A1728F9
  225. 17:17:24 PDHCPd:REQUEST received, MAC:D0-50-99-17-28-F9, IP:192.168.16.180, XID:9A1728F9
  226. 17:17:24 DHCPd:REQUEST discarded, MAC:00-E0-66-4B-37-F1, XID:674B37F1
  227. 17:17:24 DHCPd:Arch=00000
  228. 17:17:24 Proxy boot filename empty?
  229. 17:17:24 PDHCPd:DHCP_ACK sent, IP:192.168.16.180:68, xid:9A1728F9
  230. 17:17:24 TFTPd:DoReadFile:Undionly.kpxe B:1456 T:0
  231. 17:17:24 PDHCPd:REQUEST received, MAC:00-E0-66-4B-37-F1, IP:192.168.16.132, XID:674B37F1
  232. 17:17:24 TFTPd:TransferComplete=True (192.168.16.180:2070)
  233. 17:17:25 DHCPd:Arch=00000
  234. 17:17:25 Proxy boot filename empty?
  235. 17:17:25 PDHCPd:DHCP_ACK sent, IP:192.168.16.132:68, xid:674B37F1
  236. 17:17:25 TFTPd:DoReadFile:Undionly.kpxe B:1456 T:0
  237. 17:17:25 TFTPd:TransferComplete=True (192.168.16.132:2070)
  238. 17:17:29 DHCPd:DISCOVER received, MAC:00-E0-66-4B-37-F1, XID:DF5C6A0E
  239. 17:17:30 DHCPd:iPXE user-class detected
  240. 17:17:30 DHCPd:OFFER sent, IP:0.0.0.0, XID:DF5C6A0E
  241. 17:17:30 DHCPd:DISCOVER received, MAC:D0-50-99-17-28-F9, XID:A28B9F2C
  242. 17:17:30 TFTPd:DoReadFile:iPXE.menu B:1432 T:9304
  243. 17:17:30 TFTPd:TransferComplete=True (192.168.16.132:2068)
  244. 17:17:30 DHCPd:iPXE user-class detected
  245. 17:17:30 DHCPd:OFFER sent, IP:0.0.0.0, XID:A28B9F2C
  246. 17:17:30 DHCPd:REQUEST discarded, MAC:00-E0-66-4B-37-F1, XID:DF5C6A0E
  247. 17:17:30 TFTPd:DoReadFile:iPXE.menu B:1432 T:9304
  248. 17:17:30 DHCPd:REQUEST discarded, MAC:D0-50-99-17-28-F9, XID:A28B9F2C
  249. 17:17:30 TFTPd:TransferComplete=True (192.168.16.181:23261)
  250. 17:17:36 HTTPd:Connect: 192.168.16.132, TID=7588
  251. 17:17:36 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/wimboot
  252. 17:17:36 HTTPd:Server : Returning /EFI/Boot/wimboot
  253. 17:17:36 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/bootmgr
  254. 17:17:36 HTTPd:Server : Returning /EFI/Boot/bootmgr
  255. 17:17:36 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/bcd
  256. 17:17:36 HTTPd:Server : Returning /EFI/Boot/bcd
  257. 17:17:36 HTTPd:Client: 192.168.16.132 [GET] /EFI/Boot/boot.sdi
  258. 17:17:36 HTTPd:Server : Returning /EFI/Boot/boot.sdi
  259. 17:17:36 HTTPd:Client: 192.168.16.132 [GET] /Boot/WePEX64.wim
  260. 17:17:36 HTTPd:Server : Returning /Boot/WePEX64.wim
  261. 17:17:36 HTTPd:Connect: 192.168.16.181, TID=9552
  262. 17:17:36 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/wimboot
  263. 17:17:36 HTTPd:Server : Returning /EFI/Boot/wimboot
  264. 17:17:36 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/bootmgr
  265. 17:17:36 HTTPd:Server : Returning /EFI/Boot/bootmgr
  266. 17:17:36 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/bcd
  267. 17:17:36 HTTPd:Server : Returning /EFI/Boot/bcd
  268. 17:17:36 HTTPd:Client: 192.168.16.181 [GET] /EFI/Boot/boot.sdi
  269. 17:17:36 HTTPd:Server : Returning /EFI/Boot/boot.sdi
  270. 17:17:37 HTTPd:Client: 192.168.16.181 [GET] /Boot/WePEX64.wim
  271. 17:17:37 HTTPd:Server : Returning /Boot/WePEX64.wim
  272. 17:18:17 HTTPd:Exception: , Connection Closed Gracefully.
  273. 17:18:17 HTTPd:DisConnect: TID=7588
  274. 17:18:18 HTTPd:Exception: , Connection Closed Gracefully.
  275. 17:18:18 HTTPd:DisConnect: TID=9552
  276. 17:21:04 WorkingSetSize=12776 KB
  277. 17:21:04 PagedPool=211KB
  278. 17:21:04 Pagefile=211KB
  279. 17:26:05 WorkingSetSize=12808 KB
  280. 17:26:05 PagedPool=211KB
  281. 17:26:05 Pagefile=211KB
复制代码

发表于 2015-9-1 01:14:45 | 显示全部楼层
我要下载下来试试看
发表于 2015-11-20 10:10:21 | 显示全部楼层
问:原有ms-dhcp,跨网段vlan,按照上面说明只要勾选“proxydhcp”就会让ms-dhcp分配IP,也就是说Tiny PXE Server自带的DHCP不会分配IP了,这个是重要的,对吗?
Tiny PXE Server支持vlan吗?

点评

https://en.wikipedia.org/wiki/Preboot_Execution_Environment#Integration The idea behind a proxyDHCP is to split the PXE DHCP requirements in two independently run and administered server units:  详情 回复 发表于 2015-11-30 09:53
也就是说Tiny PXE Server自带的DHCP不会分配IP了,这个是重要的,对吗? -------------- 大概是这个意思! Tiny PXE Server 以接力(代理)的方式参与的。 自己不从自己的IP池取一个IP,而是代表客户机,从上级  详情 回复 发表于 2015-11-29 18:47
发表于 2015-11-29 18:47:58 | 显示全部楼层
本帖最后由 mdyblog 于 2015-11-30 10:26 编辑
zhaohj 发表于 2015-11-20 10:10
问:原有ms-dhcp,跨网段vlan,按照上面说明只要勾选“proxydhcp”就会让ms-dhcp分配IP,也就是说Tiny PXE  ...


也就是说Tiny PXE Server自带的DHCP不会分配IP了,这个是重要的,对吗?
--------------
大概是这个意思!

Tiny PXE Server 以接力(代理)的方式参与的。 自己不从自己的IP池取一个IP,发给客户机。
这样就不会冲突了。

点评

这个理解有些乱  发表于 2015-11-30 09:53
发表于 2015-11-30 09:53:18 | 显示全部楼层
zhaohj 发表于 2015-11-20 10:10
问:原有ms-dhcp,跨网段vlan,按照上面说明只要勾选“proxydhcp”就会让ms-dhcp分配IP,也就是说Tiny PXE  ...

https://en.wikipedia.org/wiki/Preboot_Execution_Environment#Integration

The idea behind a proxyDHCP is to split the PXE DHCP requirements in two independently run and administered server units:

    The classic DHCP server providing IP address, IP mask, etc. to all booting DHCP clients.
    The proxyDHCP server providing TFTP server IP address and name of the NBP only to PXE identified booting clients.


Integration


DHCP vs proxyDHCP Server


The PXE Client/Server environment was designed so it can be seamlessly integrated with an already in place DHCP and TFTP server infrastructure. This design goal presented a challenge when dealing with the classic DHCP protocol. Corporate DHCP servers are usually subject to strict policies that conspire against easily adding the additional parameters and rules required to support a PXE environment. For this reason the PXE standard developed the concept of DHCP redirection or "proxyDHCP". The idea behind a proxyDHCP is to split the PXE DHCP requirements in two independently run and administered server units:
  • The classic DHCP server providing IP address, IP mask, etc. to all booting DHCP clients.
  • The proxyDHCP server providing TFTP server IP address and name of the NBP only to PXE identified booting clients.
In a DHCP plus proxyDHCP server environment [4]:18 the PXE client initially broadcasts a single PXE DHCPDISCOVER packet and receives two complementary DHCPOFFERs; one from the regular non PXE enabled DHCP server and a second one from the proxyDHCP server. Both answers together provide the required information to allow the PXE client to continue with its booting process. This non-intrusive approach allows setting a PXE environment without touching the configuration of an already working DHCP server. The proxyDHCP service may also run on the same host as the standard DHCP service but even in this case they are both two independently run and administered applications. Since two services cannot use the same port 67/UDP on the same host, the proxyDHCP runs on port 4011/UDP. The proxyDHCP approach has proved to be extremely useful in a wide range of PXE scenarios going from corporate to home environments.


proxcy dhcp的概念好些不清楚。其实就是为了和现有的DHCP环境无缝集成。
现存的DHCPserver的配置不做任何修改。
同一网络环境中,同时存在一个已有的DHCP Server,和 新加的一台 Proxy DHCP Server。
普通的DHCP Client依然只从原有的DHCP Server获取IP。
而带PXE能力的PXE Client网络启动时,在从原有的DHCP Server获取IP后, 会继续从网络上的另一个Proxy DHCP Server上获取一个TFTP server的地址和一个启动文件名,用于启动。



或者看一下这个文件  ftp://download.intel.com/design/ ... wnloads/pxespec.pdf
就会对整个PXE的启动过程了解得非常清楚了。

如果能用TCP抓包工具抓包分析一下就会更清楚了,每个数据包都可以看得非常清楚


点评

谢谢! 这个讲的很清楚。  详情 回复 发表于 2015-11-30 10:25
您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|小黑屋|手机版|Archiver|无忧启动 ( 闽ICP备05002490号-1 )无忧启动官方群

GMT+8, 2017-3-26 03:42

Powered by Discuz! X3.3

© 2001-2017 Comsenz Inc.

快速回复 返回顶部 返回列表