Thank you Marek and Marco for your suggestions.
I have solved the following problem:
>2) When launched in debug mode (using the command batmand -d 3 ath0 &), the
> daemon starts to generate OGMs and to fill up its routing tables in a
> correct way. The problem occurs when I tries to ping an host in the network
> because the routing process uses the default routing table (that has not
> been modified by the batman daemon) and it is not aware on the correct
> batman routing tables.
Now I'm able to ping every originator in the network. The problem is derived from some iptables filters that stop the ping. Executing the following command I remove the filters solving the problem:
iptables --flush
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
As concern the other problem it's still present.
In my meshboxes, BATMAN sends OGMs only when it's launched in debug mode using the command
"batmand -d 3 ath0 &". In this case, I see OGMs travelling in the network using Wireshark and the command "ip route ls table 66" lists all reachable batman nodes.
When I launch the daemon in normal mode, using the command "batmand ath0", no error is displayed but no OGMs is observed to be travelling in the network using Wireshark. The only message displayed is:
"Interface activated: ath0
Using interface ath0 with address 10.0.0.1 and broadcast address 10.255.255.255"
Also the command "ip route ls table 66" does not produce any output.
And finally another question...
Is it normal to observe 3 different processes named batmand using the shell command ps?
Thank you in advance!
Best regards,
Massimo