From: gtolon@inti.gob.ar
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Multiple DHCP Gateways
Date: Mon, 15 Aug 2011 12:54:47 -0300 [thread overview]
Message-ID: <4E494147.5020709@inti.gob.ar> (raw)
In-Reply-To: <mailman.1.1313229601.6855.b.a.t.m.a.n@lists.open-mesh.org>
Thank you for your answers. I understood clearly how the system should
work, but i´m not using the git repository but the 2011.1.0 version.
I'll try with the repo to see what happens.
Best regards
Gabriel
> Message: 2
> Date: Fri, 12 Aug 2011 18:02:20 +0200
> From: Antonio Quartulli<ordex@autistici.org>
> 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.] Multiple DHCP Gateways
> Message-ID:<20110812160217.GB22361@ritirata.org.org>
> Content-Type: text/plain; charset=utf-8
>
> Hello and thank you for sharing your gw experience with us,
>
> On Wed, Aug 10, 2011 at 02:52:06PM -0300, gtolon@inti.gob.ar wrote:
>> Hi
> [CUT]
>> However, when the original gateway becomes
>> worse than the alternative, and the client chooses the new one as
>> preferred (observed with batctl gwl) i noticed that the subsequent
>> request DHCP messages are sent to the original server, even if it
>> doesn?t have the best link.
>>
>> I guess that?s because these subsequent DHCP requests are made as
>> Unicast to the original server and so Batman doesn?t redirect them,
>
> Unicast renewal requests are "dropped" only if the TQ towards the destination is
> smaller than the "current_GW_TQ - GW_THRESHOLD" (GW_THRESHOLD = 50).
> To clarify:
>
>
> In your topology you have three nodes: A, B and C. A and C are GWs. A is the
> current best GW for B and B got an IP from the DHCP server running on A. Then
> the link A<--> B becomes worse than B<--> C. At this point Batman-adv will
> drop a DHCP unicast renewal request directed to A
>
> if and only if TQ(C) - TQ(A)> 50
>
> Is this condition verified in your topology when your are observing the renewal
> DHCP packets?
>
> I hope I've been clear. :-)
>
>> but
>> i wonder how this behavior affects the network balance, because the
>> computers would get tied always to the original DHCP and IP default
>> gateway even if they moved, right?
>
> As above. Clients will keep the same GW as long as the link is still "usable"
> (difference on TQs greater than 50)
>
>>
>> Thank you very much
>
> Thank you too,
> Antonio
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 12 Aug 2011 19:22:28 +0200
> 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.] Multiple DHCP Gateways
> Message-ID:<201108121922.28786.lindner_marek@yahoo.de>
> Content-Type: Text/Plain; charset="utf-8"
>
> On Friday, August 12, 2011 18:02:20 Antonio Quartulli wrote:
>> In your topology you have three nodes: A, B and C. A and C are GWs. A is
>> the current best GW for B and B got an IP from the DHCP server running on
>> A. Then the link A<--> B becomes worse than B<--> C. At this point
>> Batman-adv will drop a DHCP unicast renewal request directed to A
>>
>> if and only if TQ(C) - TQ(A)> 50
>
> Be aware that only happens if you use the git repository. The "DHCP request
> drop" feature was not released yet.
>
> What version are you using ?
>
> Cheers,
> Marek
>
>
> ------------------------------
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@lists.open-mesh.org
> https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n
>
>
> End of B.A.T.M.A.N Digest, Vol 56, Issue 15
> *******************************************
>
next parent reply other threads:[~2011-08-15 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1313229601.6855.b.a.t.m.a.n@lists.open-mesh.org>
2011-08-15 15:54 ` gtolon [this message]
2011-08-15 16:29 ` [B.A.T.M.A.N.] Multiple DHCP Gateways Antonio Quartulli
2011-08-10 17:52 gtolon
2011-08-12 16:02 ` Antonio Quartulli
2011-08-12 17:22 ` Marek Lindner
2011-08-14 17:27 ` P. Mazart
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=4E494147.5020709@inti.gob.ar \
--to=gtolon@inti.gob.ar \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.