[Olsr-users] Client management in olsrd
Fri Oct 16 11:34:19 CEST 2009
Am Thu October 15 2009 15:55:07 schrieb (spam-protected):
> Dear all
> I have just started to use olsrd application. Since last two months, I
> have tried to implemented a plugin related to client management in
> mesh network by using HNA message.In my platform, I have separated
> network in two domains. First is mesh backbone where AP connected each
> other and running olsrd application. Another domain is client network
> where laptops can access to the network by associating with one of
> APs. In my objective, I want APs can update the current location of
> client by using HNA message. For example, when client_1 join to AP_A,
> AP_A will put the address of client_1 to HNA message and broadcast to
> all APs.
> ****** ******
> *AP_A* *AP_C*
> ****** ******
> Currently I use netlink socket to detect when clients are associated
> to AP.Of course, I can put the client information to HNA msg and
> update in routing table of neighbor APs. However, now I am facing some
> problems about updating the routing table. For example when client_1
> moved to associate with AP_C. AP_B and C still keep old information
> between client_1 and AP_a. Therefore, I would like to request some
> information, how can I update the routing table of neighbor AP or
> delete the routing entry of previous connection. Thank you very much
> for your consideration.
Each OLSR instance sets it's own HNA entries, so other OLSR nodes
cannot/should not influence this routing entry directly.
But you could some kind of signaling between your plugins so that the new
connected OLSR plugin can tell the old ones to drop their HNA setting. If you
set the HNA frequency high enough this should help to solve your problem I
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Neuenahrer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-263, Fax +49 228 9435 685
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: This is a digitally signed message part.
More information about the Olsr-users