public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: johnzeng <johnzeng2013@yahoo.com>
To: Sven Eckelmann <sven@narfation.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: Whether Batman-adv need suitable wifi network card (support interface modes ( mesh point ) ) .
Date: Wed, 26 Oct 2016 20:52:13 +0800	[thread overview]
Message-ID: <5810A6FD.9080308@yahoo.com> (raw)
In-Reply-To: <1499092.KaxnJhUj78@bentobox>


Dear Sven :

                     Thanks , and i will try to purchase suitable wifi 
hardware ,

                      Because i use raspberry 
<http://www.baidu.com/link?url=s_ofbUc1ZEO-1ohz5A3WnLdqY4CNZ948d7JxBMkwZtW_fjTcOKUwMjkloBUHVW475SCTMxAci7HoEvHeH80Fuz9lC1X4W6Hw4BvwQaUIDzq> 
pi  , i have to use wifi card based usb .

                      whether you can advise a set of usb wifi card 
based Atheros ( driver ath9k) ?



                       Best Regards

                       Tiger



> On Mittwoch, 26. Oktober 2016 15:19:02 CEST johnzeng wrote:
> [...]
>> HostB wlan0 : mac addr : ether 00:1d:43:10:15:44
>>
>> HostA wlan0 : mac addr: ether c8:3a:35:c9:ce:71
> [...]
>> i run the command at Host A ( Rt2070 ) at ( ping HostA from HostB)
>> iw dev wlan0 station dump:
>> Station 00:1d:43:10:15:44 (on wlan0)
> [...]
>
> Here we see that host A noticed that there is a different device and
> "connected" to it (actually, it just added it as remote station to its
> internal list).
>
> This is a good sign - at least when both devices have each other in
> their respective station lists (*spoiler* they don't).
>
>> [root@alarmpi ~]# tcpdump -i bat0
>>
>> 07:01:40.635517 ARP, Reply 0.0.0.0 is-at 43:05:43:05:00:00 (oui
>> Unknown), length 28
>> 07:01:50.655521 ARP, Reply 0.0.0.0 is-at 43:05:43:05:00:00 (oui
>> Unknown), length 28
>>
>> [root@alarmpi ~]# tcpdump -i wlan0
>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>> listening on wlan0, link-type EN10MB (Ethernet), capture size 262144 bytes
>> 07:02:35.815528 c8:3a:35:c9:ce:71 (oui Unknown) > Broadcast, ethertype
>> Unknown (0x4305), length 66:
> [...]
>
> Here we see an OGM that is transmitted from this device. So for some reason
> we don't see the an incoming OGM from host B. Either host B is not really
> transmitting it, host A is not receiving it or you just didn't capture long
> enough.
>
> [...]
>> and i run same command at Host B ( RTL8188CUS ) at ( ping HostB from HostA)
>>
>> iw dev wlan0 station dump:
>>
>> " is blank"
> This means that RTL8188CUS didn't detect a remote IBSS device. This is odd and
> at first glance looks to me like a bug in the RTL8188CUS driver. But I would
> recommend to get a third (known to work) device and check to which of the
> orignal two devices it can connect and which of the other two devices can
> connect to it.
>
> You could even use the third device to capture raw wifi frames on a monitor
> interface and check if both devices submit these OGMs and if both devices
> are beaconing (and reply to probe requests).
>
> But this is basically the main problem here.
> The rest of the reply is just to explain some additional things.
> ---------------------------------------------------------------
>
> [...]
>> tcpdump -i wlan0
>>
>> 06:57:11.425351 c8:3a:35:c9:ce:71 (oui Unknown) > Broadcast, ethertype
> [...]
>> 06:57:11.534759 00:1d:43:10:15:44 (oui Unknown) > Broadcast, ethertype
> [...]
>
> This part shows an OGM from host A and host B. So it can receive OGMs from
> other stations and batman-adv is at least trying to send some data. It is
> unknown here if the host B is not really sending it or if host A is not
> really receiving it.
>
> [...]
>> And i thought Rt2070 support Broadcast and RTL8188CUS don't support
>> Broadcast or send ...
>>
>> because when i ping ip (RTL8188CUS) from Rt2070 , and i can see ping
>> packet via (tcpdump -i bat0 ) and i can see Rt2070 mac addr via (tcpdump
>> -i wlan0 ) at HOSTB,
>>
>> but i ping ip (Rt2070) from RTL8188CUS and i can't see any ping packet
>> from RTL8188CUS and i can't see RTL8188CUS mac via (tcpdump -i wlan0 )
>> at HOSTA
> Both should have working broadcast to get the ARP stuff working for the ping.
> But of course this only a good test when each ping tests are done with clean
> ARP tables (Linux is sniffing packets to fill its own ARP table without always
> sending ARP request). There is a test which you could have done even without
> the `iw dev wlan0 station dump` info from above.
>
> This part now is without batman-adv (because the text from you is quite unclear):
> --------------------------------------------------------------------------------
>
> But it could be that the ARP table on RTL8188CUS (Host B) was filled by the
> ARP request from Host A. And this was to only reason why the ping back from
> host B to host A worked.  You can test that by making sure that the ARP table
> is clean on both hosts and then start pinging from B to A. Also make some
> captures with tcpdump on both hosts that you later can analyze with wireshark.
> After your test (when it worked) make sure that the arp table on both hosts
> contain entries for each other. And than analyze the dumps for ARP packets in
> wireshark to make sure that host B really submitted and request and host A
> replied to it.
>
> Kind regards,
> 	Sven


  reply	other threads:[~2016-10-26 12:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25  9:25 Whether Batman-adv need suitable wifi network card (support interface modes ( mesh point ) ) johnzeng
2016-10-25  9:45 ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-10-25 23:19   ` johnzeng
     [not found]     ` <580FFD64.7020704@yahoo.com>
2016-10-26  6:07       ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-10-26  7:19         ` johnzeng
2016-10-26  8:17           ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-10-26 12:52             ` johnzeng [this message]
2016-10-26 13:05               ` Sven Eckelmann
2016-10-26 13:42                 ` johnzeng
2016-10-26 14:58                 ` Martin Hundebøll
     [not found]             ` <mailman.170.1477486357.610.b.a.t.m.a.n@lists.open-mesh.org>
2016-10-26 15:09               ` [B.A.T.M.A.N.] " Simon Wunderlich
2016-10-26  7:00     ` Sven Eckelmann

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=5810A6FD.9080308@yahoo.com \
    --to=johnzeng2013@yahoo.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=sven@narfation.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