From: Ufo <ufo@rund.freifunk.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] openwrt config changes when upgrading from 2014-4 to 2015-0 ?
Date: Sat, 13 Jun 2015 19:41:14 +0200 [thread overview]
Message-ID: <557C6B3A.4020305@rund.freifunk.net> (raw)
In-Reply-To: <5848467.YBQmR7qBth@voltaire>
ok, my '10 days older openwrt trunk' with batman-adv 2015.0 (compiled
via sdk) is running without bridge-problems.
so batman-adv is not the guilty one
Am 13.06.15 um 18:21 schrieb Marek Lindner:
> On Saturday, June 13, 2015 17:40:32 Ufo wrote:
>> thank you for upgrading batman-adv inside openwrt trunk to
>> 2015-0
>>
>> im testing new version (yesterdays openwrt trunk) but have
>> problems: the bridge (br-mesh12) with bat-interface and wifi-vAP
>> isnt complete, the bat-interface is missing the "wifi" command
>> also doesnt repair that
>>
>> but, when i delete vlan-setting (for interface, where batman-adv
>> is running on) problems are gone.
>>
>> maybe config for openwrt/batman-adv has changed, or some of our
>> settings are outdated and now obsolete?
>>
>> ufo
>>
>> p.s. with 10 days old openwrt trunk (and batman-adv 2014-4) the
>> problem doesnt appear
>
> The batman-adv uci config has not changed one bit. You can check
> the package diff:
> https://github.com/openwrt-routing/packages/commit/4dc2c500ffde0e248dbc83e5bd904ec0c9af0c42
>
> Can you try the '10 days older openwrt trunk' with batman-adv
> 2015.0 ? That way you can rule out batman-adv.
>
> Cheers, Marek
>
--
---
Freifunk Leipzig http://leipzig.freifunk.net
prev parent reply other threads:[~2015-06-13 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 15:40 [B.A.T.M.A.N.] openwrt config changes when upgrading from 2014-4 to 2015-0 ? Ufo
2015-06-13 16:21 ` Marek Lindner
2015-06-13 17:41 ` Ufo [this message]
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=557C6B3A.4020305@rund.freifunk.net \
--to=ufo@rund.freifunk.net \
--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.