From: Alexis Green <agreen@cococorp.com>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: Jason Scatena <jscatena88@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Issues with mesh networking path detection
Date: Thu, 21 May 2015 10:32:48 -0700 [thread overview]
Message-ID: <CAAnMG+Maom0VOkj0YgQp_u-z8+YM7YUr7uOjZTPHAf_kpjC_Rw@mail.gmail.com> (raw)
In-Reply-To: <555E14D1.30008@rempel-privat.de>
Keep in mind that mpath table is going to empty unless you try to
reach another node. Assuming your routing is correct, pinging from one
node to another should initiate ARP request, which will cause path
requests to go out and, ultimately, add entries to mpath table. I
didn't see any mention of attempting to send data packets across the
mesh, so that might be the only problem.
On Thu, May 21, 2015 at 10:24 AM, Oleksij Rempel <linux@rempel-privat.de> wrote:
> Am 21.05.2015 um 19:11 schrieb Jason Scatena:
>> Hello all,
>>
>> I am attempting to set up a mesh network between 4 computers with
>> Atheros 9271 based usb wifi dongles using the ath9k driver.
>>
>> I followed the guide at: https://github.com/o11s/open80211s/wiki/HOWTO
>>
>> to set up the network.
>>
>> When I get all of the computers up and configured they all see each other.
>> The command "iw dev mesh station dump" shows all the nodes in the
>> area. However the path selection doesn't seem to work at all. For
>> instance the command "iw dev mesh mpath dump" returns nothing. However
>> if I manually add arp entries using the arp command they show up in
>> the mpath dump.
>>
>> I am willing to do whatever to troubleshoot however there is very
>> little documentation that I have been able to find on trouble shooting
>> these issues. I would also be able to provide a pcap file of the nodes
>> coming online.
>>
>> I'm new to the wireless world but have C coding experience and would
>> be willing to put in the time to learn.
>
>
> Hi,
>
> i don't think there are people who will know the answer without research
> and reading the code.
>
> Since you are willing to learn any way, fallow the codepath and find out
> what is happening. We would be happy to have more wifi experts :)
>
> Find out what executed in kernel if you start this command: "iw dev mesh
> mpath dump". I assume it is starting somewhere in linux/net/wireless/mesh.c
>
> Use printk() placed in code or use gdb+openocd+jtag if you use some arm
> or mips system.
>
>
>> Best,
>> Jason Scatena
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
> --
> Regards,
> Oleksij
>
prev parent reply other threads:[~2015-05-21 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 17:11 Issues with mesh networking path detection Jason Scatena
2015-05-21 17:24 ` Oleksij Rempel
2015-05-21 17:32 ` Alexis Green [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=CAAnMG+Maom0VOkj0YgQp_u-z8+YM7YUr7uOjZTPHAf_kpjC_Rw@mail.gmail.com \
--to=agreen@cococorp.com \
--cc=jscatena88@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
/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).