From: Bruno Randolf <br1@thinktube.com>
To: Richard Palethorpe <richard@lm-technologies.com>, ap420073@gmail.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: mesh support on rtl8192cu
Date: Fri, 03 Jul 2015 10:59:20 +0100 [thread overview]
Message-ID: <55965CF8.20208@thinktube.com> (raw)
In-Reply-To: <CAFSTUk6UasnV4P3B1TR7kSx1ToQTC+PC2hU6PynDBWJ3ALJzyg@mail.gmail.com>
On 07/03/2015 10:34 AM, Richard Palethorpe wrote:
> Hello Taehee,
>
> I have been experimenting with MESH mode on kernel 4.0.7. It is
> sending beacons out, but is unable to establish a connection.
>
> I have two rtl8192cu based dongles connected to identical VMs and am
> using the following commands to set up the mesh:
>
> iw dev wls160u2 set type mesh
> ip addr add 192.168.2.1/24 broadcast 192.168.2.255 dev wls160u2
> ip link set wls160u2 up
> iw dev wls160u2 mesh join lmmesh
>
> Running 'iw dev wls160u2 mpath dump' produces no results and there is
> nothing regarding mesh in dmesg. I can't find any other information on
> mesh with rtl8192cu other than the patch which you submitted.
>
> I am wondering if it does work, but there is a step I am missing or if
> something is wrong with the code?
I don't know about this 'mesh' mode, but I have noted problems in ad-hoc
mode with this chipset and driver. The problem seems to be that ARP
replies are not sent on the air... Not sure what the reason is or if
it's possible to fix it in the driver, but my conclusion for now is that
this device is unusable for ad-hoc mode. Similar problems may exist for
mesh?
bruno
next prev parent reply other threads:[~2015-07-03 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 9:34 mesh support on rtl8192cu Richard Palethorpe
2015-07-03 9:59 ` Bruno Randolf [this message]
2015-07-04 2:15 ` Taehee Yoo
2015-07-06 10:46 ` Richard Palethorpe
2015-07-06 19:04 ` Bruno Randolf
2015-07-07 11:09 ` Richard Palethorpe
[not found] ` <CAMArcTVS5SaE605vf1yQgpUbXVaaoDS2Qcn1KJJnMVbrjbWkKg@mail.gmail.com>
2015-07-08 7:20 ` Taehee Yoo
2015-07-08 11:48 ` Richard Palethorpe
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=55965CF8.20208@thinktube.com \
--to=br1@thinktube.com \
--cc=ap420073@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=richard@lm-technologies.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 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).