[Battlemesh] Limit minimum bitrate

[Ben West]

Also, to clarify, my AP virtual interfaces are bridged, so they would
appear as "br-ap1" , "br-arp2" to the hotplug script I quoted.

On Fri, Sep 12, 2014 at 12:33 PM, Ben West <ben at gowasabi.net> wrote:

> On 2.4GHz meshes I operate, where each node broadcasts an IBSS SSID plus
> one or two AP SSID's, this is what I do to bar very low bitrates on the AP
> SSID's.
>
> /etc/hotplug.d/90-ratemask-firewall:
>
> #!/bin/sh
>
>
> . /lib/functions.sh
>
> . /lib/functions/network.sh
>
>
> # Don't set rates on mesh interface
>
> meshif=$(uci -P /var/state get network.mesh.ifname)
>
>
> # Disable low legacy 2.4GHz bitrates
>
> if [ add = "$ACTION" -a wlan0 != "$meshif" ]; then
>
> case "$DEVICE" in
>
> br-*)
>
> #Bridged interfage, check for wlan0 as member
>
> for i in $(ls /sys/class/net/$DEVICE/brif); do
>
> case "$i" in
>
> wlan0)
>
> logger setting bitrate for device "$i" on interface "$INTERFACE"
>
> iw "$i" set bitrates legacy-2.4 5.5 6 9 11 12 18 24 36 48 54
>
> ;;
>
> esac
>
> done
>
> ;;
>
> esac
>
> fi
>
> #
>
> I don't limit bitrates on the IBSS interface (named "mesh"), since I would
> want the nodes to stay on the adhoc net in event of extreme interference
> (i.e. so that they remain controllable).
>
>
>
> On Fri, Sep 12, 2014 at 12:19 PM, Mitar <mitar at tnode.com> wrote:
>
>> Hi!
>>
>> I had in mind AP mode, for clients. But interesting to learn about IBSS
>> join as well.
>>
>> But I really think it is useful to be limit the minimum bitrate. It is
>> strange for me that is not easily available. Am I missing something? Is
>> it not a good idea?
>>
>>
>> Mitar
>>
>> > Mitar, you may want to check the basic-rates argument of the ibss join
>> > command. (assuming we are talking about ibss mode):
>> >
>> > from the output of "iw dev wlan0 ibss join":
>> >
>> > [basic-rates <rate in Mbps,rate2,...>]
>> >
>> > all the stations must have the same basic rates to join the ibss cell.
>> > Rates that are not part of the basic-rate set should not be used by the
>> > stations.
>> >
>> > Cheers,
>> >
>> > On 12/09/14 14:52, Pau wrote:
>> >> Not sure if it solves your question, but just in case it helps you
>> somehow.
>> >> In a mesh network you can use the mcast_rate option to set the
>> multicast rate of the WiFi devices. So if the routing protocol is using
>> multicast flooding to discover neighbors, it will only discover those who
>> are available at this specific rate.
>> >>
>> >> Cheers.
>> >>
>> >> On 12/09/14 14:00, Bastian Bittorf wrote:
>> >>> * Mitar <mitar at tnode.com> [12.09.2014 08:56]:
>> >>>> This seems to fix the bitrate to a fixed one, not setting the
>> minimum one.
>> >>>
>> >>> as far as i understand, you can set a "allowed rateset" with 'iw',
>> which
>> >>> should fit your needs...
>> >>>
>> >>> bye, bastian
>> >>> _______________________________________________
>> >>> 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
>> >
>>
>> --
>> http://mitar.tnode.com/
>> https://twitter.com/mitar_m
>> _______________________________________________
>> 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
>



-- 
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/20140912/e117117f/attachment-0001.htm>