link local IP (zeroconf/avahi)
Ryan Nowakowski
that you guys require the user to set an IP address to do VoIP. Have you
thought about using link local IPs[2] from avahi[3] instead of making
the user set an IP?
- Ryan
1. http://twit.tv/show/floss-weekly/196
2. http://en.wikipedia.org/wiki/Link-local_address
3. http://en.wikipedia.org/wiki/Avahi_(software)
Song, Stephen
Zeroconf has come up a few in times in discussion.
https://groups.google.com/forum/#!searchin/village-telco-dev/zeroconf
In part, BATMAN-ADV operating at layer 2 has made the discussion from
a data perspective somewhat moot as the mesh now acts like a big
switch. We only need IP addresses for the MPs so that the local
dialplan on each MP can resolve other Mesh Potatoes for voice calls.
The way the Asterisk dialplan works on the Mesh Potato is that you can
dial the IP address of any other Mesh Potato on the network and
Asterisk will attempt to call that Mesh Potato. Better still you can
just dial just the last octet of the IP address and it still works.
It is an ingenious hack devised by David Rowe to allow calls to be
made on the mesh without having to have a SIP server.
From that perspective we've found so far that people prefer to set
their own extension / IP address. The Mesh Potato is designed so this
can be done via the phone. Dial 2663 and enter the IP address with
an * after each octet.
Cheers... Steve
> --
> You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
> To post to this group, send email to village-...@googlegroups.com.
> To unsubscribe from this group, send email to village-telco-...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.
>
--
Steve Song
http://manypossibilities.net
http://villagetelco.org
elektra
I fully agree with Steve.
For many people interested in mesh networking, complete autoconfiguration of a mesh node is something like the holy grail. I suppose you can guess from my wording that I am skeptical towards this. So take everything with a grain of salt - what you read here is just my 0.0000002 bitcoin ;)
Complete autoconfiguration is basically not a problem. You don't even need zeroconf if you are using IPv6 with batman-adv. Just add as many radvd servers into your mesh and announce as many IPv6 prefixes as you like. Actually - you don't even need a radvd server, since any IPv6 node will autogenerate a unique link-local address!
Since batman-adv will make the mesh a big link-local collision domain, enabling IPv6 on your nodes is all you need. However, you still need a unique and known identifier for each node. This could be any unique name which is announced via mdns.
You need to set a unique identifier if you want to keep an overview of which node is where and in order to address a node in case you want to talk to it, though.
In a up-to-254 node network the last octet of a IPv4 address in a class C network satisfies this requirement for me. That is more intuitive for me than remembering MAC addresses and the deriative IPv6 link-local addresses ;)
This is not entirely zero-conf but helps me to keep a overview of what is going on.
Cheers,
Elektra
--
Viral meme of radical freedom
The fact that you talk in your head doesn't mean that you think.
The best way to lose control over yourself is 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