From: Jorge Baranda <jbaranda@cttc.es>
To: ath10k@lists.infradead.org
Subject: Re: Sending lldp packets with ath10k in ADHOC mode
Date: Fri, 25 Sep 2015 10:03:14 +0200 [thread overview]
Message-ID: <5604FFC2.8020405@cttc.es> (raw)
In-Reply-To: <5602C17A.6070509@cttc.es>
[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]
Dear all,
I upload a wireshark capture to illustrate the behavior previously
described. This wireshark is showing the traffic in the "master" computer.
It is suppossed that both interfaces should be sending periodicall LLDP
packets (with broadcast mac dst addr), but only the one configured in AP
mode is sending such packets.
However, when I try to look for a host through the interface configure
in ad-hoc, the ARP process starts with the broadcast ARP request and
this message is sent (and registered bywireshark) through the interface
configure in ad-hoc. Does the ath10k driver has to do something with
the different treatment of the broadcast packets/protocols?
Aparently, all broadcast packets should be sent by the wireless
interface no matter its configuration (AP or ad-hoc), isn't it?
Thanks in advance,
Jorge
El 23/09/15 17:12, Jorge Baranda escribió:
> Dear all,
>
> I have a setup which consists of three computers connected by means of
> WLE900VX cards using the ath10k driver.
> One computer (which we can call master) is equipped with two of these
> cards and I set different modes to connect the "master" with the other
> computers.
> In particular, a pair of computers (master-computer A) is connected in
> ad-hoc mode and the other pair (master-computer B) is connected in
> AP-STA mode.
>
> I want to send LLDP packets through both interfaces of master computer
> to perform link discovery. But I have realised that sending LLDP
> messages is only possible through the
> interface configured as AP. Nevertheless, I've seen that the ad-hoc
> interface is able to send ARP broadcast messages.
> Due to this fact, when generating the LLDP packets I set as
> destination MAC address the broadcast one, but even so, the ad-hoc
> interface is not sending the LLDP messages.
> Does anyone have an idea of the reason of this behavior? Which is
> treating differently the ARP and the LLDP packet?
> I was expecting the ad-hoc interface to forward any kind of packet
> with mac destination address the broadcast address.
>
> Thank you very much in advance for your time and attention,
>
> With kind regards,
>
--
Jorge Baranda
Research Engineer, MSc
jorge.baranda@cttc.es
Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
Av. Carl Friedrich Gauss, 7
08860 Castelldefels, Barcelona (Spain)
Tel: +34 93 645 29 00 Ext: 2171
Fax. +34 93 645 29 01
www.cttc.es
[-- Attachment #2: arp_lldp_packets.pcapng --]
[-- Type: application/octet-stream, Size: 3136 bytes --]
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2015-09-25 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 15:12 Sending lldp packets with ath10k in ADHOC mode Jorge Baranda
2015-09-25 8:03 ` Jorge Baranda [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=5604FFC2.8020405@cttc.es \
--to=jbaranda@cttc.es \
--cc=ath10k@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.