uawei.com) to take a look.
> > > >
> > > >
> > > > >
> > > > > Jocke
> > > > >
> > > > > On Mon, 2020-10-26 at 12:31 -0600, David Ahern wrote:
> > > > > >
> > > > > > On 1
;>
>>> Adding the author of that patch (linyunsh...@huawei.com) to take a look.
>>>
>>>
>>>>
>>>> Jocke
>>>>
>>>> On Mon, 2020-10-26 at 12:31 -0600, David Ahern wrote:
>>>>>
>>>
take a look.
> >
> >
> > >
> > > Jocke
> > >
> > > On Mon, 2020-10-26 at 12:31 -0600, David Ahern wrote:
> > > >
> > > > On 10/26/20 6:58 AM, Joakim Tjernlund wrote:
> > > > > Ping (maybe it
>>
>> Jocke
>>
>> On Mon, 2020-10-26 at 12:31 -0600, David Ahern wrote:
>>>
>>> On 10/26/20 6:58 AM, Joakim Tjernlund wrote:
>>>> Ping (maybe it should read "arping" instead :)
>>>>
>>>> Jocke
>>>>
> for lockless qdisc" (749cc0b0c7f3dcdfe5842f998c0274e54987384f)
>
> Reverting that commit on top of our tree made it work again. How to fix?
This is odd. The above commit touches the netdev reset path, did
your netdev get reset when you ran arping? You said your eth1 is UP,
is it always UP or
t;
>> 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
on top of our tree made it work again. How to fix?
Jocke
On Mon, 2020-10-26 at 12:31 -0600, David Ahern wrote:
>
> On 10/26/20 6:58 AM, Joakim Tjernlund wrote:
> > Ping (maybe it should read "arping" instead :)
> >
> > Jocke
> >
> > O
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\
On Mon, 26 Oct 2020 12:58:16 + Joakim Tjernlund wrote:
> 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
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
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, },
20) = -1 ENOBUFS (No buffer space available)
and t
From: Amit Cohen
Starting from iputils s20190709 (used in Fedora 31), arping does not
support timeout being specified as a decimal:
$ arping -c 1 -I swp1 -b 192.0.2.66 -q -w 0.1
arping: invalid argument: '0.1'
Previously, such timeouts were rounded to an integer.
Fix this by spec
Instead of relying on "arping" being installed everywhere under that
name, introduce a variable $ARPING like the other tools do.
Convert an existing test, mirror_gre_vlan_bridge_1q.sh to
require_command $ARPING and then invoke arping through the variable.
Signed-off-by: Petr Machata
Someone filed a bug at bugs.gentoo.org reflecting a possible
enhancement to arping. In short the patches author felt that select
should be used instead of signals to avoid missing a timeout.
The bug is located at:
http://bugs.gentoo.org/show_bug.cgi?id=144526
The diff follows:
--- arping.c
14 matches
Mail list logo
