Suse Linux Enterprise 10 Server 不回應(yīng)DHCP-NAK的問題，歡迎大家討論！

xiash028

大家好：
      一個無線終端，先是入到的一個子網(wǎng)下面，該子網(wǎng)下的dhcp server分配的ip如（192.168.1.***）,24位掩碼，此時獲取的ip位192.168.1.10。改變終端的地理位置，由于該終端插在了windows 7 操作系統(tǒng)上，該操作系統(tǒng)具有較強的記憶功能，此時繼續(xù)發(fā)送dhcp-request，攜帶的請求ip仍然是192.168.1.10，在這個新的地理位置上DHCP Server分配的是(192.168.2.***)，24位掩碼。此時終端一直發(fā)送request請求，按照協(xié)議的理解是新的dhcp server應(yīng)該回應(yīng)NAK消息的。但是，通過在server上抓包看到只有request消息，server不給終端回應(yīng)NAK消息。   終端獲得不了新的ip，所以就一直不能入網(wǎng)做業(yè)務(wù)。 我們通過在筆記本上執(zhí)行ipconfig/release,renew規(guī)避。
      現(xiàn)在的問題是server為什么不回應(yīng)nak消息�。�

      我在網(wǎng)絡(luò)上搜索了如下這一段，不知道有無關(guān)系？


      When a Windows NT DHCP client is moved to another subnet (without issuing the ipconfig/release command before moving), the client will request its previous IP address. Usually this IP address is not valid for usage on the new subnet.

When a DHCP server detects that the client requests an IP address that does not fit for the current subnet, the DHCP server must send a DHCPNAK to the client (according to RFC1541).

Some non-rfc compliant DHCP servers do not send this DHCPNAK. Because of this, the client does not attempt to lease a new IP address on the new subnet and tries to use its old IP address (see the frame information later in this article).

This problem has been experienced only when using a third-party DHCP server. The Microsoft Windows NT DHCP server does not experience this behavior.