Project

General

Profile

Actions

Feature #205

closed

fallback uplink mode

Added by Pascal Garber about 9 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
03/08/2015
Due date:
% Done:

0%

Estimated time:

Description

The gluon team thinks my idea is better placed in batman-adv.
You can find the original issue and discussion on https://github.com/freifunk-gluon/gluon/issues/230

In my idea batman-adv has an optional fallback uplink mode.
In this mode, the uplink would only be activated / used if no other node (which is meshing with our current note) has an activated uplink.
This would have the advantage that slow uplinks could only be used if no other (faster) uplink is in the near.

For example: I've two Internet connections, one over "Kabel Deutschland" with 100 Mbit/s and one over "T-Online" with 2Mbit/s. My Freifunk router's are using "Kabel Deutschland" for his uplink because it's much faster than "T-Online", but sometimes "Kabel Deutschland" has a fault and is not working anymore. In this situation it would be very useful, if my other Freifunk router (whose config is pre-configured for "T-Online") would activate his uplink as long as my Freifunk router (that is configured for "Kabel Deutschland") has no uplink.

I think this scenario is often, for example if your neighbor has an much slower connection as yours, normally your neighbor use the uplink of your faster uplink and his Freifunk router has an deactivated uplink, but what if the mash is interrupted? Then your neighbor would have no more uplink, with an backup uplink mode his Freifunk router could use his own uplink as long as the mash is interrupted.

I think this feature should not be so difficult to implement, in my imagination batman-adv would have a further checkbox in his config mode webinterface for this backup uplink mode, when this mode is activated, then a script runs every few minutes and test the own internet connection / uplink (In this case, it is not relevant from which node the uplink is), if no internet connection / uplink is found, the script activates the uplink in /etc/config/fastd. If the backup uplink is activated, the scripts checks the uplink status of his neighbor nodes, if one of the neighbors has an uplink (that comes not from his own), the script deactivates his own.

What necessary to clarify is, is how the node knows, that the uplink of the neighbor nodes are not comes from his own uplink. Could this information be stored in alfred?

What do you think of my idea?

Cheers,
Pascal

Actions #1

Updated by Marek Lindner about 9 years ago

Why not simply have both gateways announce their uplink but advertise different uplink speeds ? One 100mbit/s connection and one 2Mbit/s connection (see https://downloads.open-mesh.org/batman/manpages/batctl.8.html -> gw_mode).

When the fast uplink goes down the affected node should stop advertising the uplink to make everybody switch to the slower link.

Nodes with a weak connection to the fast uplink can always select the slow link depending on their gw selection class settings.

Actions #2

Updated by Pascal Garber about 9 years ago

Would this also work if the fast uplink node is an indirect node (e.g. 3 nodes away but connected / meshed) and the slow uplink node is the first node the client node is connected with?
In this case, would the client node get the fast uplink speed nevertheless?

Actions #3

Updated by Marek Lindner about 9 years ago

I do believe the document I gave you the link to does answer your question.

Actions #4

Updated by Marek Lindner almost 9 years ago

Any update ?

Actions #5

Updated by Marek Lindner almost 9 years ago

  • Status changed from New to Closed

Closed due to inactivity. Feel free to re-open if the issue persists.

Actions #6

Updated by Sven Eckelmann about 7 years ago

  • Status changed from Closed to Rejected
Actions

Also available in: Atom PDF