public inbox for b.a.t.m.a.n@lists.open-mesh.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: Maurice Smulders <Maurice.Smulders@windtalker.com>,
	linux-wireless@vger.kernel.org
Subject: Re: MediaTek MT7612u and IBSS mode
Date: Fri, 11 Jun 2021 08:48:10 +0200	[thread overview]
Message-ID: <4182303.XkkeXVZP1n@ripper> (raw)
In-Reply-To: <4E744A61-BBA0-404E-B435-23C26ACF031B@windtalker.com>

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

On Friday, 11 June 2021 03:55:29 CEST Maurice Smulders wrote:
> Platform: Raspberry Pi 4B / CM4 with CentOS 8 stream 64 bit - 5.10.42 kernel
> 
> Trying to use this Mediatek USB device and I notice a - quite nasty - problem using IBSS mode. On startup of the IBSS network, there is a chance the Pi goes into a tizzy 	https://github.com/openwrt/mt76/issues/543 - when it's the first (and only) node.
> I was able to dupe it consistently in my home - fairly static network - but not anymore in a lab environment. I cannot easily go back home - it's ~3000km from where I am at temporarily.
> 
> Does anyone have experience with these MediaTek devices and B.A.T.M.A.N. on lower performance nodes like a Raspberry Pi...

It doesn't seem to me like this is batman-adv or batmand related. So I would 
most likely better to ask on linux-wireless@vger.kernel.org too

And is IBSS mode really required or would meshpoint with mesh_fwding set 0 
also work?

    iw phy0 interface add mesh0 type mp
    ip link set up dev mesh0
    iw dev mesh0 mesh join 11s-bat freq 2412 HT20 mcast-rate 18 beacon-interval 1000

    iw dev mesh0 set mesh_param mesh_fwding 0
    # please make sure that it is actually 0 with: iw dev mesh0 get mesh_param mesh_fwding

    ip link set master bat0 dev mesh0

> I have ascertained that NONE of the USB Realtek dongles work, as the kernel driver is missing IBSS support at this time...
> 
> I'm against an urgent deadline, and trying to understand what I can do to make this work

Kind regards,
	Sven

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

      reply	other threads:[~2021-06-11  6:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11  1:55 MediaTek MT7612u and IBSS mode Maurice Smulders
2021-06-11  6:48 ` Sven Eckelmann [this message]

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=4182303.XkkeXVZP1n@ripper \
    --to=sven@narfation.org \
    --cc=Maurice.Smulders@windtalker.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=linux-wireless@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox