All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: Is it possible to send all batman-adv traffic through http proxy cache?
Date: Fri, 4 Sep 2020 20:44:03 +0200	[thread overview]
Message-ID: <20200904184403.GA2391@otheros> (raw)
In-Reply-To: <CA+RexfHNV+HY28OiuHKNy4Rn=MM4gxOU0xCiVG0z56dfnv_z6g@mail.gmail.com>

Hi, 

On Fri, Aug 28, 2020 at 06:00:59PM -0400, Chuck Ritola wrote:
> Is it possible to send all batman-adv ethernet traffic through an HTTP
> proxy cache such as Squid?

Not really, there are a bunch of headers too many for an HTTP
caching proxy to work with batman-adv.

I'm wondering, are HTTP caching proxies actually still useful these
days where all major sides have switched to HTTPS?

> Another consideration was ALFRED but it doesn't appear to be easily
> integratable with existing software.

Alfred is more useful for little bits of information, not really
for complete packet streams.


The "best" solution I could think of right now for limited uplink
bandwidths is hosting content within your mesh network instead.
Like setting up a Seafile or MediaGoblin, for instance.

Or using P2P technologies, like Bittorrent. Although you might
need to be careful with this particular one that it won't greedly
occupy the rest of the bandwidth your uplink has left, if content is
still mainly shared over the uplink and not within the mesh.

Regards, Linus

  reply	other threads:[~2020-09-04 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 22:00 Is it possible to send all batman-adv traffic through http proxy cache? Chuck Ritola
2020-09-04 18:44 ` Linus Lüssing [this message]
2020-09-04 19:03   ` A. James Lewis
2020-09-08 15:47     ` Chuck Ritola

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=20200904184403.GA2391@otheros \
    --to=linus.luessing@c0d3.blue \
    --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.