From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Mahdi Mokhtari <mmokhi@freebsd.org>
Subject: Re: [B.A.T.M.A.N.] batman-adv and/or batmand porting effort to FreeBSD
Date: Wed, 14 Feb 2018 10:03:44 +0100 [thread overview]
Message-ID: <3678642.ZAPEa3b1nE@prime> (raw)
In-Reply-To: <839a5aa7-ed42-27d5-1453-6b152943d811@FreeBSD.org>
[-- Attachment #1: Type: text/plain, Size: 2612 bytes --]
Hi Mokhi,
On Tuesday, February 13, 2018 6:52:51 PM CET Mahdi Mokhtari wrote:
> Hi,
>
> After some time of playing with the B.A.T.M.A.N protocol and
> net-interface on OpenWRT and Debian I was thinking to use it with
> the servers I use everyday (and maybe on routers/appliances I have
> nanoBSD on).
>
> So I started an effort...
> (As a background) I already ported some applications to FreeBSD [and I'm
> maintaining them] and
> also I did work already on the Linux emulation layer of FreeBSD (FreeBSD
> has a Linux syscall-emulation and Linux-KPI layers).
> So my approach (as naturally I didn't expect the build of batman-adv.ko
> to be successful as is),
> was based on the approach that we [at FreeBSD] did to port Linux's
> drm... <https://github.com/FreeBSDDesktop/kms-drm>
> I ended up in adding some header-files to FreeBSD Linux-KPI (like
> average.h, percpu.h, ...).
> Now I'm at a state that Netlink blocks me and I'm to determine next step :-)
> [Which I don't assume it being trivial with my current approach]
That sounds interesting ... will you be able to follow up the port with our
development, or what is your plan on that? I'd assume that you need to rewrite
a rather large chunk of "Linuxism" as you say, and I would assume that porting
newer versions as we release would be quite some manual work.
>
> So I'd like to ask:
> 1- Is it better approach to "rewrite" batman-adv.ko [at least
> Netlink-ish (let's call "Linuxism") parts] than what I'm doing now?
I don't have enough knowledge of FreeBSD to answer that. I would assume that
the skb handling and netlink/debugfs parts are Linux specific. You'd at least
need to rewrite those. You better don't touch the routing code, I would not
advise rewriting that.
> 2- Any other efforts are being done out there?
I'm not aware. At least nothing serious (I remember someone demanding batman-
adv to work in web browsers). :D
> 3- is batmand deprecated [So I should mainly focus on batman-adv.ko]?
We agreed to not call it deprecated, but there hasn't been any developments in
the past 7 years except for some build-specific issues. I'd suggest to focus on
batman-adv.ko. batmand may be easier to port though, but I see more people
using batman-adv today.
> 4- any other comments do you have? :D
Good luck! :D
And please keep us posted!
>
> P.S. sorry if I'm not really good at starting conversation from scratch
> and out-of-nowhere :D
> but I hope by continuing the collaboration we can have better (more
> enriched) FreeBSD and better (as in more portable) B.A.T.M.A.N :-)
Looking forward to it!
Cheers,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-14 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 15:22 [B.A.T.M.A.N.] batman-adv and/or batmand porting effort to FreeBSD Mahdi Mokhtari
2018-02-14 9:03 ` Simon Wunderlich [this message]
2018-02-14 12:39 ` elektra
2019-12-28 19:50 ` batman-adv on FreeBSD 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=3678642.ZAPEa3b1nE@prime \
--to=sw@simonwunderlich.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mmokhi@freebsd.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