服务器 Gind.cn
  1. 服务器 Gind.cn
  3. 客户端没有从某个DHCP服务器获取地址
Intereting Posts
Windows 10，微软VLC图像下载 – 任何方式使用下载pipe理器？ 2个子网上的VTP域 将NSlogging传输到新服务器 PHPfile upload失败的大文件 Windows服务器备份MMC崩溃 允许非root用户访问/根文件夹 Mysql InnoDB优化 如何在Windows 7上创build没有configuration文件的用户 弹性负载均衡器和SSL终止 如何制作使用TLS的自签名SSL证书？ 如何更改站点间拓扑生成器 如果我在ProLiant DL320 G5服务器上重新启用板载RAID，会丢失当前的磁盘内容吗？ 替代Ganglia接口？ linux内核configuration来过滤基于接口的组播stream量 初级和高级系统pipe理员多less钱？

客户端没有从某个DHCP服务器获取地址

我正在研究一些embedded式设备，它们应该通过以太网连接到一个大型networking（数百个设备），并且应该使用DHCP协议进行configuration。 我所经历的显然是设备在一些networking中获得地址，而在其他networking中却没有。 我只用一台客户机，一台交换机和一台DHCP服务器（Ubuntu Linux）build立了一个testingnetworking。 地址被正确分配，DHCP服务器日志显示DORA序列。

我尝试将同一个客户端连接到一个带有DHCP服务器的普通家庭路由器（这是我的家庭路由器，所以它应该正常工作），IP地址不是由客户端获取的。 这是设备的序列转储： 

