Re: DHCP relay - wrong interface for relayed packet

On 07/07/2022 17:37, Paul Thornton wrote:

That then exposed another issue - more relating to the original patch to change the destination port relayed to.  Of course, when I send to port 1067, the upstream DHCP server sends the reply on 1067 - which the relay isn't listening on.  So the OFFER goes into the void.

Ah - I noticed this the first time, but wasn't sure if it actually mattered (any "normal" protocol would flip the src/dest ports, right? but we are talking DHCP here...)

I think the proper fix for that is to ensure that the relay is listening on any alternative port; but my knowledge of the inner workings of the

What happens if you just add a listen{} section on port 1067? -- Matthew