All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: mbiglari4@gmail.com
Subject: Re: Gateway shut down detection takes too time from other nodes
Date: Wed, 15 Oct 2025 10:05:16 +0200	[thread overview]
Message-ID: <9767419.DvuYhMxLoT@prime> (raw)
In-Reply-To: <176039145278.1493.3258424615578163774@diktynna.open-mesh.org>

Hi,

can you describe your setup a bit more? Are your "gateways" connected with 
each other over Ethernet? Do you have multiple DHCP servers on your gateways 
respectively, or is there a DHCP server in your LAN interconnecting gateways? 
Are you using bridge loop avoidance? Perhaps an illustration would help.

There are different scenarios how to set up this network kind of network, and 
failover time  may differ from a couple of seconds to a couple of minutes 
depending on the setup.

Thank you,
        Simon

On Monday, October 13, 2025 11:37:32 PM Central European Summer Time 
mbiglari4@gmail.com wrote:
> Dear readers,
> 
> I have implemented a Mesh network with Wifi nodes on 802.11s and BATMAN adv.
> My mobile nodes are mesh nodes, and I am using 802.11s to create a mesh
> network. Within this network, some nodes act as servers and others as
> clients. Suppose one of the nodes is selected as a gateway by the clients.
> The problem is that when this gateway node powers off, the other nodes do
> not immediately detect this change, and it takes a long time for them to
> recognize and switch to a new server as the gateway.





  reply	other threads:[~2025-10-15  8:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 21:37 Gateway shut down detection takes too time from other nodes mbiglari4
2025-10-15  8:05 ` Simon Wunderlich [this message]
2025-10-23 12:28   ` mbiglari4
2025-10-24 10:03     ` Simon Wunderlich
2026-04-07 13:46       ` martinvdberg
2026-04-15 15:10         ` Simon Wunderlich
2026-04-16  5:46           ` Simon Wunderlich
2026-04-17  7:49             ` Martin
2026-04-20 12:06               ` Simon Wunderlich
     [not found]                 ` <T9GBvsX7uc7S-GxsAnHMFg5oj-euOauWkNTXi2SouU2ow1oX1yogmMCi6FW7mXlFuZ3D9zMBiIGARWa2UDobQ2S0OrY8To4neWUtWArNXzw=@protonmail.com>
2026-04-22 14:21                   ` Simon Wunderlich

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=9767419.DvuYhMxLoT@prime \
    --to=sw@simonwunderlich.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=mbiglari4@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.