Replies to request coming over a relay goes to relay's internal IP, not to original request's source IP

Simon Hobson dhcp1 at thehobsons.co.uk
Sun Oct 7 08:49:25 UTC 2012


Oguz Yilmaz wrote:
>I understand what you mean. According to basic networking this does
>not seem meaningful for me. DHCPD does not reply to the asking relay
>server:
>
>192.168.0.81.67 > 192.168.0.1.67: BOOTP/DHCP, Request from
>00:1e:68:06:eb:37, length: 300, hops:1,
>	Gateway IP: 172.16.17.81
>	Client Ethernet Address: 00:1e:68:06:eb:37 [|bootp]
>
>192.168.0.1.67 > 172.16.17.81.67: BOOTP/DHCP, Reply, length: 300, hops:1
>	Your IP: 172.16.17.11
>	Gateway IP: 172.16.17.81
>	Client Ethernet Address: 00:1e:68:06:eb:37 [|bootp]
>
>However, if you say this is how it works, I have nothing to say but thank you.

Yes, this is how it works.

>According to your comments a client for example 172.16.17.11 can
>directly try to talk with 192.168.0.1. So we should always have right
>path to 172.16.17.0 in routing table of dhcpd server.

Yes, there must be correct routing in place for client and server to 
be able to communicate directly.

-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.


More information about the dhcp-users mailing list