From: Mitar <mmitar@gmail.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Route selection over VPN links
Date: Tue, 17 Jul 2012 12:29:02 -0700 [thread overview]
Message-ID: <CAKLmikNosnGfr+Qx4KV39mmjcA1M-+VqpM7Nd6B_GQpXwjA_4Q@mail.gmail.com> (raw)
In-Reply-To: <20120717182254.GN4015@lunn.ch>
Hi!
On Tue, Jul 17, 2012 at 11:22 AM, Andrew Lunn <andrew@lunn.ch> wrote:
> You have to be careful with packet reordering.
Hm. True. Yes, maybe multipath routing is just in theory a good idea.
;-) I also don't really believe in it. Or even believe it is
necessary. But some balancing could be useful to have. For example,
based on origin. So all packets from same origin goes on the same
link, and the other on the other. Is this possible to achieve?
> Are these assumptions really true? In my home setup, my ADSL modem is
> where my telephone socket is. My VPN server is somewhere else and
> there is a wifi and a powerline link in between. If my neighbors swamp
> the wifi channel with their torrent download, my VPN will
> suffer. (Well not really, i known this wifi stuff better than my
> neighbors)
I think we talk about different topologies here. We have a gateway
server on collocation, with VPN servers spread around the country. We
connect all nodes to those VPN servers, and VPN servers to gateway
server. We do not use ADSL uplinks for anything else than just to
connect to those VPN servers.
I am not talking about user's VPN servers, but network's. The ones
which allow nodes to be in the same network even if there is no (yet)
existing WiFi link between them.
Mitar
next prev parent reply other threads:[~2012-07-17 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 20:29 [B.A.T.M.A.N.] Route selection over VPN links Mitar
2012-07-16 10:02 ` Marek Lindner
2012-07-17 6:36 ` Mitar
2012-07-17 10:57 ` Marek Lindner
2012-07-17 18:06 ` Mitar
2012-07-17 18:22 ` Andrew Lunn
2012-07-17 19:29 ` Mitar [this message]
2012-07-18 6:43 ` Christian Huldt
2012-07-18 8:15 ` Mitar
2012-07-18 20:06 ` Marek Lindner
2012-07-20 21:14 ` Mitar
2012-07-21 10:12 ` 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=CAKLmikNosnGfr+Qx4KV39mmjcA1M-+VqpM7Nd6B_GQpXwjA_4Q@mail.gmail.com \
--to=mmitar@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.