From: Marek Lindner <lindner_marek@yahoo.de>
To: 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.] "Distributed" DHCP vs gateway
Date: Sun, 7 Aug 2011 15:25:29 +0200 [thread overview]
Message-ID: <201108071525.29452.lindner_marek@yahoo.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1108060959150.9094@localhost6.localdomain6>
Hi,
> Now, what if the network is fractured and the same IP address gets
> assigned to a router (and thus is used as a prefix for that router's
> clients) on each side of the split? When the segments join up, we'll have
> multiple nodes with the same IP address and this will cause problems.
>
> Yes. The lease times will be very short, so this type of problem should
> resolve itself quickly.
you are overlooking the fact that you can't be sure each gateway receives
every DHCP packet even if you have a single network cell. On wireless you
always have packet loss as opposed to wired networks. Therefore this approach
won't be reliable. You can try things like arping nodes, etc but at the end of
the day you will always hit the same wall: Just because nodeX did not receive
a packet / can't reach nodeY you must not assume it does not exist.
> But, what do I do about how the gateway business interferes with DHCP?
> Could I somehow have two DHCP servers serving the same interface? One
> that serves out IP addresses and one that deals only with gateways?
Why not simply disable the "gateway business" ? Or better, not enabling it -
the gateway extension is disabled per default.
Regards,
Marek
next prev parent reply other threads:[~2011-08-07 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 14:19 [B.A.T.M.A.N.] "Distributed" DHCP vs gateway Ryan Hughes
2011-08-06 14:56 ` Troy Benjegerdes
2011-08-06 17:20 ` Ryan Jud Hughes
2011-08-15 21:15 ` Donald Gordon
2011-08-07 13:25 ` Marek Lindner [this message]
2011-08-08 19:15 ` The Doctor
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=201108071525.29452.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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