[Olsr-dev] gateway code
Tue Jul 24 14:13:26 CEST 2012
On 24-07-12 13:56, Teco Boot wrote:
> Op 24 jul. 2012, om 13:26 heeft Henning Rogge het volgende
>> On 07/24/2012 01:24 PM, Ferry Huberts wrote:
>>> On 24-07-12 13:22, Henning Rogge wrote:
>>>> On 07/24/2012 01:15 PM, Teco Boot wrote:
>>>>> Manual interference with unmanaged tunnels is a request for
>>>>> trouble. If there is a side effect on tunnel_down (e.g.
>>>>> removed routes), that is how it is designed. Let's have a
>>>>> clean smart-gw.
>>>> At the moment there would be no way to restore the route for
>>>> the tunnel. That is why the mechanism was inside.
>>>> Similar for mesh interfaces, if they go up again, OLSRd must
>>>> restore the routes.
>>> So I think I'm going to revert my changes to that code. Agree?
>> I am not sure if it is really needed, but I dislike the idea that a
>> single if-down wrecks your tunnel to the gateway (and most likely
>> your internet connection with it!).
> If tunnel goes down, the multi-hop route to nearest gw is taken.
> Could be same gw, then nothing breaks. If another gw is taken, we are
> back to nat_threshold or plain gw routing.
> When we have multiple tunnels & conntrack & route policies, we can do
> much better than sticking on far_away gw that was selected long time
> ago. I do not prefer enhancing smart_gw with unneeded bypasses for
> cornercases. Just me.
> I'll discuss with Ferry what to do.
We discussed it and we're not reverting the commits.
So we're keeping it the way it is.
If someone is messing about with a tunnel that is under control of olsrd
then he should expect that olsrd can end up 'confused' and without a
working gw ;-)
>> What do you think?
>> 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
>> http://www.fkie.fraunhofer.de GPG: E1C6 0914 490B 3909 D944 F80D
>> 4487 C67C 55EC CFE0
More information about the Olsr-dev