[Olsr-dev] [PATCH v1 0/3] Use bandwidth during gateway selection
Fri Jul 27 13:21:41 CEST 2012
I use SmartGW. I need this new function.
Maybe the ETX factor can be altered, so high means more important.
With default settings: no change in operation at all (maybe update
config file to reflect defaults also).
After this change, I can start removing my double /1 and quadruple
/2 default routes. This needs more changes, in my ppp and dhcp
configs (adding default route in routing tables lower than SmartGW).
And mechanism to update SmartGW uplink and downlink, e.g. GPRS/UMTS/HSPA
for ppp and satcom/DSL/cable for dhcp. And the mechanism to manage
the best exit link, which can be a local link or an exit link of
another node. So nodes with low rate GPRS can make use of a nearby fat
pipe, HSPA or DSL.
If this is arranged, the next step is having multiple tunnels and the
conntrack / policy routing trick. This enables usage of best exit link
for new connections, where these connections will keep using this exit
link during their lifetime.
These are the basics for multi-path...
I also want to see comments. Maybe also:
- not interest in SmartGW at all
- interested, but not tried yet
Op 27 jul. 2012, om 12:50 heeft Henning Rogge het volgende geschreven:
> I would like to hear some comments about this from someone who has USED the SmartGW system.
> *looking around on the mailing list*
> On 07/26/2012 04:23 PM, Ferry Huberts wrote:
>> From: Ferry Huberts <(spam-protected)>
>> (this series applies on top of my previous gateway patch series)
>> Hi guys,
>> While reviewing the gateway code, I encountered something that works
>> differently than Teco and I expected so we would like to change it.
>> The problem: the current gateway selection code doesn't take the
>> advertised uplink/downlink speeds into account, it only looks at the tc
>> path cost (sum of ETX-link costs).
>> The result of the current code is that the 'nearest' gateway is
>> selected. We would like to change that to 'nearest fat pipe'.
>> 'nearest fat pipe' is a bit fuzzy so we would like to propose the
>> - We calculate a new path cost of
>> new_path_cost = (1 / (uplink + downlink)) + (tc_path_cost / 4)
>> (uplink and downlink in Mbps)
>> (the 1 and 4 are weighing factors and we can make then configurable)
>> - Gateway selection is done based on new_path_cost
>> PS. in this we assume that tc_path_cost=1 signifies that the WLAN speed is
>> reasonably good, say 4Mbps (but if that's different then we can tune it
>> with the weighing factors)
>> Ferry Huberts (3):
>> gateway: also take gateway bandwidth into account...
>> cfg: add SmartGatewayWeightExitLink and SmartGatewayWeightEtx
>> pud: add SmartGatewayWeightExitLink and SmartGatewayWeightEtx
>> README-Olsr-Extensions | 18 ++++++++
>> files/olsrd.conf.default.full | 12 +++++
>> files/olsrd.conf.default.lq | 12 +++++
>> files/olsrd.conf.default.lq-fisheye | 12 +++++
>> lib/pud/doc/olsrd.conf.default.pud | 12 +++++
>> src/cfgparser/cfgfile_gen.c | 18 ++++++++
>> src/cfgparser/olsrd_conf.c | 4 ++
>> src/cfgparser/oparse.y | 20 +++++++++
>> src/cfgparser/oscan.lex | 10 +++++
>> src/gateway_default_handler.c | 88 ++++++++++++++++++++++++++++++++++---
>> src/olsr_cfg.h | 4 ++
>> 11 files changed, 203 insertions(+), 7 deletions(-)
> 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
More information about the Olsr-dev