[Olsr-dev] Client Roaming Plugin

marc fawzi (spam-protected)
Fri Jan 22 20:51:22 CET 2010

Sorry to mess up the conversation between Markus and Raphael's but Raphael's
response came in just as I was sending my response to Markus regarding
scenarios A thru D in his previous message.

I just wanted to say that if the approach you guys are working on with
Raphael gives any wifi client (no ad-hoc, no olsrd) the ability to switch
between accesspoints without losing VoIP connection (as Raphael was
suggesting in his initial email) then that would be all I'm looking for,
assuming it could work in case of VoIP.


On Fri, Jan 22, 2010 at 11:39 AM, Raphael <(spam-protected)> wrote:

> Good Evening
> > henning
> > found a very simple one, which will work nearly as well,..
> > just send one (or maybe 2-3) hnas #1 with the minimal valid validity time
> (~
> > 1/16 second) at the old master (as soon as he knows he is the old master
> > (probably because he received a hna-message from the new master))
> > this will update (the validity time) and in fact delete the old hna entry
> > quite fast in the whole mesh
> This sounds like a good approach to me.
> > On Wed, Jan 20, 2010 at 10:49 PM, Raphael <(spam-protected)> wrote:
> >>
> >> Hi everybody
> >>
> >> I still have some issues with the update on routes because the nodes
> >> do not communicate directly.
> >>
> >> I need help with adding new olsrd messages so that changing routes is
> >> fast enough to maintain voip-connections.
> >
> > beside the hnas to announce(and "delete") the client
> > i think you need an additional message type, to announce the mac of the
> > client, so that new new master will (be able to identify) and use the
> same
> > ip for its hna as the old one,
> > (or you calculate the ip from the mac-address)
> Right, I have already defined a structure for this type of messages
> but I can't get olsrd to transmit this struct.
> I currently simply merge the client's lease-files to spead news about
> new IPs and MACs.
> > -> but it might be better to start with a simple approach to find out how
> > many loops will actually happen *G
> I would be glad if I could test my implementation, to see if there are
> design flaws or something similar.
> There were some concerns if we need an extra real interface or VAP is
> enough. I use a VAP-interface. Basically every atheros-wifi-based
> router should be capable of this.
> Feel free to look at the current source at
> http://github.com/ralisi/olsrd_cl_roam but please be gentle because it
> is the first time other people look at my program-code.
> Raphael
> --
> Olsr-dev mailing list
> (spam-protected)
> http://lists.olsr.org/mailman/listinfo/olsr-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100122/b1422bbe/attachment.html>

More information about the Olsr-dev mailing list