Hi Marcel and Samuel,

I plan to update the current private network implementation to be able
to request multiple private network.
I noticed that using fd as key of hash table is not a good idea:)
I would like to have your opinion about the best way to do it.

Here is my scenario:

When an application needs a private network, it should request it in
passing an UId in argument.
Thus ConnMan can add the private network settings in a hash table and
use the UId as the key.
Then, when the application doesn't need it anymore it just has to pass
the UId to the release API and ConnMan just has to remove the entry into
the hash table.

Concerning the IP addresses for peer and server, should we determine a
maximum of number of private network available like 10?
We would have 10 tun interfaces with 10 different IP addresses for
server and 10 for the peer?
Those private network settings would be stored in a static array of
struct connman_private_network{}.

Do you have a better solution? As I mentionned to Samuel previously, I
am quite new in ConnMan:)

Thanks a lot for your help.

Kind regards,
Guillaume

_______________________________________________
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman

Reply via email to