Wednesday, July 05, 2017

Re: dhcrelay broken after Apr 5

> On 05.07.2017, at 11:41, Kapetanakis Giannis <bilias@edu.physics.uoc.gr> wrote:
>
> On 04/07/17 19:09, Reyk Floeter wrote:
>> Could you try again with the attached diff? It doesn't change
>> behavior but it adds some chatty logging when a packet is rejected.
>> Maybe it helps to find the issue.
>>
>> Reyk
>
> I've send the bug report as detailed as I could.
>

Thanks, now it is a good bug report and I think it helps to find the issue with carp+dhcrelay.

You had a typo in the email subject ;-)

> In a few words, applying your diff gave me these:
> Jul 5 11:53:09 dhcrelay[68565]: decode_hw_header:229: invalid htype 0
> Jul 5 11:53:09 dhcrelay[68565]: receive_packet:457: decode_hw_header failed, len 364
> Jul 5 11:53:10 dhcrelay[68565]: decode_hw_header:229: invalid htype 0
> Jul 5 11:53:10 dhcrelay[68565]: receive_packet:457: decode_hw_header failed, len 364
>

Reyk

No comments:

Post a Comment