[Battlemesh] Broadcast lost because of hidden station

Ben West ben at gowasabi.net
Thu May 8 16:08:39 UTC 2014


I'm curious if a recent changeset to OpenWRT trunk with Henning's name on
it is relevant this to thread about unreliable multicasts:
https://dev.openwrt.org/changeset/40696/trunk

If so, has it yielded a noticeable improvement?

On Tue, Apr 29, 2014 at 1:45 AM, Henning Rogge <hrogge at gmail.com> wrote:

> Hi,
>
> RTS/CTS is a good explanation... I remember seeing RTS packets, maybe
> the CTS wasn't visible in my trace because it was produced by the
> local station.
>
> Still its an annoying problem... routing agent drops route because of
> no multicasts but in theory unicast still works.
>
> Henning
>
> On Sat, Apr 26, 2014 at 2:56 PM, Paul Fuxjaeger <fuxjaeger at ftw.at> wrote:
> > On 26.04.14 12:07, Henning Rogge wrote:
> >> but I would expect that at least "one in five" broadcasts would make
> >> it through, because unicasts get up to 4 retransmissions.
> >
> > retransmission are sent in "fast" succession, maybe that helps to get
> > them received easier or maybe RTS/CTS is enabled?
> >
> > But if you don't see those non-retried frames EVER (multicast FER=1
> > while unicast FER<<1 while using the same channel code) this sounds like
> > the problem is located somewhere "higher".
> >
> >
> > _______________________________________________
> > Battlemesh mailing list
> > Battlemesh at ml.ninux.org
> > http://ml.ninux.org/mailman/listinfo/battlemesh
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh
>



-- 
Ben West
http://gowasabi.net
ben at gowasabi.net
314-246-9434
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20140508/69bcc70c/attachment.htm>


More information about the Battlemesh mailing list