From: Stephen Scheck <singularsyntax@gmail.com>
To: guile-user@gnu.org
Subject: Re: Curious if anyone has tried scripting BPF with Guile yet
Date: Sun, 17 Nov 2019 11:33:16 -0600 [thread overview]
Message-ID: <CAKjnHz0j3dVX6qcua3z8bfn4R-scC72cJtThc-ihvLYHiPcKsg@mail.gmail.com> (raw)
Daniel Tornabene <address@hidden> wrote:
> Did a couple of light searches, haven't found anything yet. Does anyone
> know if this is a silly question? As in, there's something that would
> prohibit a straight forward set of bindings via C to BPF, allowing one to
> write monitoring or introspection tools via Guile?
Does libpcap qualify? There’s this:
https://github.com/davelambert/guile-pcap
A quick look at the code suggests that it’s a fairly direct mapping of the
libpcap C API, and probably no longer maintained as the last commit was 9
years ago. Before I realized that existed, I started my own libpcap binding
for Guile, mostly as a learning exercise. It’s perhaps a bit more bespoke,
but not yet ready for release.
next reply other threads:[~2019-11-17 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 17:33 Stephen Scheck [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-02 1:38 Curious if anyone has tried scripting BPF with Guile yet Daniel Tornabene
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKjnHz0j3dVX6qcua3z8bfn4R-scC72cJtThc-ihvLYHiPcKsg@mail.gmail.com \
--to=singularsyntax@gmail.com \
--cc=guile-user@gnu.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).