public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Antonio Quartulli <a@unstable.cc>
Subject: Re: [B.A.T.M.A.N.] Problem with DHCP on batman-adv V
Date: Thu, 12 May 2016 07:05:20 +0200	[thread overview]
Message-ID: <1588847.AaxGtfAtFh@sven-edge> (raw)
In-Reply-To: <CAKOC6KQMSca-tSOoKFm9t1LXrOnwHKbf3Ac0hXT6QZWxM_uwtw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

On Wednesday 11 May 2016 18:58:48 Alvaro Antelo wrote:
> Hi everyone,
> 
> I am testing batman-adv V5 from the development feed on Chaos Calmer
> and so far everything is working except for DHCP IPv4, only static
> addresses.
> In the same setup wich involves bridges connected to bat0 interfaces,
> if I change only the routing algorithm to batman-adv IV, DHCP works
> fine.
> 
> Is it a expected behaviour?

Afaik there is no working gateway selection logic in B.A.T.M.A.N. V. At least 
Antonio works on some patches for this:

https://patchwork.open-mesh.org/patch/16139/
https://patchwork.open-mesh.org/patch/16140/
https://patchwork.open-mesh.org/patch/16141/
https://patchwork.open-mesh.org/patch/16142/
https://patchwork.open-mesh.org/patch/16143/

This includes splitting up the logic and use the metrics for each routing 
algorithm. But I think he can tell you more about now works (or doesn't) and 
what will work after his patchset is applied.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-05-12  5:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 21:58 [B.A.T.M.A.N.] Problem with DHCP on batman-adv V Alvaro Antelo
2016-05-12  5:05 ` Sven Eckelmann [this message]
2016-05-12  8:57   ` Antonio Quartulli
2016-05-12 13:42     ` Alvaro Antelo

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=1588847.AaxGtfAtFh@sven-edge \
    --to=sven@narfation.org \
    --cc=a@unstable.cc \
    --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