192.168.7.1 192.168.7.2----10.1.1.1 10.1.1.2 ---- 220.127.116.11
Win DHCP Server 1 ---Linux DHCP Server 2------Linux DHCP relay -------Win XP DHCP client PC
Routing mode Routing mode
Win DHCP Server 1 : IP address 192.168.7.1
Linux DHCP Server 2 : 192.168.7.2 , 10.1.1.1 ( As its in routing mode)
Linux DHCP relay : 10.1.1.2 , 18.104.22.168
Win XP DHCP Client : Has to get IP from DHCP servers.
Config/ Observations 1:
1) DHCP server 1 is disabled, now only one server is present in the network.
2) In DHCP relay the DHCP server is mentioned as 10.1.1.1 and client interface as 22.214.171.124
3) On DHCP server in the config file (dhcpd.conf) subnet is defined for 126.96.36.199 network, make a note that this subnet is not part of the subnet on which server is runnning ( server is running on 192.168.7.2 and 10.1.1.1.)
4) Start DHCP client on windows PC, the DHCP discover can be seen on Linux DHCP Server , but it is not replying to the discover.As i know, if the subnets configured are not of the same subnet as one of its interfaces the DHCP server will not reply. So this is expected behavior. ( Correct me if I am wrong , i am trying to find supporting links, will update on this also)
Config/ Observations 2:
1) Now start Windows DHCP Server 2 and on DHCP relay configure the DHCP server as 192.168.7.1 and client interface as 188.8.131.52
2) Again run "ipconfig/release" and "ipconfig /renew" on the WIndows DHCP client PC.
3) On Linux PC forwarding is enabled and it is forwarding the "unicast DHCP DISCOVER" packet to the Windows Server.
4) Now suddenly both Linux DHCP Server starts working and it start replying along with the Windows DHCP server. Both the servers are replying for the intended subnets (184.108.40.206) , even though the DHCP discover packet is not intended for the Linux server.
The question is why the Linux server is replying now? As it is supposed to reply only to the connected interfaces IP subnets.
I am still trying to find answers, if you have any comments/ideas let me know in comments.
Keep Researching !