b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
* Batman adv selective broadcast mechanism
@ 2021-03-24 12:16 oytunyapar
  2021-03-24 13:27 ` Linus Lüssing
  0 siblings, 1 reply; 5+ messages in thread
From: oytunyapar @ 2021-03-24 12:16 UTC (permalink / raw)
  To: b.a.t.m.a.n

Hi everybody,

    As I check, batman-adv protocol, sends IP broadcast packets, to every slave interface, including the slave interface from which the broadcast packet is received. Is there any way for preventing the batman-adv from sending IP broadcast packets to some of the slave interfaces (etc. the one which the packet is received)?

Regards.
Oytun

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Batman adv selective broadcast mechanism
  2021-03-24 12:16 Batman adv selective broadcast mechanism oytunyapar
@ 2021-03-24 13:27 ` Linus Lüssing
  2021-03-25 12:58   ` oytunyapar
  0 siblings, 1 reply; 5+ messages in thread
From: Linus Lüssing @ 2021-03-24 13:27 UTC (permalink / raw)
  To: The list for a Better Approach To Mobile Ad-hoc Networking

Hi,

On Wed, Mar 24, 2021 at 12:16:16PM -0000, oytunyapar@hotmail.com wrote:
> Hi everybody,
> 
>     As I check, batman-adv protocol, sends IP broadcast packets, to every slave interface, including the slave interface from which the broadcast packet is received. Is there any way for preventing the batman-adv from sending IP broadcast packets to some of the slave interfaces (etc. the one which the packet is received)?

When there is just a single neighbor on the interface a node
received the packet on that batman-adv avoids sending it
back automatically. E.g. this case here:

https://www.open-mesh.org/projects/batman-adv/wiki/Broadcast#IIII-Single-Neighbor-Is-Previous-Sender

If there are multiple neighbors on the receiving interface then
batman-adv assumes that other neighbors might potentially not have
received the packet from the original sender. And will therefore
rebroadcast on the incoming interface, too.

If you are 100% sure that all other neighbors received it from
the original sender then there is this old patch which isn't
upstream though (including the discussion with why it was
rejetected for upstream):

https://patchwork.open-mesh.org/project/b.a.t.m.a.n./patch/1380030033-11533-1-git-send-email-linus.luessing@web.de/

Regards, Linus

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Batman adv selective broadcast mechanism
  2021-03-24 13:27 ` Linus Lüssing
@ 2021-03-25 12:58   ` oytunyapar
  2021-03-28 21:18     ` Linus Lüssing
  0 siblings, 1 reply; 5+ messages in thread
From: oytunyapar @ 2021-03-25 12:58 UTC (permalink / raw)
  To: b.a.t.m.a.n

Hi Linus,

    Thank you for the answer. Configuring batman-adv from /sys is deprecated in the last version (batctl is the only way now). I am not sure how to apply this patch. What do you suggest as a proper way of doing this?

Regards.
Oytun

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Batman adv selective broadcast mechanism
  2021-03-25 12:58   ` oytunyapar
@ 2021-03-28 21:18     ` Linus Lüssing
  2021-03-31  9:06       ` oytunyapar
  0 siblings, 1 reply; 5+ messages in thread
From: Linus Lüssing @ 2021-03-28 21:18 UTC (permalink / raw)
  To: The list for a Better Approach To Mobile Ad-hoc Networking

Hi Oytun,

Are you able to recompile the kernel module and batctl? If so, I
could have a look at updating that patch for a more recent
batman-adv version.

Actually, I'm also kind of curious about your use-case. Sounds
like it's not 802.11 wifi you are using, right?

Regards, Linus


On Thu, Mar 25, 2021 at 12:58:15PM -0000, oytunyapar@hotmail.com wrote:
> Hi Linus,
> 
>     Thank you for the answer. Configuring batman-adv from /sys is deprecated in the last version (batctl is the only way now). I am not sure how to apply this patch. What do you suggest as a proper way of doing this?
> 
> Regards.
> Oytun

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Batman adv selective broadcast mechanism
  2021-03-28 21:18     ` Linus Lüssing
@ 2021-03-31  9:06       ` oytunyapar
  0 siblings, 0 replies; 5+ messages in thread
From: oytunyapar @ 2021-03-31  9:06 UTC (permalink / raw)
  To: b.a.t.m.a.n

Hi Linus,

    I hard coded it, instead of making a configuration. We could use with this way.
    You are correct Linus, it's not 802.11 wifi. We are using MARLIN protocol (NATO STANAG-4691).
    This protocol aims for gaining TCP/IP features to HF and UHF radios.
    We are using BATMAN protocol, for inter-MARLIN network routing. MARLIN itself has features for handling routing, internally, for a single  MARLIN network.

Regards.
Oytun

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-03-31  9:06 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-24 12:16 Batman adv selective broadcast mechanism oytunyapar
2021-03-24 13:27 ` Linus Lüssing
2021-03-25 12:58   ` oytunyapar
2021-03-28 21:18     ` Linus Lüssing
2021-03-31  9:06       ` oytunyapar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).