On Mon, May 17, 2010 at 09:30:10AM -0500, Don Weeks wrote:
> Also, I am thinking of ripping out the config/babeld and going with
> standard babeld.config because I find the syntax confusing from
> straight babel.
I definitely agree with you, but such a syntax is a necessary evil to
plug babel into
I think we have found it to be a bad radio. At least, in one case, for sure
it is a radio that was only sending but had quit receiving. So, it works for
my friend in his daisy chain scenario and should work for me. I suspect I
have a bad radio as well. Both of us are using the same brand and type o
Once again, are you able to ping the link-local addresses of one node
from the other? If you aren't, then it's not a Babel issue, and you
need to fix your lower layers before you try any routing protocol.
Juliusz
___
Sorry for the previous 2 mails. I swear I am hitting reply all but must be
missing it.
Don
On Sun, May 16, 2010 at 12:12 PM, Juliusz Chroboczek <
juliusz.chroboc...@pps.jussieu.fr> wrote:
- Show quoted text -
It seems more that the one system is sending only and the other side is
receiving.
> Cell IDs show to be the same and I see what appears to be babel
> packets going between the 5.8G radios
Do you only see sent Babel packets, or do you see received Babel
packets? (Look at the source address in your dumps.)
Are you able to ping the link-local IPv6 addresses of your neighbouring
I am using multiple radios in my Open-WRT system. 1 is at 2.4G the other is
at 5.8G. Another system has the same radios and a third has only 5.8G. What
I see is that 2.4G radios connect together but the 5.8G radio does not
associate with the 5.8G radio in the 3rd system. Cell IDs show to be the
sam
6 matches
Mail list logo
