B.A.T.M.A.N or 802.11.s or Repeaters daisy chain

What would you say is the best method for the next use case:

  1. The system consists of a ad-hoc linear “daisy chain” of wifi repeaters that extend the effective wlan from a gateway router throughout a linear space such as a corridor for example.
  2. The main use case: A human operator will walk away from the gateway switching on the identical units one by one. The units will automatically define the path. Wifi client devices will be free to roam through the corridor and have seamless connection to the main gateway.
  3. This paper addresses only the R units in the attached sketch.
  4. The units are identical and will act like a repeater - softAP+STA at the same time or an MP. no DHCP, no firewalls.
  5. The units consist of a new hardware with two versions - 1. 802.11.n 2.4 GHZ with low power consumption and lower performance. 2. 802.11.ac\ax Dual band with higher power consumption and higher performance.
  6. Failover - when a signal from the previous AP or MP is under the threshold RSSI the unit will scan for an alternative path. No closed loops are allowed of course.

Are you using vlans?

no. no need for vlans

Totally depends.
Could be you are served well with 11s and it's build in forwarding.
Could be batman version 5 serves you well.
Could be depending on the distance you need to tune tx power.
Given; so called repeater mode even sucks more.

But depends of what? :slight_smile:
what are the pros and cons for batman vs only 11s for example in this use case?

You could or even should ask at the mailing list of the wireless battle of the mesh for data on this scenario.

My stomach tells me in every case, for layer 2, tuned tx power and batman on 11s works well enough.

Edit ps https://www.battlemesh.org/ContactUs

In my opinion there is no added value for batman in this scenario (no vlans).

2 Likes

You need any form of spanning tree anyway and STP is still to heavy and slow. So even without vlans, batman provides a benefit here.

1 Like

Sorry, i don't see the risk for loops easily in this kind of architecture.

I would argue that even if you really do well tune your tx power shit can hit the fan. If you can't ensure that you really can not get a loop, then running without any form of STP is just dump.
Sure I have done so too.

But if something breaks, most of the time it will never recover so you go around and power cycle everything....

1 Like

I have run a 12 node 802.11s, mesh many years without stp without fatal loops. I added the batman for vlans, Basically I'm a kiss (keep ist simple stupid) kind of fool.

If you're saying it has to work regardless of the physical order of how the devices are placed (a person taking them out of a box at random), that will require a mesh protocol. It is possible to use a chain of repeaters but each one's STA needs to be pre-configured to BSSID locked to the MAC address of the one upstream of it in line. Otherwise a group of units can connect together in useless loops instead of to the proper one that gives it a path to the control system.

2 Likes

Batman has per default options the loop avodance feature enabled. Which is good.

1 Like

Yes It's built in but not enabled by default, Using it nowadays.

I would bet or would have been sooooo certain that's a default on OpenWrt.

1 Like

Yet again, I smell a rat.
Do we have someone wanting us to do their school homework for them, or am I just getting very cynical in my old age?

Copied straight of an old exam paper...

Nice bit of word salad.....

Definitely an old exam paper....

Yup, exam paper, confirmed.

Person setting exam paper: "Lets see if the students have done their revision, lets state something that is just plain silly and see if they notice."

"Add a snippet of information that is irrelevant"

"We said it was a daisy chain, but now throw in something that can't happen with a daisy chain - just to really sort the men from the boys "

And last but not least, put in a diagram showing a very nice daisy chain of cabled access points - that should really confuse them.....

Sorry, but ... not sorry.

2 Likes

Answering your initial question: YES, you smell wright. The problem to be solved "by chance" is very similar to a 2 days old project offering on a well known job site. Thus, either one of the bidders wants us to do the work for him, or the project provider tries to get the work done for free. BTW, I have seen this a few times here on the forum already.

1 Like

i think this is the problem. if you want a daisychain, you should enforce that with distinct wds links between adjacent links. if you want some fallback protection, use 802.11s.

1 Like

You probably mean right not wright

Looking shouldn't happen in a single network. The problem only happens when there are multiple paths for data to reach a destination.