From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: MK <mailing.m1@kkk-web.de>
Subject: Re: Does batman choose DHCP server by random?
Date: Tue, 29 Sep 2020 22:22:12 +0200 [thread overview]
Message-ID: <5095353.evS3lK4dNX@sven-edge> (raw)
In-Reply-To: <998e8a9b-e0c6-babb-0b45-5fb3fb657a32@kkk-web.de>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
On Tuesday, 29 September 2020 22:04:58 CEST MK wrote:
[...]
> Client:
> https://github.com/ffulm/firmware/blob/ec1d061e20557662dd8c7fc75dc603fee9bf77e0/files/etc/uci-defaults/50_freifunk-setup#L207
I think you forgot to paste the information here. It is not really relevant
what the server sees when the gw client has to decide where the IPv4 DHCP
Broadcast packet has to go.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-29 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 20:23 Does batman choose DHCP server by random? MK
2020-09-18 6:06 ` Sven Eckelmann
2020-09-29 20:04 ` MK
2020-09-29 20:08 ` Marek Lindner
2020-09-29 20:22 ` Sven Eckelmann [this message]
2020-10-02 8:29 ` MK
2020-10-02 9:25 ` Sven Eckelmann
2020-10-02 9:40 ` MK
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=5095353.evS3lK4dNX@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mailing.m1@kkk-web.de \
/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