From: tanner.perkins@cnftech.com
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Dynamic DHCP server assignment and spin-up on batman-adv mesh network
Date: Tue, 31 Aug 2021 17:28:41 -0000 [thread overview]
Message-ID: <20210831172841.1195.74688@diktynna.open-mesh.org> (raw)
If this is not the best place to ask questions regarding mesh networks utilizing the batman-adv kernel module, I apologies and please point me to where I need to be.
I'm looking to set up distributed mesh network using the batman-adv Linux kernel module. However, I don't want to have to statically assign IP addresses to all my nodes therefore my first thought was to use DHCP. The problem arises in my scenario that any node could come and go in the mesh network as they move in and out range of the network. Therefore manually allocating a single or even a few DHCP servers isn't realistic as that DHCP server may drop out of the network at anytime. Is there a dynamic way to reassign the DHCP server based on the nodes still within the network when the previous DHCP server drops from the network?
Thanks,
-tdev
next reply other threads:[~2021-08-31 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 17:28 tanner.perkins [this message]
2021-09-01 19:54 ` Dynamic DHCP server assignment and spin-up on batman-adv mesh network Linus Lüssing
2021-09-01 20:12 ` Linus Lüssing
2021-09-02 13:02 ` Steve Newcomb
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=20210831172841.1195.74688@diktynna.open-mesh.org \
--to=tanner.perkins@cnftech.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).