For beginners, explain the difference between meshpoint and adhoc IBSS

[jedahan]

Hiya!

I've got adhoc mode working in a project, and was wondering what the main differences / benefits would be if I were to switch from plain old adhoc IBSS to meshpoint. If someone more familiar could write something on the wiki that would rule.

Thanks!

[chunyeow]

802.11 adhoc mode is peer-to-peer routing and requires the upper layer protocol stack (layer 3 and above) to handle multi-hop scenario. 802.11s or mesh allows MAC or layer 2 multi-hop routing whereby your a Mesh STA can assist in forwarding the frame from other STAs to its destination if all belongs to same MBSS. Take example of home routers nowadays, those offering the mesh solution are running 802.11s.

…

On Tue, Aug 14, 2018 at 12:41 AM Jonathan Dahan ***@***.***> wrote: Hiya! I've got adhoc mode working in a project, and was wondering what the main differences / benefits would be if I were to switch from plain old adhoc IBSS to meshpoint. If someone more familiar could write something on the wiki that would rule. Thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#78>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABBewgqa0UnBF11uFwo8u36-_XNbWtjaks5uQawtgaJpZM4V62HU> .

[freedombird]

Good explain. Is there a packages flow between two Mesh point ? and how about the encryption mode PSK? Is it the same with AP mode, need to go 4-way handshake? Chun-Yeow <notifications@github.com> 于2018年8月14日周二 上午9:46写道：

…

802.11 adhoc mode is peer-to-peer routing and requires the upper layer protocol stack (layer 3 and above) to handle multi-hop scenario. 802.11s or mesh allows MAC or layer 2 multi-hop routing whereby your a Mesh STA can assist in forwarding the frame from other STAs to its destination if all belongs to same MBSS. Take example of home routers nowadays, those offering the mesh solution are running 802.11s. On Tue, Aug 14, 2018 at 12:41 AM Jonathan Dahan ***@***.***> wrote: > Hiya! > > I've got adhoc mode working in a project, and was wondering what the main > differences / benefits would be if I were to switch from plain old adhoc > IBSS to meshpoint. If someone more familiar could write something on the > wiki that would rule. > > Thanks! > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#78>, or mute the thread > < https://github.com/notifications/unsubscribe-auth/ABBewgqa0UnBF11uFwo8u36-_XNbWtjaks5uQawtgaJpZM4V62HU > > . > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#78 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABVt9EMl_ptdkvZdelWyrXVT3ylpvm78ks5uQivlgaJpZM4V62HU> .

[chunyeow]

You can look at the SAE (https://github.com/cozybit/authsae) and AMPE for this.

…

---- Chun-Yeow On Thu, Sep 27, 2018 at 5:15 PM freedombird <notifications@github.com> wrote:

Good explain. Is there a packages flow between two Mesh point ? and how about the encryption mode PSK? Is it the same with AP mode, need to go 4-way handshake? Chun-Yeow ***@***.***> 于2018年8月14日周二 上午9:46写道： > 802.11 adhoc mode is peer-to-peer routing and requires the upper layer > protocol stack (layer 3 and above) to handle multi-hop scenario. > > 802.11s or mesh allows MAC or layer 2 multi-hop routing whereby your a Mesh > STA can assist in forwarding the frame from other STAs to its destination > if all belongs to same MBSS. > > Take example of home routers nowadays, those offering the mesh solution are > running 802.11s. > > On Tue, Aug 14, 2018 at 12:41 AM Jonathan Dahan < ***@***.***> > wrote: > > > Hiya! > > > > I've got adhoc mode working in a project, and was wondering what the main > > differences / benefits would be if I were to switch from plain old adhoc > > IBSS to meshpoint. If someone more familiar could write something on the > > wiki that would rule. > > > > Thanks! > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > <#78>, or mute the thread > > < > https://github.com/notifications/unsubscribe-auth/ABBewgqa0UnBF11uFwo8u36-_XNbWtjaks5uQawtgaJpZM4V62HU > > > > . > > > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#78 (comment)>, or mute > the thread > < https://github.com/notifications/unsubscribe-auth/ABVt9EMl_ptdkvZdelWyrXVT3ylpvm78ks5uQivlgaJpZM4V62HU > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#78 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABBewuDOSJSrNcRvh_6FWbn0u5AHCJypks5ufJcagaJpZM4V62HU> .

[darkdrgn2k]

From what i understand (correct me if I'm wrong) If you skip the actually traffic forwarding (actual meshing since it only can mesh WIRELESS connections not wired) other advantages are

• Meshpoint support is also much better then AdHoc (IBSS) support. Many devices say they support IBSS but in fact its old code that has not been maintained for years.

• IBSS "Standard" is old as well, officially as far as i know supporting only 80211b (not to say that manufactures dont "Break" the standard supporting even AC)

• It has more functionality to deal with wireless connections (ie set a min signal strength threshold)

Also as to add to a point made above

upper layer protocol stack (layer 3 and above) to handle multi-hop scenario.

Unless you use another layer 2 meshing protocol (like batman-adv) that will do this on layer 2.