On Wed, Aug 16, 2017 at 4:30 PM, Christian Pock wrote:
> Looks like Henning fixed an issue with the MPR handling of oonf/olsrd2.
> The most current commit v0.14.1-16-g8c625e9 seems to work fine right know.
>
> As soon as David updated the daemon on our "TranslationServer"/Gateway,
@lists.funkfeuer.at>
Betreff: Re: [Wien] ipv6 with olsrd2?
Just to mention it,
we found a major issue in the message generation code of Olsrd2 during the
Battlemesh in Vienna... which was the reason behind releasing 0.14.0...
I would suggest you update to a new version if you have something
On Tue, Aug 15, 2017 at 4:52 PM, Erich N. Pekarek wrote:
>> But the real solution should be to make sure Olsrd2 measures the link
>> cost right... so if there are good examples of links Olsrd2 classifies
>> "too good", a modification of the metric would be the right thing.
>
> I
Hello!
Am 2017-08-15 um 14:16 schrieb Henning Rogge:
On Tue, Aug 15, 2017 at 2:12 PM, Markus Kittenberger
wrote:
my 2 cents are that bridges without WDS already cause ipv4 problems and not
only issues with ipv6, so they should never have been used.
Unfortunately i
Am 2017-08-15 um 14:12 schrieb Markus Kittenberger:
my 2 cents are that bridges without WDS already cause ipv4 problems
and not only issues with ipv6, so they should never have been used.
Unfortunately i fear there are still quite a few of them in our network.
Definitely all firmware builds
On Tue, Aug 15, 2017 at 2:12 PM, Markus Kittenberger
wrote:
> my 2 cents are that bridges without WDS already cause ipv4 problems and not
> only issues with ipv6, so they should never have been used.
>
> Unfortunately i fear there are still quite a few of them in our
my 2 cents are that bridges without WDS already cause ipv4 problems and not
only issues with ipv6, so they should never have been used.
Unfortunately i fear there are still quite a few of them in our network.
lg Markus
On Tue, Aug 15, 2017 at 12:07 PM, Erich N. Pekarek wrote:
Hi!
Am 2017-08-15 um 11:43 schrieb Matthias Šubik:
let me have a guess ...
Let me guess a bit further...
On 11 Aug 2017, at 15:37, Gui Iribarren wrote:
On 11/08/17 13:43, Christian Pock wrote:
...
For some reason, not all routers running olsr2 are reachable via IPv6.
let me have a guess ...
> On 11 Aug 2017, at 15:37, Gui Iribarren wrote:
>
> On 11/08/17 13:43, Christian Pock wrote:
...
>>
>>
>> For some reason, not all routers running olsr2 are reachable via IPv6. As
>> far as we found out, this is related to the setting "WDS
Just to mention it,
we found a major issue in the message generation code of Olsrd2 during
the Battlemesh in Vienna... which was the reason behind releasing
0.14.0...
I would suggest you update to a new version if you have something like
0.13.x or before.
Henning Rogge
On Fri, Aug 11, 2017 at
Hi Gui,
you are right: IPv6 on olsr1 is no longer active on the majority of node that
supported it earlier this year (or last year). Anyway, as far as I know the
tunnel service "6in4" is still active, thus: as long as you are able to find a
path on IPv6@olsr1, you might be lucky to get online.
11 matches
Mail list logo