[B.A.T.M.A.N.] Adhoc0 Interface not showing up

[B.A.T.M.A.N.] Adhoc0 Interface not showing up

[Sailash Moirangthem]

Hi Team,

I really appreciate for all your contributions in the mesh network.
I am trying to set-up mesh network using tplink WR1043ND routers and
raspberry pi B+ integrated with ra2800usb (wi pi). The tplink routers
are working as expected. Howoever, the raspberry pi is not working.

The configuration file for the Pi board is as follows:

config interface loopback
 option ifname lo
option proto static
 option ipaddr 127.0.0.1
 option netmask 255.0.0.0
config interface lan
option ifname eth0
option type bridge
 option proto static
option ipaddr 192.168.1.1
option netmask 255.255.255.0
 config interface 'mesh'
option ifname 'adhoc0'
option mtu '1528'
 option proto 'batadv'
 option mesh 'bat0'
 config interface mb
option ifname bat0
option type bridge option proto static
 option ipaddr 192.168.99.26
 option netmask 255.255.255.0

using the same config in tplink routers work but not in pi boards. The
adhoc0 interface is not shown up in pi board.

cat sys/class/net/adhoc0/batman-adv/mesh_iface says none.
cat sys/class/net/adhoc0/batman-adv/staus says not in use.

Please Help!!! Thanks in advance.

Yours Sincerely,
Sailash M
Research Student

Re: [B.A.T.M.A.N.] Adhoc0 Interface not showing up

[Sven Eckelmann]

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

On Thursday 23 June 2016 14:54:37 Sailash Moirangthem wrote:
[..]
> I am trying to set-up mesh network using tplink WR1043ND routers and
> raspberry pi B+ integrated with ra2800usb (wi pi). The tplink routers
> are working as expected. Howoever, the raspberry pi is not working.

Sounds more like an OpenWrt/LEDE question. But I think the persons which
created the OpenWrt/LEDE scripts for batman-adv are subscribed to this
list.

> The configuration file for the Pi board is as follows:
> 
[...]
>  config interface 'mesh'
> option ifname 'adhoc0'
> option mtu '1528'
>  option proto 'batadv'
>  option mesh 'bat0'
[...]

Why are you adding the interface in /etc/config/wireless and not as
described in the quick start guide [1] to /etc/config/wireless? I would
suggest to try to use the /etc/config/wireless because these are
"dynamically" created interfaces and (not tested) should work better with
netifd.

Is it working when you do `batctl if add adhoc0`? Is something shown
in dmesg related to an error while adding the interface?

Kind regards,
	Sven

[1] https://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config

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

Re: [B.A.T.M.A.N.] Adhoc0 Interface not showing up

[Sailash Moirangthem]

My wireless configuration is:

config wifi-iface wmesh
option device radio1
option ifname adhoc0
option network mesh
option mode adhoc
option ssid mesh
option bssid 02:ca:ca::ca:40
option encryption none

So, it is almost the same as mentioned in
[1]  https://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config

Yes, I tried batctl if add adhoc0, and when i put batctl if.. it days
adhoc inactive.
Nothing critical says in dmesg. One line is to increase the mtu from
1500 to 1532 for eth0.

Thanks for your help. Please check. I hope we can fix this.

Thanks,
Sailash M


On Thu, Jun 23, 2016 at 3:25 PM, Sven Eckelmann <sven@narfation.org> wrote:
> On Thursday 23 June 2016 14:54:37 Sailash Moirangthem wrote:
> [..]
>> I am trying to set-up mesh network using tplink WR1043ND routers and
>> raspberry pi B+ integrated with ra2800usb (wi pi). The tplink routers
>> are working as expected. Howoever, the raspberry pi is not working.
>
> Sounds more like an OpenWrt/LEDE question. But I think the persons which
> created the OpenWrt/LEDE scripts for batman-adv are subscribed to this
> list.
>
>> The configuration file for the Pi board is as follows:
>>
> [...]
>>  config interface 'mesh'
>> option ifname 'adhoc0'
>> option mtu '1528'
>>  option proto 'batadv'
>>  option mesh 'bat0'
> [...]
>
> Why are you adding the interface in /etc/config/wireless and not as
> described in the quick start guide [1] to /etc/config/wireless? I would
> suggest to try to use the /etc/config/wireless because these are
> "dynamically" created interfaces and (not tested) should work better with
> netifd.
>
> Is it working when you do `batctl if add adhoc0`? Is something shown
> in dmesg related to an error while adding the interface?
>
> Kind regards,
>         Sven
>
> [1] https://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config

Re: [B.A.T.M.A.N.] Adhoc0 Interface not showing up

[Sven Eckelmann]

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

