All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Matteo Fortini" <matteo.fortini@gmail.com>,
	"Antonio Quartulli" <antonio@mandelbit.com>,
	"Linus Lüssing" <linus.luessing@c0d3.blue>
Subject: Re: Multiple ARP replies for same address on openwrt module 6.6.69.2024.3-r3
Date: Thu, 09 Jan 2025 11:55:23 +0100	[thread overview]
Message-ID: <4646493.cEBGB3zze1@ripper> (raw)
In-Reply-To: <74e4f2ce-5629-4816-93ee-f8b3ed3891e2@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]

On Thursday, 9 January 2025 11:31:06 CET Matteo Fortini wrote:
> I am noticing random unreachability of hosts in my network, in 
> particular if I just nmap -sP the whole range.
> 
> I traced it down to ARP poisoning, and the source seems to be two hosts 
> running batman-adv which are claiming the same address.
[...]
> 
> issue is, 02:00:06:bb:00:07 is not the right node and the host is 
> unreachable. The other MAC is the right one.
> 
> If I clear the ARP cache in my source host, then the remote host is 
> reachable again as it gets the right answer.

Might be DAT related. But I am not sure of it. Can you please add the output 
of

$ batctl mj

to see the (batadv interface specific) configuration.

This might be helpful for Antonio/Linus. If it is enabled, you could also try 
to disable it on all involved hosts via:

$ batctl dat disable

Just to see if it has any influence on the behavior (to see if there is any 
ARP poisoning in the long run - not to solve the intermediate problem).


> The problem started after updating to the 24.10RC series of openwrt.

When you used 23.05.x before, then this would suggest that it was introduced 
somewhere between 2023.1 and 2024.3 (or OpenWrt) somehow.

I didn't test it but a quick check in the sources suggest that the 23.05 
batman-adv sources (from the routing feed) should also work with 24.10 - so 
you could actually git-bisect openwrt routing from 
6afc0452c2534ed0bc65b59b1fb6fd74439ddf27 to 
eaa4aba30b017de66bece8ef9d3dde5299fc787d

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-01-09 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 10:31 Multiple ARP replies for same address on openwrt module 6.6.69.2024.3-r3 Matteo Fortini
2025-01-09 10:55 ` Sven Eckelmann [this message]
2025-01-09 11:32   ` Matteo Fortini
2025-01-09 12:47     ` [SOLVED] " Matteo Fortini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4646493.cEBGB3zze1@ripper \
    --to=sven@narfation.org \
    --cc=antonio@mandelbit.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=linus.luessing@c0d3.blue \
    --cc=matteo.fortini@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.