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: 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.] DAT issue
Date: Wed, 07 Aug 2013 19:07:09 +0200	[thread overview]
Message-ID: <52027EBD.70007@gmail.com> (raw)
In-Reply-To: <20130807160945.GN2943@ritirata.org>

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

El 07/08/13 18:09, Antonio Quartulli escribió:
> Hello Fernando,
>
> to be honest the set up is not really clear to me, not because of the topology
> but because of all the bridges you created.
>
> Once thing I am confident enough is
> that if you have clients connected to wlan1.N and then you have a bridge
> configured as { wlan1, eth0, bat0 } this is not going to work as expected.
>
> Traffic sent over wlan1.1 will not be delivered to the bridge and so not
> delivered to bat0.
>
> You should include wlan1.1 in the bridge itself.
>
>
> Other than DAT, I expect this to be a general problem.
>
>
> Cheers,
>
Hi Antonio,

This stage is working correctly in a lab. Every client can connect and 
traffic is correctly routed and delivered. But I noticed the empty dat 
table, so I think there's something that I'm not understanding or, at 
least, that I could do it better. I'll try to explain what I want to 
achieve, perhaps in that way I could be understood better.

I have a freeradius service controlling clients acces, one of the 
attributes is the vlan-id, I'm using 802.1x. This part is quite easy I 
think, but the reason why nodes haven't got any ip (but management IP, 
which users can't achieve...) is not so easy.

1) I'm using dynamic vlan assignment. With this config, I just have to 
change attribs in my radius server and create a new pool in my fw... I 
haven't to configure anything in every node.

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..

There is an image attached explaining bridges.

Thanks a lot.
Fernando.

[-- Attachment #2: Interfaces.png --]
[-- Type: image/png, Size: 12460 bytes --]

  reply	other threads:[~2013-08-07 17:07 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 [this message]
2013-08-07 17:23             ` Marek Lindner
2013-08-14 10:05               ` Fernando Pizarro

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=52027EBD.70007@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