On Thu, Jun 8, 2017 at 11:50 PM, Juliusz Chroboczek wrote:
> For anyone interested, the Z3 algorithm is named in honour of Benjamin,
> the author of the mail I'm replying to.
>
>> Beware also that babel does not support all "recent" channel configurations:
>
>>
For anyone interested, the Z3 algorithm is named in honour of Benjamin,
the author of the mail I'm replying to.
> Beware also that babel does not support all "recent" channel configurations:
> https://wiki.freifunk.net/ideas
That's not quite true.
> In the absence of explicit diversity routing
> R1(AP mode) ---> R2( Station mode)
All of your routes are single-hop, so there's no diversity information
being propagated. You'll need some longer routes in order to see anything..
> The channel information remains as 11 and 36 for station mode but ap
> mode it is 255. Whether it is
Hi Juliusz,
Thanks for your support.
I'm using the following topology to understand the diversity behaviour,
R1(AP mode) ---> R2( Station mode)
Both R1,R2 having two radio's 2.4 and 5 Ghz.I'm getting following result for
with diversity and without diversity. It seems only change i can
Hi all,
Please anyone help me in this.
ThanksBalaji
On Monday, 29 May 2017 8:17 PM, Balaji .J wrote:
Hi Juliusz chroboczek,
Thanks for your help, as i'm using uci configuration i tried by adding
diversity '0' and diversity_factor '128' in /etc/config/babeld
> Unable to find the channel information.
Send the SIGUSR1 signal to babeld (killall -USR1 babeld), then check the
log (using logread if a recent version of LEDE/OpenWRT, in /var/log/babeld.log
if using an older version).
-- Juliusz
___
Babel-users
6 matches
Mail list logo