Regarding dhcp server behavior (Simon Hobson)

[Shweta Jogi]

Thanks Simon for your reply.

>  Can't see packets according to dhcpd logs, or can't see packets when using a packet sniffing tool (eg tcpdump or wireshark) ?

I am not able to see packets in dhcpd logs, and can see in tcpdump running on enp0s3. Also not able to see packet if tcpdump running on enp0s8.


>  You can change this by turning off a setting (something related to "use raw packets") and recompiling - then the server will just use the normal IP stack (but won't be able to handle local, ie not relayed, clients).



This solution is not feasible as server is also handling broadcast packets.



>  I suspect that in your case, you just need to change your relay invocation to send packets to 20.20.20.22 - the dhcp server will be listening on this interface and will see the packet.



If I configure 20.20.20.22 as Server IP address in relay, then things are working fine.

If server is running on enp0s3 (20.20.20.22), and it receives packet with destination 30.30.30.30, it should serve that packet ?

In my case it is serving the relay, and sending offer to the client, in this case server behavior is not predictable.



Regards,

Shweta Jogi


________________________________

Sophos Technologies Private Limited Regd. Office: Sophos House, Saigulshan Complex, Beside White House, Panchvati Cross Road, Ahmedabad - 380006, Gujarat, India CIN: U72200GJ2006PTC047857

Sophos Ltd, a company registered in England and Wales number 2096520, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20190324/f7b7674a/attachment-0001.html>