public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Fernando Pizarro <feanpg@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] DAT issue
Date: Wed, 14 Aug 2013 12:05:44 +0200	[thread overview]
Message-ID: <520B5678.4090200@gmail.com> (raw)
In-Reply-To: <201308080123.50676.lindner_marek@yahoo.de>

El 07/08/13 19:23, Marek Lindner escribió:
> Fernando,
>
> On Thursday, August 08, 2013 01:07:09 Fernando Pizarro wrote:
>> 2) I thougt having nodes without IP and just forwarding traffic to the
>> main GW (the firewall) through batman-adv, not natting every client
>> traffic with the node IP. In that way, roaming is working very good. The
>> problem are stablished sessions, these sessions are lost jumping from a
>> node to any other. I think this problem is nearly related to the empty
>> DAT table, and empty DAT table problem is nearly related too the nodes
>> has no IP assigned. However, I'm not sure about this..
> the DAT table has nothing to do with roaming or sessions. It merely is an IP
> address cache to speed up ARP lookups. Even without DAT everything should
> work. I recommend to read our DAT user guide:
> http://www.open-mesh.org/projects/batman-adv/wiki/DistributedArpTable
>
> If disabling DAT would break something we certainly would not make it an
> option to invite everybody to shoot themselves in the foot.  ;-)
>
> Therefore, I have to agree with Antonio that your problem is likely to be
> found somewhere else. First, you should define which established sessions
> break. The ones going into the internet or the ones you have locally.
> Depending on the answer we can dig deeper.
>
> Generally it is a good idea to simplfy the setup until a point where
> everything works. Then you can move forward and make things more complicated.
> For the time being I'd recommend to vastly simplify your bridge & vlan setup
> by bridging your AP interface with bat0 only (no vlans, no radius tags, no
> brvlanN interface) to see if your roaming works.
>
> Cheers,
> Marek
>
Hi all, thanks for your answers.

I have tested my setup in lab and I think that roaming works even if the 
DAT table is empty, local and external established connections seems to 
don't have problems.

Thanks for your help.
Fernando

      reply	other threads:[~2013-08-14 10:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07  8:58 [B.A.T.M.A.N.] DAT issue Fernando Pizarro
2013-08-07  9:09 ` Antonio Quartulli
2013-08-07 10:58   ` Fernando Pizarro
2013-08-07 12:05     ` Antonio Quartulli
2013-08-07 15:53       ` Fernando Pizarro
2013-08-07 16:09         ` Antonio Quartulli
2013-08-07 17:07           ` Fernando Pizarro
2013-08-07 17:23             ` Marek Lindner
2013-08-14 10:05               ` Fernando Pizarro [this message]

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=520B5678.4090200@gmail.com \
    --to=feanpg@gmail.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