* [B.A.T.M.A.N.] Consistent bat0 hardware address?
@ 2016-08-25 15:52 Jonathan Haws
2016-08-26 1:45 ` Antonio Quartulli
0 siblings, 1 reply; 2+ messages in thread
From: Jonathan Haws @ 2016-08-25 15:52 UTC (permalink / raw)
To: b.a.t.m.a.n
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?
Thanks!
Jon
--
Jonathan R. Haws
Embedded Engineer
Space Dynamics Laboratory
jhaws@sdl.usu.edu
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [B.A.T.M.A.N.] Consistent bat0 hardware address?
2016-08-25 15:52 [B.A.T.M.A.N.] Consistent bat0 hardware address? Jonathan Haws
@ 2016-08-26 1:45 ` Antonio Quartulli
0 siblings, 0 replies; 2+ messages in thread
From: Antonio Quartulli @ 2016-08-26 1:45 UTC (permalink / raw)
To: Jonathan Haws,
The list for a Better Approach To Mobile Ad-hoc Networking
[-- 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-08-26 1:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).