That code is only being executed because your DHCP relay is including
the agent-id option in requests with sub-option 11, server-identifier
override.
It would be worth reading RFC 5107 to get more background on this.
The idea is that the server-identifier IP address in the DHCP exchange
should be
Hello,
Does anyone have an issue if we make the change below?
If we keep the code then at the very least the code should log why we are
failing.
Take Care
Jason
> On Sep 28, 2017, at 4:44 PM, Jason Kary wrote:
>
> Hi Folks,
>
> I was able to fix the problem by removing the following code:
Hi Folks,
I was able to fix the problem by removing the following code:
lines 1107-1108 in rfc2131.c:
if (option_addr(opt).s_addr != override.s_addr)
return 0;
Once I commented out this if statement the client was able to obtain the
correct IP address via
Hi Folks,
I wanted to follow up and see if anyone is available to help debug this issue?
I won’t have the test bed available to me to help out for much longer.
Is there some sort of debug that I could collect to help with the analysis?
Take Care
Jason
> On Sep 25, 2017, at 4:11 PM, Jason Kary
Hi Chris,
I cloned the GIT repository and tested with version 2.78test2-gb697fbb
I’m still seeing the server fail to respond to the request message:
Frame 40189 (388 bytes on wire, 388 bytes captured)
Arrival Time: Sep 25, 2017 20:59:01.142813000
[Time delta from previous captured frame:
On 22/09/2017 19:24, Jason Kary (jkary) wrote:
> Thank you for the update. We are running version 2.66
2.66 is four and a half years old now, and those parts of the codebase
have been overhauled quite a lot since then --- is there any way you can
test your setup with 2.77 plus the patch in [2] fr
Hi Chris,
Thank you for the update. We are running version 2.66
Take Care
Jason
> On Sep 22, 2017, at 8:44 AM, Chris Novakovic wrote:
>
> On 22/09/2017 13:42, Chris Novakovic wrote:
>> If you're using 2.76,
>
> It's implied by my later comment, but I should also clarify that this
> bug affect
On 22/09/2017 13:42, Chris Novakovic wrote:
> If you're using 2.76,
It's implied by my later comment, but I should also clarify that this
bug affects 2.77 as well as 2.76.
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://
On 21/09/2017 14:15, Jason Kary (jkary) wrote:
> I’m working on getting DNSMASQ to work with IP RELAY in a VxLAN environment.
> Using tcpdump we were able to trace a DHCP relay request to the ‘request’
> message. It appears the server is not sending an DHCP ACK message.
Which version of dnsm
Hi Folks,
I’m working on getting DNSMASQ to work with IP RELAY in a VxLAN environment.
Using tcpdump we were able to trace a DHCP relay request to the ‘request’
message. It appears the server is not sending an DHCP ACK message.
Here is a tcpdump of the request message:
11:18:56.868214 IP (
10 matches
Mail list logo