On Thursday 23 June 2016 15:40:53 Sailash Moirangthem wrote:
> My wireless configuration is:
> 
> config wifi-iface wmesh
> option device radio1
> option ifname adhoc0
> option network mesh
> option mode adhoc
> option ssid mesh
> option bssid 02:ca:ca::ca:40
> option encryption none
> 
> So, it is almost the same as mentioned in
> [1]  https://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config
> 
> Yes, I tried batctl if add adhoc0, and when i put batctl if.. it days
> adhoc inactive.

Please show the output of "iw dev", "iw phy", "ip link" and "batctl if"
after you did the "batctl if add adhoc0".

> Nothing critical says in dmesg. One line is to increase the mtu from
> 1500 to 1532 for eth0.

Hm, this retracted information is not telling the whole story. You are
most likely not telling us about the other batman-adv messages. These
for example would tell us what interfaces are added/removed/activated/...

Kind regards,
	Sven

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

Re: [B.A.T.M.A.N.] Adhoc0 Interface not showing up

[Sven Eckelmann]

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

[Please don't remove b.a.t.m.a.n@lists.open-mesh.org without
giving a reason. I nearly only replied to you instead to
the mailing list]

On Thursday 23 June 2016 16:13:11 Sailash Moirangthem wrote:
> Please check the results of the commands.

"ip link" shows that the adhoc0 interface is down. Please make
sure that the interface goes up. This is now definitely an
OpenWrt+wifi driver question and not related to batman-adv.

The interface combination [1] is showing only
"#{ managed, AP, mesh point } <= 8,". So you can try to
deactivate your AP interface in /etc/config/wireless. Make
sure that you only see the adhoc0 interface in `iw dev`
after you've restarted the wifi.

Kind regards,
	Sven

[1] https://www.kernel.org/doc/htmldocs/80211/API-struct-ieee80211-iface-combination.html

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

Re: [B.A.T.M.A.N.] Adhoc0 Interface not showing up

[Sven Eckelmann]

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

On Thursday 23 June 2016 12:53:35 Sven Eckelmann wrote:
[...]
> "ip link" shows that the adhoc0 interface is down. Please make
> sure that the interface goes up. This is now definitely an
> OpenWrt+wifi driver question and not related to batman-adv.
> 
> The interface combination [1] is showing only
> "#{ managed, AP, mesh point } <= 8,". So you can try to
> deactivate your AP interface in /etc/config/wireless. Make
> sure that you only see the adhoc0 interface in `iw dev`
> after you've restarted the wifi.

Any success when only using adhoc0 without the extra AP interface? 

Kind regards,
	Sven

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

Re: [B.A.T.M.A.N.] Adhoc0 Interface not showing up

[sailashm]

Hi Sven,

I will give it a shot on monday and let you know. However, when using the BATMAN-adv in my 5 tplink routers, the AP interface keeps disconnecting and is not stable. The version of batman-adv is 14. Is this version of batman-adv unstable?

Thanks,
Sailash M

> On 25-Jun-2016, at 1:27 AM, Sven Eckelmann <sven@narfation.org> wrote:
> 
>> On Thursday 23 June 2016 12:53:35 Sven Eckelmann wrote:
>> [...]
>> "ip link" shows that the adhoc0 interface is down. Please make
>> sure that the interface goes up. This is now definitely an
>> OpenWrt+wifi driver question and not related to batman-adv.
>> 
>> The interface combination [1] is showing only
>> "#{ managed, AP, mesh point } <= 8,". So you can try to
>> deactivate your AP interface in /etc/config/wireless. Make
>> sure that you only see the adhoc0 interface in `iw dev`
>> after you've restarted the wifi.
> 
> Any success when only using adhoc0 without the extra AP interface? 
> 
> Kind regards,
>    Sven

Re: [B.A.T.M.A.N.] Adhoc0 Interface not showing up

[Sven Eckelmann]

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

On Saturday 25 June 2016 10:04:41 sailashm@gmail.com wrote:
> Hi Sven,
> 
> I will give it a shot on monday and let you know. However, when using the 
BATMAN-adv in my 5 tplink routers, the AP interface keeps disconnecting and is 
not stable. The version of batman-adv is 14. Is this version of batman-adv 
unstable?

batman-adv with the COMPAT_VERSION 14 (used in v2011.3.0 <= batman-adv < 
v2014.0.0) is either really old and unsupported (it has known problems which 
fill not be fixed by us anymore).... or you are using batman-adv-legacy [1] 
from Matthias Schiffer. If the latter is the case then please upgrade to the 
latest version from him, test again and then contact him when you need support 
for this version.

But to be honest, batman-adv is not managing the AP interface and thus it 
should have no influence on the AP interface authentication/deauthentication 
behavior or the AP interface state.

Kind regards,
	Sven

