From: Sven Eckelmann <sven@narfation.org>
To: Antonio Quartulli <a@unstable.cc>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [RFC v2 0/5] batman-adv netlink query API
Date: Sat, 19 Mar 2016 10:19:39 +0100 [thread overview]
Message-ID: <2005230.N8INYQKvQl@sven-edge> (raw)
In-Reply-To: <20160319084934.GD9971@prodigo.lan>
[-- Attachment #1: Type: text/plain, Size: 1791 bytes --]
On Saturday 19 March 2016 16:49:34 Antonio Quartulli wrote:
> On Fri, Mar 18, 2016 at 01:04:50PM +0100, Sven Eckelmann wrote:
> > On Friday 18 March 2016 13:00:54 Matthias Schiffer wrote:
> > [...]
> >
> > > > What about the "socket" file?
> >
> > [...]
> >
> > > Ah, I forgot about that one because it is very different from the
> > > others.
> > >
> > > I think it should be possible to convert "socket" as well by wrapping
> > > the
> > > BATADV_ICMP packets in netlink packets. Or maybe it would be possible to
> > > drop that altogether and just do ping/traceroute in userspace with
> > > AF_PACKET or similar?
> >
> > The latter could be problematic for TP meter implementation [1,2,3,4,5].
> > Antonio, do you have an opinion about that?
>
> Personally I wouldn't mind doing ping/traceroute 100% in userspace.
How can this be implemented 100% in userspace? Lets ignore the
reply/forwarding part for a second and just concentrate on the initiator of
the ping/traceroute. It can use AF_PACKET in userspace to send batadv packets
directly on the hardif. But here comes the first problem... which is the
correct hardif? There can be multiple and the userspace does not really know
which one is the one the kernel would use at a particular time. So you have to
implement the same algorithms in userspace the emulate the kernel part (or you
may do something completely different). And still then you would have problems
when the kernel is tweaked and the userspace didn't receive this tweak.
Maybe it is necessary to ask the kernel before sending the ping by asking him
"hey, what interface would use use right now and what other parameters are now
required". Similar to what "ip route get 8.8.8.8" would do.
Or am I just overcomplicated things now?
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-19 9:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 16:45 [B.A.T.M.A.N.] [RFC v2 0/5] batman-adv netlink query API Matthias Schiffer
2016-03-17 16:45 ` [B.A.T.M.A.N.] [RFC v2 1/5] batman-adv: add generic netlink query API to replace debugfs files Matthias Schiffer
2016-03-17 16:45 ` [B.A.T.M.A.N.] [RFC v2 2/5] batman-adv: netlink: add translation table query Matthias Schiffer
2016-03-17 16:45 ` [B.A.T.M.A.N.] [RFC v2 3/5] batman-adv: netlink: add originator and neighbor table queries Matthias Schiffer
2016-03-17 16:45 ` [B.A.T.M.A.N.] [RFC v2 4/5] batman-adv: add B.A.T.M.A.N. IV bat_{orig, neigh}_dump implementations Matthias Schiffer
2016-03-17 16:45 ` [B.A.T.M.A.N.] [RFC v2 5/5] batman-adv: add B.A.T.M.A.N. V " Matthias Schiffer
2016-03-17 17:04 ` [B.A.T.M.A.N.] [RFC v2 0/5] batman-adv netlink query API Matthias Schiffer
2016-03-18 7:09 ` Sven Eckelmann
2016-03-18 11:53 ` Matthias Schiffer
2016-04-18 10:59 ` Sven Eckelmann
2016-03-18 11:23 ` Sven Eckelmann
2016-03-18 12:00 ` Matthias Schiffer
2016-03-18 12:04 ` Sven Eckelmann
2016-03-19 8:49 ` Antonio Quartulli
2016-03-19 9:19 ` Sven Eckelmann [this message]
2016-04-18 11:10 ` Sven Eckelmann
2016-04-18 14:50 ` Simon Wunderlich
2016-04-20 2:31 ` Andrew Lunn
2016-04-20 11:39 ` Simon Wunderlich
2016-04-20 7:32 ` Matthias Schiffer
2016-04-20 7:39 ` Sven Eckelmann
2016-04-20 7:49 ` Matthias Schiffer
2016-04-20 7:53 ` Sven Eckelmann
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=2005230.N8INYQKvQl@sven-edge \
--to=sven@narfation.org \
--cc=a@unstable.cc \
--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