After reading the docs on Sessions, I have several questions that I
don't believe were directly addressed:
1) Let's say I have two session policies:
[policy_auser]
uid = auser
AllowedBearers = wifi
[policy_buser]
uid = buser
AllowedBearers = cellular
At a given point, the WiFi service is "online" and the "auser" is
connected. The "buser" application chooses to "connect". What will be
the outcome? Will ConnMan disconnect WiFi and connect the cellular
service so "buser" can access the cellular network? Will the "buser"
be informed that a connection cannot be made? Will ConnMan establish
two connections in parallel so that both users are connected to the
network ("auser" over WiFi, "buser" over cellular)? If only one
session can be connected (e.g. they don't have a common bearer), who
takes priority? Is it solely based on the priority field in the
session policy file?
2) Not directly session related, but what triggers the service state
to become "online". The documentation indicates that when the
Internet connection is available and "verified" it will be marked as
"online". What criteria has to be met in order to be declared
"verified"?
3) Is there ever a scenario where two services can be declared
"online" at the same time? If possible, who owns the default route if
gateway information is available?
Fundamentally, I'm trying to understand whether it's possible, under
ConnMan, to have more than one active/configured interface/service
available which applications can use to reach the Internet. Perhaps
application "A" is designed to work over WiFi only while application
"B" works over a cellular connection. If both interfaces/services are
up/ready, could these applications reach the Internet simultaneously?
Is this a use-case ConnMan was designed for? Is it a use-case that is
planned to be supported?
Thanks,
Glenn
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
