Hi Mika -

10.1.4.2 is in a different subnet than 10.1.2.0/24, so the rule to table 66 doesn't match.

The IPs of your mesh interfaces (those interfaces that batmand is supposed to take care of) must be in the same subnet.

If you actually want to announce routes to different networks/hosts, use the network announcement feature of batmand: -a

Happy testing! Elektra

On Wed, 30 Mar 2016 07:31:45 +0000 Mika Rajala mika.rajala@patria.fi wrote:

Hi

I'm using the latest batmand with ns-3 to test routing.

I'm a bit of a newbie with this stuff, so this might be really simple

I'm not getting a ping through to 10.1.4.2, from a node that has this in its routing table

ip route ls table 66 10.1.4.2 via 10.1.2.2 dev eth 0 proto static src 10.1.2.3 // and so on

I'm guessing it's because of this ip rule 0: from all lookup local 6600: from all to 10.1.2.0/24 lookup 66 6699: from all lookup 65 6700: from all to 10.1.2.0/24 lookup 67 32766: from all lookup main 32767: from all lookup default

It isn't being told to look for the route to 10.1.4.2 from the table 66 where the route is stored.

-mika