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" <b.a.t.m.a.n@lists.open-mesh.org>
Cc: Jingwei LI <marscatcn@live.com>
Subject: Re: Limited Connectivity in Mixed Wired & Wireless Backhaul Deployment
Date: Sun, 16 Mar 2025 13:30:37 +0100	[thread overview]
Message-ID: <8603745.T7Z3S40VBb@sven-l14> (raw)
In-Reply-To: <OS3PR01MB576553C5DACFE878AF2C6878D5DC2@OS3PR01MB5765.jpnprd01.prod.outlook.com>

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

On Sunday, 16 March 2025 11:07:17 GMT+1 Jingwei LI wrote:
> ```
>    Router A             Router B                Router C
> _____________     ___________________       ________________
> |    br-lan    |      |         br-lan        |      |     br-lan         |
> |____________|     |__________________|      |________________|
> |AP|   bat0  |     |AP|      bat0          |      |AP|     bat0      |
> |___|________|     |___|_______________|      |___|____________|
>    |lan|BHAP|         |STA| lan | BHAP|           |STA| BHAP |
>    |___|______|         |____|_____|______|           |____|_______|
>      ^     ^----WiFi--^     ^      ^-----WiFi---^
>       |______Eth_Cable_____|  
> ```

This is completely distorted in a fixed width character (editor). Is router C 
required to see the problem? Because only router A and B are mentioned in the 
problem description.

Is the ethernet cable connection required to trigger the problem?

> Problem description:
> 
> Router A (192.168.6.1) and Router B (192.168.6.2) can ping each other. The client (192.168.6.192) associating with Router B cannot ping Router A and its associating client.
> I also wrote some simple rules to trace the data frames in each router, below is the output for a ping from client associating with Router B (192.168.6.2) to Router A (192.168.6.1):

At which point are the packets dropped from client to client? The "trace" you 
showed me looks like output from iptables (or actually its kernel part 
"netfilter") - which is above bat0 (and therefore not in control of batman-
adv). If you want to figure out something on layer 2, please use tcpdump to 
capture packets on the various interfaces involved here (bridge, ap, bat0, 
lan, BHAP, ...) and then check what happens. You can analyze pcaps recorded by 
tcpdump using a somewhat recent wireshark version

How does you bridge loop avoidance configuration look like and what is the 
backbone and claim (table) state?

What is the content of the translation tables?

Kind regards,
	Sven

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

  parent reply	other threads:[~2025-03-16 12:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-16 10:07 Limited Connectivity in Mixed Wired & Wireless Backhaul Deployment Jingwei LI
2025-03-16 12:17 ` Sven Eckelmann
2025-03-16 12:30 ` Sven Eckelmann [this message]
2025-03-16 13:21   ` Jingwei LI
2025-03-16 13:27   ` marscatcn

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=8603745.T7Z3S40VBb@sven-l14 \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=marscatcn@live.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.