Hello Guido,
On Sun, Aug 05, 2012 at 03:26:43AM -0300, Gui Iribarren wrote:
Here i am again,
the involuntary stress-tester of gw_mode + bla2
and mailing-list readers' headache ;)
Given the setup described here
http://www.open-mesh.org/attachments/download/128
let's say one node in mesh1
I am having some trouble setting up batman-adv for my mesh. I can get each
access point to see the other using batctl o but I am not able to route
messages between my client devices. I think there is something wrong with my
bridging.
Here is the nature of my testbed:
2 Pandaboards
running
On Tuesday 07 August 2012 10:18:13 adam wiz wrote:
I am having some trouble setting up batman-adv for my mesh. I can get each
access point to see the other using batctl o but I am not able to route
messages between my client devices. I think there is something wrong with
my bridging.
[...]
In
On Tue, 7 Aug 2012, Jesper Juhl wrote:
Memory is allocated for 'tt_change_node' with kmalloc().
'tt_change_node' may go out of scope really being used for anything
This should of course read ... go out of scope without really being used ... .
(except have a few members initialized) if we hit
Memory is allocated for 'tt_change_node' with kmalloc().
'tt_change_node' may go out of scope really being used for anything
(except have a few members initialized) if we hit the 'del:' label.
This patch makes sure we free the memory in that case.
Signed-off-by: Jesper Juhl j...@chaosbits.net
---
On Tue, Aug 07, 2012 at 08:32:34PM +0200, Jesper Juhl wrote:
Memory is allocated for 'tt_change_node' with kmalloc().
'tt_change_node' may go out of scope really being used for anything
(except have a few members initialized) if we hit the 'del:' label.
This patch makes sure we free the memory
Thanks for the quick reply. I didn't mention my bridge setup because it didn't
work, but what I was doing was essentially following the quick-start-guide. In
this case I did not assign IP to bat0, but created a bridge called mesh-bridge
and added wlan0 and bat0 to it. I also used udhcp to
