All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Alfred 2016.1 bind errors
Date: Sat, 07 May 2016 08:39:54 +0200	[thread overview]
Message-ID: <1906308.Wsn34X6QAt@sven-edge> (raw)
In-Reply-To: <44fbd783f3734573bf7121e8bb3819fe@Ek.usurf.usu.edu>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

On Friday 06 May 2016 20:45:50 Jonathan Haws wrote:
> I am trying to get familiar with the Alfred tools and downloaded version
> 2016.1.  Unfortunately it didn't work - I couldn't get past a bind error:
> 
> root@sierra1:~# ./alfred -m -i bat0
> can't bind: Cannot assign requested address
> Failed to open interfaces
> 
> I had setup batman-adv with the commands:
> 
> batctl if add eth0
> ip link set up bat0 (eth0 was already up)
> 
> I rolled back to 2015.0 (per a hint at
> http://wiki.pinneberg.freifunk.net/alfred) and alfred started up just
> fine instead of giving the error.  However it periodically gives the
> following message:

Thanks for reporting it (why didn't FF Pinneberg report it?). Can you please 
try following workaround:

    make clean
    make CONFIG_ALFRED_CAPABILITIES=n
    # only when you've installed it before
    make CONFIG_ALFRED_CAPABILITIES=n install
    # try it again
    ./alfred -m -i bat0

It would also be interesting to see the output of `ip addr show dev bat0` and 
the used kernel version.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-05-07  6:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06 20:45 [B.A.T.M.A.N.] Alfred 2016.1 bind errors Jonathan Haws
2016-05-07  6:39 ` Sven Eckelmann [this message]
2016-05-07 16:37   ` Jonathan Haws
2016-05-07 16:46     ` Sven Eckelmann
2016-05-07 16:48     ` Jonathan Haws
2016-05-07 12:15 ` Matthias Schiffer
2016-05-07 16:42   ` Jonathan Haws
2016-05-07 16:47     ` Jonathan Haws
2016-05-08  4:19   ` Jonathan Haws

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=1906308.Wsn34X6QAt@sven-edge \
    --to=sven@narfation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.