b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: petermilani80@gmail.com
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Using BATMAN over ppp interfaces.
Date: Wed, 12 Jul 2023 04:29:50 -0000	[thread overview]
Message-ID: <168913619024.1040.2149557919065248797@diktynna.open-mesh.org> (raw)

Hi All,

I've just started using batman and was trying to see if I could get it to work over a serial radio link such as the simple serial devices commonly used in cheap drone telemetry. The goal here is to enable low bandwidth but adhoc ip networking. 

I had set up a pair of radios to connect using pppd and I was wondering if I could utilise batman to try and create a mesh. An example of setting up the serial ports as ppp interfaces:

$ sudo pppd /dev/ttyUSB0 57600 noauth nodetach 10.42.5.5:

That works fine but applying batman to that interface was unsuccessful. I think that was due to limitations in the ppp and interfaces created by pppd:
e.g.

$ sudo batctl if add ppp0
Error - failed to add interface ppp0: Invalid argument

The interface ppp0 was specified as POINTTOPOINT e.g.

$ ip link
$  ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 3

I'm not an expert in this so don't have full visibility of all the tools available.  I was wondering if there were better ways to set this up, possibly not using pppd? Any guidance would be appreciated.

cheers
Peter

             reply	other threads:[~2023-07-12  4:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12  4:29 petermilani80 [this message]
2023-07-12 11:55 ` Using BATMAN over ppp interfaces Simon Wunderlich
2023-07-12 12:18   ` Peter Milani
     [not found]   ` <CAB_9twWTs3dxT97ze2YP44_6vgJBdXw5yQcDUO=M=RvNP27D1w@mail.gmail.com>
2023-07-12 12:28     ` Simon Wunderlich

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=168913619024.1040.2149557919065248797@diktynna.open-mesh.org \
    --to=petermilani80@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).