public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] dynamic gateway / hna / services
Date: Fri, 27 Jul 2007 16:07:24 +0200	[thread overview]
Message-ID: <200707271607.24544.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20070724152109.yhywdc2kj6skcgck@webmail.ddmesh.de>


Hi,


this question was a bit forgotten.  :-)

> how does batmand detect whether the internet connection is really connected
> to the internet or not. Or does batmand just relays on the -g parameter.
> Until now we let run a cron job that checks for the real working
> gateway. Because we can not relay on the presence of the default
> route. User may use a different
> router to connect to the internet and just add the default route this
> private router.
> The problem is that the node offering a internet connection (-g)
> should also be able to access other internet connection if its local
> connection is brocken.

First of all, "-g" is just flooded through the network. We also want some kind 
of "dyngw"-plugin but with a better approach: By using tunnels to the gateway 
batman is in a far better situation than OLSR. The "is internet really 
available" check can be done on the client side and is therefore much more 
reliable. With batman 0.3 all the packet flow towards and from the internet 
is going through batman. Batman just has to check whether traffic is coming 
back through the tunnel after sending packets to the internet. If this is not 
the case the batman node offering the internet is blacklisted and another 
gateway is chosen.
This has not been implemented yet but all the neccessary basics for that 
feature are completed by now. Expect this feature to come in the following 
weeks.

Regards,
Marek

  parent reply	other threads:[~2007-07-27 14:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 13:21 [B.A.T.M.A.N.] dynamic gateway / hna / services Freifunk Dresden
2007-07-24 18:35 ` Daniel Poelzleithner
2007-07-25 11:50   ` Alexander Morlang
2007-07-25 12:52     ` tetzlav
2007-07-25 15:06       ` Alexander Morlang
2007-07-25 15:19         ` Daniel Poelzleithner
2007-07-25 16:05           ` Alexander Morlang
2007-07-25 17:25             ` Daniel Poelzleithner
2007-07-26 12:33               ` Alexander Morlang
2007-07-25 16:21         ` clauz
2007-07-25 15:05     ` Daniel Poelzleithner
2007-07-25 14:56   ` Marek Lindner
2007-07-27 14:07 ` Marek Lindner [this message]
2007-07-27 14:43   ` Aaron Kaplan
2007-07-27 15:23     ` Marek Lindner
2007-07-27 16:03       ` Aaron Kaplan
2007-07-27 16:40         ` Marek Lindner
2007-07-27 20:41           ` Aaron Kaplan
2007-07-28  8:03             ` Axel Neumann
2007-07-27 14:59   ` Lui
2007-07-27 15:31     ` Marek Lindner
2007-08-02 14:26 ` Axel Neumann
  -- strict thread matches above, loose matches on Subject: below --
2007-08-03  9:31 Freifunk Dresden
2007-08-04  9:43 ` Axel Neumann
2007-08-04 21:38   ` Freifunk Dresden
2007-08-20 13:10   ` Alexander Morlang
2007-08-04 10:34 ` Marek Lindner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200707271607.24544.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox