public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Sailash Moirangthem <sailashm@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Adhoc0 Interface not showing up
Date: Mon, 27 Jun 2016 09:52:45 +0200	[thread overview]
Message-ID: <11032818.o7fJnuSa5X@bentobox> (raw)
In-Reply-To: <CAM3k=86OU_+ZX8TqiBrLAqe446Z1YNGpD7WtH+BxPanrksjoAA@mail.gmail.com>

[-- 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 --]

      reply	other threads:[~2016-06-27  7:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23  9:24 [B.A.T.M.A.N.] Adhoc0 Interface not showing up Sailash Moirangthem
2016-06-23  9:55 ` Sven Eckelmann
2016-06-23 10:10   ` Sailash Moirangthem
2016-06-23 10:17     ` Sven Eckelmann
     [not found]       ` <CAM3k=84yf5iiZqYrzTK2cSwJGM8cmRH4Vf9cJxthz4Lp3dowCg@mail.gmail.com>
2016-06-23 10:53         ` Sven Eckelmann
2016-06-24 19:57           ` Sven Eckelmann
2016-06-25  4:34             ` sailashm
2016-06-25  5:34               ` Sven Eckelmann
2016-06-27  7:28                 ` Sailash Moirangthem
2016-06-27  7:52                   ` Sven Eckelmann [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=11032818.o7fJnuSa5X@bentobox \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=sailashm@gmail.com \
    /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