On 10/26/20 6:58 AM, Joakim Tjernlund wrote:
> Ping (maybe it should read "arping" instead :)
>
> Jocke
>
> On Thu, 2020-10-22 at 17:19 +0200, Joakim Tjernlund wrote:
>> strace arping -q -c 1 -b -U -I eth1 0.0.0.0
>> ...
>> sendto(3, "\0\1\10\0\6\4\0\1\0\6\234\v\6
>> \v\v\v\v\377\377\377\377\377\377\0\0\0\0", 28, 0, {sa_family=AF_PACKET,
>> proto=0x806, if4, pkttype=PACKET_HOST, addr(6)={1, ffffffffffff},
>> 20) = -1 ENOBUFS (No buffer space available)
>> ....
>> and then arping loops.
>>
>> in 4.19.127 it was:
>> sendto(3,
>> "\0\1\10\0\6\4\0\1\0\6\234\5\271\362\n\322\212E\377\377\377\377\377\377\0\0\0\0",
>> 28, 0, {sa_family=AF_PACKET, proto=0x806, if4, pkttype=PACKET_HOST,
>> addr(6)={1,
>> ffffffffffff}, 20) = 28
>>
>> Seems like something has changed the IP behaviour between now and then ?
>> eth1 is UP but not RUNNING and has an IP address.
>>
>> Jocke
>
do a git bisect between the releases to find out which commit is causing
the change in behavior.
