All of lore.kernel.org
 help / color / mirror / Atom feed
* [B.A.T.M.A.N.] Ip rule issue
@ 2016-03-30  7:31 Mika Rajala
  2016-03-31  9:54 ` elektra
  0 siblings, 1 reply; 2+ messages in thread
From: Mika Rajala @ 2016-03-30  7:31 UTC (permalink / raw)
  To: b.a.t.m.a.n

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [B.A.T.M.A.N.] Ip rule issue
  2016-03-30  7:31 [B.A.T.M.A.N.] Ip rule issue Mika Rajala
@ 2016-03-31  9:54 ` elektra
  0 siblings, 0 replies; 2+ messages in thread
From: elektra @ 2016-03-31  9:54 UTC (permalink / raw)
  To: b.a.t.m.a.n

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


-- 
Viral meme of radical freedom 
 
The fact that you talk in your head doesn't mean that you think. 
 
The worst way to lose control over yourself is by trying to control yourself. 
 
Most people experience themselves as a voice in their head, telling them 
 who they are, what they think and what they have to do. 
 
http://en.wikipedia.org/wiki/Meme 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-03-31  9:54 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-30  7:31 [B.A.T.M.A.N.] Ip rule issue Mika Rajala
2016-03-31  9:54 ` elektra

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.