get routing table to neighbors back about batphone

[aiQon]

As of now I back-ported batman standalone in my current working copy and added it to Control.java to start when all other services boot up. But having 2 services who constantly broadcast their advertisements does not sound reasonable with respect to both battery life time and bandwidth.

[lakeman]

What do you want to do with the list of devices on the network?
We decided some time ago to build a new routing engine that can work across weird network topologies and doesn't depend on having root access to change the routing table, or even on having IP addresses.
We have built a packet relay service that our voice protocol is built on. But I wouldn't call the API stable for 3rd party service development.

[aiQon]

Its a nice step to not have the need for root access :)
I work on my master thesis and program for android. My boss doesnt want me to talk about it yet in public but lets say that I need tcp connections among the nodes (if they are in reach). I thought I sync with upstream and ended up not having the route entries ><
Maybe I extend your broadcast messages to carry the IP addresses too and make the deamon add them. Lots of fiddling. Do you expect your servald to change a lot in the coming months?

EDIT: or do you think it might be possible to extend your packages with a 32bit field holding the IP4 addresses if available and provide them on "ip peers" command request?

[lakeman]

Simplest work around for now is just using an old version of our software. We're a long way from supporting anything like a TCP stream over our new routing protocol.

I've been working on some changes to support co-existing on an olsrd network. If you build our new olsr plugin from this repo;
https://github.com/servalproject/olsr
Then add some magic configuration, servald nodes wont be very chatty but can still resolve phone numbers and should be able to call each other. In this configuration, other peers (subscribers) that are discovered on the network will be marked as REACHABLE_UNICAST, and have their last seen IP4 address saved. But if you're using olsr, you probably want to read the routing table directly.

[quixotique]

Closing issue - won't fix.