[Olsr-users] OLSRD routing table problem.

[Henning Rogge]

On Tue, 04 Oct 2011 14:36:38 Henning Rogge wrote:
> On Tue, 04 Oct 2011 14:24:34 Philip Hugg wrote:
> > > Switch on ETX, the non-ETX case might be broken (nobody ever has used
> > > it in years).
> > > 
> > > Henning Rogge
> > 
> > Hello Henning,
> > 
> >  From what I understand about ETX.
> > 
> > If I turn it on, then OLSRD is not actually compliant with the RFC.
> > Is this true?
> 
> Yes.
> 
> The pure RFC 3626 compatible implementation would be not very useful in
> wireless environments, except for networks that only have point to point
> links.
> 
> Thats the reason why the latest draft of OLSRv2 of the IETF directly
> contains a standardized way to implement routing metrics.

You could try to use the Development/Master branch code, the non-etx code 
there might work (because its handled with the same codebase as the ETX code).

Still, it would not work well in wireless networks.

Henning Rogge
-- 
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Neuenahrer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961,   Fax +49 228 9435 685
mailto:(spam-protected) http://www.fkie.fraunhofer.de
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4364 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20111004/0dc5e4df/attachment.bin>