From: Antonio Quartulli <a@unstable.cc>
To: Jonathan Haws <Jonathan.Haws@sdl.usu.edu>,
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.] Consistent bat0 hardware address?
Date: Fri, 26 Aug 2016 09:45:36 +0800 [thread overview]
Message-ID: <20160826014536.GS16157@flavoursapulia.lan> (raw)
In-Reply-To: <1472140362.4465.4.camel@sdl.usu.edu>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
On Thu, Aug 25, 2016 at 03:52:42PM +0000, Jonathan Haws wrote:
> Is there a way to ensure that the assigned hardware address for bat0 is
> consistent? What I would like to have is keep the hardware address the
> same across reboots. Can this be done? Would it be done through
> /etc/udev/rules.d? Or some other mechanism?
Yes, I'd suggest using udev for this. batman-adv generates a random address
every time it creates a new batX interface, therefore you need to use some
userspace tool to make it static.
Cheers,
--
Antonio Quartulli
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-08-26 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 15:52 [B.A.T.M.A.N.] Consistent bat0 hardware address? Jonathan Haws
2016-08-26 1:45 ` Antonio Quartulli [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=20160826014536.GS16157@flavoursapulia.lan \
--to=a@unstable.cc \
--cc=Jonathan.Haws@sdl.usu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox