On Dienstag, 4. September 2018 17:07:34 CEST Ligang LIU wrote: [...]
I captured frames with tcpdump and found somethings.
[..]
The pcap files are attached in this email. I'm not sure whether it's proper to send them to the mailinglist, so I don't cc this email to the mailinglist.
The mails would have been held back and I might not have accepted them due to the size of the attachments. So you did everything right.
I have now added the mailing list again to the Cc
First, there are many ELP unicast packets.
Second, there are many RTS/CTS/ACK. When a node wants to send ELP unicast packets to a weak neighbor, this will happen frequently. While in batman-adv 4, there is only a very small amount of RTS/CTS frames.
Ack
Third, change elp interval from 500 to 1000 will decrease ELP unicast packets but it does not decrease RTS/CTS too much.
Shouldn't the number of probes be reduced and thus also the RTS? It is something which the wifi layer handles - not batman-adv.
And the duration of the RTS frames seem to be rather high (I don't say that these are wrong) when I've looked through the dump via
(wlan.fc.type_subtype == 0x001b) || ((llc.type == 0x4305) && (data.data[0] == 03))
Maybe someone can check whether they make sense or not (don't have the time right now to do it).
Although Antonio explained in the previous email, "... if you have no data over the link, sending 2 probes of 200bytes each every 500ms (default ELP interval) won't really eat much airtime, unless you have a lot of idling 1-hop neighbours", I think the ELP probe packets will occupy much wifi airtime, because wlan is working on the SHARED media. The transmission of ELP probe packets between idle 1-hop neighbours can be heard by the other nodes and their transmission have to be delayed. Consequently, the performance, delay and throughput, could be lowered down, compared to batman-adv 4.
@Antonio, you must also keep in mind that the RTS + CTS frames are transmitted at the lowest available rate (1Mbit/s in this case). The Ack is done with 6Mbit/s in his dump. The broadcast is done with 18Mbit/s. The unicast stuff seems to be send with MCS rates.
The RTS+CTS will therefore use an amazing high number of airtime (but I didn't do the calculations). Attached are some estimates using Dave Taht's airtime- pie-chart fork [1] + a modification to show the transmitter and not the destination host. And these numbers are the raw ones - not normalized in any way (so not directly comparable). Don't forget that these also don't take the duration field of the RTS into account.
[...]
And, my wireshrk (windows, v2.6.3) can not analize the batman-adv 5 packet. I find a wireshark code for batman-adv: https://github.com/wireshark/wireshark/blob/master/epan/dissectors/packet-ba... Is it for batman-adv 4 only? Do you know any plugin to do this?
It only support B.A.T.M.A.N. IV frames of different version. Feel free to submit the ELP and OGM2 support to wireshark (this is not necessarily directed to Ligang but to everyone).
Kind regards, Sven