I have a DHCP-server configured at my edge router (server). At the LAN we have a MKT whith a default GW pointed to the edge router and at its LAN there is a second MKT. This last one has a dhcp-relay configured to the edge router but the hosts connected to the second MKT don’t recive any IP from the server. Capturing traffic at the edge router I don’t see anythig related with the DHCP, is it possible that the first MKT is filtering the DHCP discover?
NOTE: The network is routed statically and every object in it can see each other. In fact if we force an IP of the correct range (that should be assigned by the dhcp-server) then the equipment can surf the internet without any troubble.
PS: This is the command that I’m using to configure the dhcp-raly:
ip dhcp-relay add name=WISPRO interface=bridge_de_red dhcp-server=10.0.10.1 local-address=10.58.21.1 disabled=no
Capturing traffic at the edge router I don’t see anythig related with the DHCP, is it possible that the first MKT is filtering the DHCP discover?
Could be… have you torched MKT1 ether wired to MKT2 to see if DHCP requests are present?
It should work. There is a silly mistake somewhere (not visible in your picture).
Note that it is not relevant there is a cascade. The dhcp-relay is configured on the router where DHCP should be available
for the clients, and it points to the IP of the actual server that can be in an entirely different part of the network. I regularly
have this working over 4 hops or so.
UPDATE: There was a thundercache at the middle that the client forgot to comment. After a few routes configurations the result was the expected. In fact I’ve now configured a few more nodes and the relay hops at least 4 times without any trouble.
Thanks for your cooperation guys!