All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Mu De <soanican@gmail.com>
Cc: Simon Wunderlich <sw@simonwunderlich.de>,
	b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: IP connectivity issue at openwrt nodes
Date: Tue, 19 Nov 2024 16:11:51 +0100	[thread overview]
Message-ID: <2631894.Lt9SDvczpP@ripper> (raw)
In-Reply-To: <CACKXFERn_+LZ4ztxmfOwhUM91ccjVSAbTYf8U1ivS+0sXeJkWw@mail.gmail.com>

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

On Tuesday, 19 November 2024 15:59:58 CET Mu De wrote:
> "batctl o" shows empty table

Which means that the underlying link is not working. Either because the 
interface is down, not connected or is manipulating the transmitted OGMs 
(broadcast) in some form. The latter can for example happen if the underlying 
link is converting broadcasts to unicast - some accesspoints are doing that. I 
just mention this because you seem to use station interfaces as underlying 
interface for bat0.

You can use tcpdump on the underlying interface to see whether the submitted 
packets (OGMs) on one side are received exactly the same on the other side. 
Wireshark has support for batman-adv. So, you could easily check the recorded 
PCAPs with it.

You can also check "batctl n" to see on which side you can correctly "hear" 
OGM packets. If you can not hear it only on one side then you should check 
this one initially (but continue with the rest).

Kind regards,
	Sven

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

  parent reply	other threads:[~2024-11-19 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 19:44 IP connectivity issue at openwrt nodes soanican
2024-11-19  8:19 ` Sven Eckelmann
     [not found]   ` <CACKXFETaiEdriRp7rS2KfuFOcfXpcNe_y+4WfgRUW5t8R=MsLQ@mail.gmail.com>
2024-11-19 14:18     ` Sven Eckelmann
2024-11-19 14:24     ` Sven Eckelmann
2024-11-19 15:02       ` soanican
     [not found]       ` <CACKXFERn_+LZ4ztxmfOwhUM91ccjVSAbTYf8U1ivS+0sXeJkWw@mail.gmail.com>
2024-11-19 15:11         ` Sven Eckelmann [this message]
2024-11-19 21:58           ` soanican
2024-11-19 22:22             ` Sven Eckelmann
2024-11-20 10:20               ` soanican
2024-11-19 14:21 ` soanican

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=2631894.Lt9SDvczpP@ripper \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=soanican@gmail.com \
    --cc=sw@simonwunderlich.de \
    /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.