[Olsr-users] [Olsr-dev] Fwd: Re: Is there a way to pick a specific OLSR gateway with smart gateway?

[Henning Rogge]

Hi,

I think the original idea was that you could implement your own "gateway
handler" as a plugin, similar to the default one
"src/gateway_default_handler.c".

Not sure if this would work anymore, the codebase has changed a lot since
then.

Ferry, how much is the "gateway handler" still used?

Henning

On Mon, May 9, 2016 at 8:47 PM, Ferry Huberts <(spam-protected)> wrote:

>
>
>
> -------- Forwarded Message --------
> Subject: Re: Is there a way to pick a specific OLSR gateway with smart
> gateway?
> Date: Mon, 2 May 2016 23:20:43 +0100
> From: Ferry Huberts <(spam-protected)> <(spam-protected)>
> Organisation: Pelagic
> To: elektra <(spam-protected)> <(spam-protected)>
>
> It would not be too difficult to hook into the current selection algorithm
> with a new plugin (or core extension) that forces a certain gateway.
> Maybe something that does whitelisting or blacklisting of a list of
> gateways.
> It is not my itch to scratch though so I will not work on it. However, I
> can offer to mentor someone.
>
>
> And for the record: I inherited all this stuff...
> I only adjusted / extended olsrd with stuff we need.
>
>
> F.
>
>
> On 02/05/16 22:40, elektra wrote:
>
> Hi Ferry –
>
> thank you for your answer.
>
>
> Something could be made for this but ofcourse it would be better to fix
> the misbehaving gateway node.
>
> I see. I don't want to complain at all, but let me share some personal thoughts, if you don't mind.
>
> There might be multiple reasons to pick a gateway. For example, one might not trust the gateway (owner) that pretends to offer amazing bandwidth while we have a good routing metric to the destination. It might be someone aggregating traffic for malicious purposes.
>
> Our setups are also getting more and more complex and so does the software. Accidental or transient black holes for internet traffic do sometimes occur and we usually solve them on a social level. But for the time while the problem occurs and the social solution takes time to progress, we are stuck without uplink connection in the area affected by the black hole.
>
> I am trying to run live radio shows via the mesh and I need to feed an official FM transmitter to cover Berlin via antenna.
>
> Sure we can dream of a bug-free world, but in case someting goes south at the gateway end (it might actually be the ISP of the gateway operator having problems) I want to be able to pick the gateway as a client. Where is the point of a gateway selection mechanism, if the gateway can not be selected manually? I personaly hate automatisms that are trying to outsmart me.
>
> Here is the relevant section in the manual of the old batmand:
>
>  -p preferred gateway
>               Set the internet gateway by yourself. Note: This automatically switches your daemon to
>               "internet search modus" with "-r 1" unless "-r" is given. If the preferred gateway  is
>               not  found  the gateway selection will use the current routing class to choose a gate‐
>               way.
>
> Many years ago, when the CCC congress was still held in Berlin, I asked Henning to add the gateway selection feature of batmand to OLSR. We had the problem of gateway flapping with NAT ever since 2003, when we had started to use OLSR. Hence, a gateway selection mechanism was high on the feature list of batmand. I didn't succeed to convince the Berlin crowd to migrate the entire network to batmand, though, as OLSR was already well known and people were used to it. So I asked Henning to add the gateway selection functionality of batmand into OLSR to fix the issue for OLSR networks. I have now learned from you that the feature has never been fully implemented. Too bad. At least gateway flapping is not a problem anymore, since we are using OpenVPN as a workaround for legal reasons.
>
> Most Freifunk communities that started in the last years are using batman-adv now.
>
> Cheers,
> Elektra
>
>
>
>
>
>
>
> --
> Ferry Huberts
>
>
> --
> Ferry Huberts
>
>
> --
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20160510/2a7d52a6/attachment-0001.html>