B.A.T.M.A.N Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: tcpdump-workers@lists.tcpdump.org
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: B.A.T.M.A.N. Advanced libpcap pull-request
Date: Fri, 15 Aug 2025 14:41:42 +0200	[thread overview]
Message-ID: <aJ8rBnoIBaOuKVCT@sellars> (raw)

Hello,

I wanted to cautiously inquire about the pull-request I had filed
about 5 years ago for adding B.A.T.M.A.N. Advanced support to
libpcap here:

"Add support for B.A.T.M.A.N. Advanced #980"
-> https://github.com/the-tcpdump-group/libpcap/pull/980

I'm not in a hurry and would need a while to add any change
requests anyway, due to other things having priorities right now.

But I had also been wondering why it might not be progressing
anymore, even though the initial feedback was very swift,
constructive and super helpful. Many thanks for that again!

I see that there generally is quite some activity in libpcap, so
it seems to me like it's a bit of an issue of motivation or
priorities on other people's sides as well, maybe?

(And I was also wondering if people maybe lost interest after
noticing that batman-adv is GPL licensed and a Linux kernel module
only so far. Do maintainers/devs on the libpcap/tcpdump project tend
to be more motivated to work with and integrate protocols that have
a copyfree instead of copyleft license and/or protocols with an
IETF RFC?)

Regards, Linus

             reply	other threads:[~2025-08-15 12:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 12:41 Linus Lüssing [this message]
2025-08-15 17:54 ` [tcpdump-workers] B.A.T.M.A.N. Advanced libpcap pull-request Michael Richardson

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=aJ8rBnoIBaOuKVCT@sellars \
    --to=linus.luessing@c0d3.blue \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=tcpdump-workers@lists.tcpdump.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