All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Haws <Jonathan.Haws@sdl.usu.edu>
To: Matthias Schiffer <mschiffer@universe-factory.net>
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
	<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, 7 May 2016 16:42:01 +0000	[thread overview]
Message-ID: <1b43c9dff51e492397ca5202456d9d2f@Ek.usurf.usu.edu> (raw)
In-Reply-To: 33aefc13-e1a0-cef5-74f1-d21d7112b7d3@universe-factory.net

On 05/07/2016 06:16 AM, Matthias Schiffer wrote:
> On 05/06/2016 10:45 PM, 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:
>>
>> announce master ...
>> Error during sent: Cannot assign requested address
>>
>> I also tried alfred -m -i eth0 with the same results.
>>
>> Is there something wrong in my configuration?  Can anyone point me in
>> the right direction?  I've read through the Wiki for both batman-adv and
>> alfred and am out of ideas.
>>
>> I'm trying to prove this setup and get familiar with it in a virtual
>> environment, so I am using VirtualBox to setup a network of 4 nodes in
>> my mesh.  Should be simple enough, and batman-adv seems to work just
>> great - once its up and running, all nodes can communicate one with
>> another as expected.  Only issue is I am trying to get alfred to work
>> with batadv-vis to give me a graph to tell me it really is working right.
>>
>> Thoughts?
>> Thanks!
>> Jon
>>
>
> alfred explicitly binds to the link-local IPv6 address of the interface
> since version 2016.0. I suspect one of the following caveats might be your
> problem:
>
> * The link-local IPv6 address must match the MAC address of the interface
> (here bat0) (derived by flipping the 2 bit of the first byte, and adding
> fe80 and fffe); this ususally breaks when the MAC address is changed after
> the interface is up
> * The link-local address must not be tentative when alfred is started
> (duplicate address detection must have finished; this usually means that
> the interface must be up for 3 seconds before alfred is started)
>
> I hope this helps...

This does help.  I don't believe my system is configured to use IPv6 at 
the moment, though the kernel appears to have the right configuration.

root@sierra1:~# zcat /proc/config.gz | grep IPV6
CONFIG_IPV6=y
CONFIG_IPV6_ROUTER_PREF=y
# CONFIG_IPV6_ROUTE_INFO is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_IPV6_VTI is not set
CONFIG_IPV6_SIT=y
# CONFIG_IPV6_SIT_6RD is not set
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=m
# CONFIG_IPV6_GRE is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_IPV6_MROUTE is not set
# CONFIG_NF_DEFRAG_IPV6 is not set
# CONFIG_NF_CONNTRACK_IPV6 is not set
# CONFIG_NF_REJECT_IPV6 is not set
# CONFIG_NF_LOG_IPV6 is not set
CONFIG_IP6_NF_MATCH_IPV6HEADER=m


Am I missing a kernel configuration or just some missing configuration 
on my network interfaces?

root@sierra1:~# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
group default
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 scope host lo
        valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
master bat0 state UP group default qlen 1000
     link/ether 08:00:27:09:a2:bc brd ff:ff:ff:ff:ff:ff
     inet 192.168.74.101/24 scope global eth0
        valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000
     link/ether 08:00:27:b5:50:cb brd ff:ff:ff:ff:ff:ff
     inet 192.168.73.101/24 scope global eth1
        valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000
     link/ether 08:00:27:30:0d:96 brd ff:ff:ff:ff:ff:ff
     inet 10.0.2.15/24 brd 10.0.2.255 scope global eth2
        valid_lft forever preferred_lft forever
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default
     link/sit 0.0.0.0 brd 0.0.0.0
6: bat0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state 
UNKNOWN group default
     link/ether f2:52:c3:50:2e:d7 brd ff:ff:ff:ff:ff:ff


root@sierra1:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
master bat0 state UP mode DEFAULT group default qlen 1000
     link/ether 08:00:27:09:a2:bc brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
state UP mode DEFAULT group default qlen 1000
     link/ether 08:00:27:b5:50:cb brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
state UP mode DEFAULT group default qlen 1000
     link/ether 08:00:27:30:0d:96 brd ff:ff:ff:ff:ff:ff
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group 
default
     link/sit 0.0.0.0 brd 0.0.0.0
6: bat0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state 
UNKNOWN mode DEFAULT group default
     link/ether f2:52:c3:50:2e:d7 brd ff:ff:ff:ff:ff:ff





  reply	other threads:[~2016-05-07 16:42 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
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 [this message]
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=1b43c9dff51e492397ca5202456d9d2f@Ek.usurf.usu.edu \
    --to=jonathan.haws@sdl.usu.edu \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=mschiffer@universe-factory.net \
    /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.