[1] https://github.com/freifunk-gluon/batman-adv-legacy

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

Re: [B.A.T.M.A.N.] Adhoc0 Interface not showing up

[Sailash Moirangthem]

Hi Sven,
This question may sound dumb. But I need your help in this please. I
upgraded my openwrt to the latest version 15.05. I then tried
installing kmod-batman-adv. It gave me error:

satisfy_dependencies_for: Cannot satisfy the following dependencies
for kmod-batman-adv:
kernel (= 3.18.14-1-406f55e08cbd4433be5683443e405921) *

I followed the following steps:
1 . Note: If you downloaded an Openwrt release but intend to build the
latest batman-adv package you might need to modify your
feeds.conf(.default). Make sure you have "src-git routing
git://github.com/openwrt-routing/packages.git" instead of e.g.
"src-git routing
git://github.com/openwrt-routing/packages.git;for-12.09.x".

This doesnt seem to work. Can you please tell me the steps on how to
install the latest batman-adv in my 15.05 openwrt firmware. Thanks a
ton.

Thanks,
Sailash M

On Sat, Jun 25, 2016 at 11:04 AM, Sven Eckelmann <sven@narfation.org> wrote:
> On Saturday 25 June 2016 10:04:41 sailashm@gmail.com wrote:
>> Hi Sven,
>>
>> I will give it a shot on monday and let you know. However, when using the
> BATMAN-adv in my 5 tplink routers, the AP interface keeps disconnecting and is
> not stable. The version of batman-adv is 14. Is this version of batman-adv
> unstable?
>
> batman-adv with the COMPAT_VERSION 14 (used in v2011.3.0 <= batman-adv <
> v2014.0.0) is either really old and unsupported (it has known problems which
> fill not be fixed by us anymore).... or you are using batman-adv-legacy [1]
> from Matthias Schiffer. If the latter is the case then please upgrade to the
> latest version from him, test again and then contact him when you need support
> for this version.
>
> But to be honest, batman-adv is not managing the AP interface and thus it
> should have no influence on the AP interface authentication/deauthentication
> behavior or the AP interface state.
>
> Kind regards,
>         Sven
>
> [1] https://github.com/freifunk-gluon/batman-adv-legacy

Re: [B.A.T.M.A.N.] Adhoc0 Interface not showing up

[Sven Eckelmann]

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

On Monday 27 June 2016 12:58:24 Sailash Moirangthem wrote:
> Hi Sven,
> This question may sound dumb. But I need your help in this please. I
> upgraded my openwrt to the latest version 15.05. I then tried
> installing kmod-batman-adv. It gave me error:
> 
> satisfy_dependencies_for: Cannot satisfy the following dependencies
> for kmod-batman-adv:
> kernel (= 3.18.14-1-406f55e08cbd4433be5683443e405921) *
> 
> I followed the following steps:
> 1 . Note: If you downloaded an Openwrt release but intend to build the
> latest batman-adv package you might need to modify your
> feeds.conf(.default). Make sure you have "src-git routing
> git://github.com/openwrt-routing/packages.git" instead of e.g.
> "src-git routing
> git://github.com/openwrt-routing/packages.git;for-12.09.x".
> 
> This doesnt seem to work. Can you please tell me the steps on how to
> install the latest batman-adv in my 15.05 openwrt firmware. Thanks a
> ton.

Not sure what this has to do with the the problem you quoted earlier.
I would just have done following to generate 15.05 images which already
include batman-adv:

    git clone git://git.openwrt.org/15.05/openwrt.git openwrt-15.05
    cd openwrt-15.05
    ./scripts/feeds update
    ./scripts/feeds install kmod-batman-adv
    ./scripts/feeds install batctl
    cat << EOF > .config
    CONFIG_TARGET_ar71xx=y
    CONFIG_TARGET_ar71xx_generic=y
    CONFIG_TARGET_ar71xx_generic_Default=y
    CONFIG_KMOD_BATMAN_ADV_BLA=y
    CONFIG_KMOD_BATMAN_ADV_DAT=y
    CONFIG_KMOD_BATMAN_ADV_MCAST=y
    CONFIG_PACKAGE_batctl=y
    CONFIG_PACKAGE_kmod-batman-adv=y
    CONFIG_PACKAGE_kmod-crypto-crc32c=y
    CONFIG_PACKAGE_kmod-crypto-hash=y
    CONFIG_PACKAGE_kmod-lib-crc16=y
    CONFIG_PACKAGE_kmod-lib-crc32c=y
    EOF
    make defconfig
    make -j$(nproc || echo 1)

(make sure you remove the "    " in front when you want to copy+paste the
commands).

You can find the generated images in bin/ar71xx/

Kind regards,
	Sven

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