DHCP Relay Not configured properly?

[LateLearn]

I have the following topology:

I'm simply trying to relay the role of DHCP server from router0 to router1.

router0 is pretty much just:

and router1 looks correct to me as well:

I'm not sure where I went wrong. The helper address is 192.168.0.2 which is the "broadcast/ dora facing" interface of Router1 ( the router that also is supposed to be serving as the DHCP server, having the pool and all).

Router0 only needs the helper address of that interface right?

The client on the left still isn't getting ip addresses from the server.

[Georg Pauwen]

Hello,

The default router address in your pool doesn't look right, it is not in the same address space as the network of the pool...

[luis_cordova]

Hi @LateLearn,

Change this in your DHCP configuration:

ip dhcp pool test 

network 172.16.0.0 255.255.0.0

default-router 172.16.0.1

dns-server 8.8.8.8

Regards

[Alan Ng'ethe]

Hi,

I have reproduced this issue in GNS3 and the below are my observations:

1.Started off with no IP on the client.

2. When I attempt to renew the client IP address, the following happens

 The client does not appear to get past the discover (D) phase. 

After turning on the relevant debugs on both routers as the discover was running, I was able to see the following:

So R2 appears to be correctly working as a relay agent (see above). 

So is R1 as a DHCP server, as shown above.

Unsurprisingly, querying the pool on R1 reveals the following:

The server is assigning addresses as expected. But the client still has not received an IP address!

For the sake of brevity, the only changes I did to make it work was to add a route back to the 172.16.0.0/16 subnet on router 1. Only then was the client able to get an IP from the scope defined on the pool. (See complete logs below).

 
Hope this helps.