[Olsr-dev] [PATCH 2/4] smart gateway: do not stop choosing a new (better) gateway
Teco Boot
(spam-protected)
Thu Dec 8 17:34:30 CET 2011
The reason for the patch was a lost tunnel and not setting up a
new one. I don't think the patch replaces an existing tunnel.
For testing purposes, an informational syslog message is needed
each time a tunnel is set up or removed. Problems with this?
Let's go for a threshold parameter, e.g. SmartGatewayThreshold.
Default can be hard coded for now, set to 0.0.
We have to define some metric calculation, with ETX & uplink &
downlink. Then, outcome can be compared. Ideas?
Teco
Op 8 dec. 2011, om 14:42 heeft Henning Rogge het volgende geschreven:
> On 12/08/2011 02:39 PM, Ferry Huberts wrote:
>> So I think we then agree that a solution with hysteresis is acceptable?
>>
>> Then as a first step, is merging the patch as it is now also acceptable?
> Maybe you can add a compiler condition to (de)activate the repeating gateway search.
>
> #ifndef KEEP_LOOKING_FOR_GATEWAY
> ...
> #endif
>
> Henning
>
> --
> 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
>
> --
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev
More information about the Olsr-dev
mailing list