No. Time Source Destination Protocol Length Info 86 26.515684000 :: ff02::16 ICMPv6 90 Multicast Listener Report Message v2 Frame 86: 90 bytes on wire (720 bits), 90 bytes captured (720 bits) on interface 0 Ethernet II, Src: DavicomS_91:de:41 (00:60:6e:91:de:41), Dst: IPv6mcast_00:00:00:16 (33:33:00:00:00:16) Internet Protocol Version 6, Src: :: (::), Dst: ff02::16 (ff02::16) Internet Control Message Protocol v6 No. Time Source Destination Protocol Length Info 87 26.515688000 :: ff02::1:ff91:de41 ICMPv6 78 Neighbor Solicitation for fe80::260:6eff:fe91:de41 Frame 87: 78 bytes on wire (624 bits), 78 bytes captured (624 bits) on interface 0 Ethernet II, Src: DavicomS_91:de:41 (00:60:6e:91:de:41), Dst: IPv6mcast_ff:91:de:41 (33:33:ff:91:de:41) Internet Protocol Version 6, Src: :: (::), Dst: ff02::1:ff91:de41 (ff02::1:ff91:de41) Internet Control Message Protocol v6 No. Time Source Destination Protocol Length Info 88 26.596056000 0.0.0.0 255.255.255.255 DHCP 371 DHCP Discover - Transaction ID 0xb444e919 Frame 88: 371 bytes on wire (2968 bits), 371 bytes captured (2968 bits) on interface 0 Ethernet II, Src: DavicomS_91:de:41 (00:60:6e:91:de:41), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol Message type: Boot Request (1) Hardware type: Ethernet Hardware address length: 6 Hops: 0 Transaction ID: 0xb444e919 Seconds elapsed: 0 Bootp flags: 0x0000 (Unicast) Client IP address: 0.0.0.0 (0.0.0.0) Your (client) IP address: 0.0.0.0 (0.0.0.0) Next server IP address: 0.0.0.0 (0.0.0.0) Relay agent IP address: 0.0.0.0 (0.0.0.0) Client MAC address: DavicomS_91:de:41 (00:60:6e:91:de:41) Client hardware address padding: 00000000000000000000 Server host name not given Boot file name not given Magic cookie: DHCP Option: (53) DHCP Message Type Option: (57) Maximum DHCP Message Size Option: (60) Vendor class identifier Option: (12) Host Name Option: (55) Parameter Request List Option: (255) End No. Time Source Destination Protocol Length Info 94 27.515730000 fe80::260:6eff:fe91:de41 ff02::2 ICMPv6 70 Router Solicitation from 00:60:6e:91:de:41 Frame 94: 70 bytes on wire (560 bits), 70 bytes captured (560 bits) on interface 0 Ethernet II, Src: DavicomS_91:de:41 (00:60:6e:91:de:41), Dst: IPv6mcast_00:00:00:02 (33:33:00:00:00:02) Internet Protocol Version 6, Src: fe80::260:6eff:fe91:de41 (fe80::260:6eff:fe91:de41), Dst: ff02::2 (ff02::2) Internet Control Message Protocol v6 No. Time Source Destination Protocol Length Info 119 30.427837000 0.0.0.0 255.255.255.255 DHCP 371 DHCP Discover - Transaction ID 0xb444e919 Frame 119: 371 bytes on wire (2968 bits), 371 bytes captured (2968 bits) on interface 0 Ethernet II, Src: DavicomS_91:de:41 (00:60:6e:91:de:41), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol Message type: Boot Request (1) Hardware type: Ethernet Hardware address length: 6 Hops: 0 Transaction ID: 0xb444e919 Seconds elapsed: 4 Bootp flags: 0x0000 (Unicast) Client IP address: 0.0.0.0 (0.0.0.0) Your (client) IP address: 0.0.0.0 (0.0.0.0) Next server IP address: 0.0.0.0 (0.0.0.0) Relay agent IP address: 0.0.0.0 (0.0.0.0) Client MAC address: DavicomS_91:de:41 (00:60:6e:91:de:41) Client hardware address padding: 00000000000000000000 Server host name not given Boot file name not given Magic cookie: DHCP Option: (53) DHCP Message Type Option: (57) Maximum DHCP Message Size Option: (60) Vendor class identifier Option: (12) Host Name Option: (55) Parameter Request List Option: (255) End No. Time Source Destination Protocol Length Info 122 30.985580000 fe80::260:6eff:fe91:de41 ff02::16 ICMPv6 90 Multicast Listener Report Message v2 Frame 122: 90 bytes on wire (720 bits), 90 bytes captured (720 bits) on interface 0 Ethernet II, Src: DavicomS_91:de:41 (00:60:6e:91:de:41), Dst: IPv6mcast_00:00:00:16 (33:33:00:00:00:16) Internet Protocol Version 6, Src: fe80::260:6eff:fe91:de41 (fe80::260:6eff:fe91:de41), Dst: ff02::16 (ff02::16) Internet Control Message Protocol v6 No. Time Source Destination Protocol Length Info 127 31.525478000 fe80::260:6eff:fe91:de41 ff02::2 ICMPv6 70 Router Solicitation from 00:60:6e:91:de:41 Frame 127: 70 bytes on wire (560 bits), 70 bytes captured (560 bits) on interface 0 Ethernet II, Src: DavicomS_91:de:41 (00:60:6e:91:de:41), Dst: IPv6mcast_00:00:00:02 (33:33:00:00:00:02) Internet Protocol Version 6, Src: fe80::260:6eff:fe91:de41 (fe80::260:6eff:fe91:de41), Dst: ff02::2 (ff02::2) Internet Control Message Protocol v6 No. Time Source Destination Protocol Length Info 138 35.535297000 fe80::260:6eff:fe91:de41 ff02::2 ICMPv6 70 Router Solicitation from 00:60:6e:91:de:41 Frame 138: 70 bytes on wire (560 bits), 70 bytes captured (560 bits) on interface 0 Ethernet II, Src: DavicomS_91:de:41 (00:60:6e:91:de:41), Dst: IPv6mcast_00:00:00:02 (33:33:00:00:00:02) Internet Protocol Version 6, Src: fe80::260:6eff:fe91:de41 (fe80::260:6eff:fe91:de41), Dst: ff02::2 (ff02::2) Internet Control Message Protocol v6 No. Time Source Destination Protocol Length Info 142 39.405342000 0.0.0.0 255.255.255.255 DHCP 371 DHCP Discover - Transaction ID 0xb444e919 Frame 142: 371 bytes on wire (2968 bits), 371 bytes captured (2968 bits) on interface 0 Ethernet II, Src: DavicomS_91:de:41 (00:60:6e:91:de:41), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol Message type: Boot Request (1) Hardware type: Ethernet Hardware address length: 6 Hops: 0 Transaction ID: 0xb444e919 Seconds elapsed: 13 Bootp flags: 0x0000 (Unicast) Client IP address: 0.0.0.0 (0.0.0.0) Your (client) IP address: 0.0.0.0 (0.0.0.0) Next server IP address: 0.0.0.0 (0.0.0.0) Relay agent IP address: 0.0.0.0 (0.0.0.0) Client MAC address: DavicomS_91:de:41 (00:60:6e:91:de:41) Client hardware address padding: 00000000000000000000 Server host name not given Boot file name not given Magic cookie: DHCP Option: (53) DHCP Message Type Option: (57) Maximum DHCP Message Size Option: (60) Vendor class identifier Option: (12) Host Name Option: (55) Parameter Request List Option: (255) End No. Time Source Destination Protocol Length Info 392 55.264802000 0.0.0.0 255.255.255.255 DHCP 371 DHCP Discover - Transaction ID 0xb444e919 Frame 392: 371 bytes on wire (2968 bits), 371 bytes captured (2968 bits) on interface 0 Ethernet II, Src: DavicomS_91:de:41 (00:60:6e:91:de:41), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol Version 4, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255) User Datagram Protocol, Src Port: bootpc (68), Dst Port: bootps (67) Bootstrap Protocol Message type: Boot Request (1) Hardware type: Ethernet Hardware address length: 6 Hops: 0 Transaction ID: 0xb444e919 Seconds elapsed: 29 Bootp flags: 0x0000 (Unicast) Client IP address: 0.0.0.0 (0.0.0.0) Your (client) IP address: 0.0.0.0 (0.0.0.0) Next server IP address: 0.0.0.0 (0.0.0.0) Relay agent IP address: 0.0.0.0 (0.0.0.0) Client MAC address: DavicomS_91:de:41 (00:60:6e:91:de:41) Client hardware address padding: 00000000000000000000 Server host name not given Boot file name not given Magic cookie: DHCP Option: (53) DHCP Message Type Option: (57) Maximum DHCP Message Size Option: (60) Vendor class identifier Option: (12) Host Name Option: (55) Parameter Request List Option: (255) End

这是我的理解，DHCP发现没有回答。 它是否正确？ 你知道为什么吗？

编辑：我试图再次使用wireshark检查数据包，我可以看到选项：（53）DHCP消息types。 通过扩展我看到DHCP发现。 这对我来说似乎是DHCP。 我还使用wireshark检查了Mac OS X DHCP数据包，并且在数据包中仍然看到“消息types：Boot Request（1）”。 唯一的区别是不发送DHCP发现，只是一个DHCP请求地址。 此外，相同的适配器不能在Windows 7下工作。

那么，这真的是bootp协议？ 你能证实吗？ 或者它是DHCP？ 为什么发送DHCP Discover消息但没有发送DHCP Offer？

问题是你的客户端不是说DHCP而是bootp 。 由于devise限制或configuration设置，并不是所有的dhcp服务器都可以处理bootp 。