[Olsr-dev] [PATCH v1 0/3] Use bandwidth during gateway selection

[Ferry Huberts]

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
following:

- 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(-)

-- 
1.7.11.2