LinuxQuestions.org - How to route using my own custom routing tables and not the Kernel's table

Hi,

im trying out a mesh-networking protocol called BATMAN. the protocol scans for other nodes and saves the nodes in an i.p table #66 ( the kernel uses #254 I think )

you see the protocol saves the nodes in ip table 66 and then makes an "ip rule"which states that everything destined for the nodes should go through that table.

Code:

~# ip rule

0:        from all lookup local 

6600:        from all to 192.168.10.0/24 lookup 66 

6699:        from all lookup 65 

6700:        from all to 192.168.10.0/24 lookup 67 

32766:        from all lookup main 

32767:        from all lookup default

the rule 6600 tells to lookup table 66 right ? now my table 66 contains the nodes:

Code:

~# ip route ls table 66

192.168.10.10 dev wlan0  proto static  scope link  src 192.168.10.11 

192.168.10.12 via 192.168.10.10 dev wlan0  proto static  scope link  src 192.168.10.11

this means my pc ( .10.11 ) cannot see node12 ( .10.12 ) but the BATMAN routing protocol sees it and says its accessible through node10 ( .10.10 ).

now for the issue at hand. despite this rule being in place the kernel's table is used all the time and any attempts to ping out of range computers means i get the "destination host is unreachable" message. what must i do such that my network hardware uses table 66 only when these specific nodes need to be contacted ?

thanks.