On Thu, 2016-02-25 at 09:25 +0000, Lamsoge, Abhijit wrote:
I have a few queries regarding connman's configuration file.
I am trying to configure connman as access point using tether
But What I want to do is change the range of IP-Address's for the
clients connecting it.
I mentioned some options in wifi.config file dumped
TetheringTechnologies = wifi
Now how do I mention a DHCP IP address range in this.
As far as options in the config-format.txt is concerned, I believe, in
wifi context it talks about STAtion role and not AP/Tether mode.
Let me know how to specify IP-Address Pool for DHCP server for wifi AP
The IP range to use for DHCP cannot be configured. ConnMan picks an
unused /24 subnet and starts a DHCP server there. If that subnet or
parts thereof suddenly appear on a uplink connection, tethering will be
restarted which causes another /24 subnet to be selected that does not
conflict with any of the uplink ones.
Deciding in the configuration file which subnet to use for tethering
introduces an interesting problem. What will now happen when the
tethered subnet starts to conflict with the uplink prefix? Half the
people will argue that the uplink connection is more important, while
the other half will argue that the tethered subnet prefix must not
change. Moreover, how is an unsuspecting user that belongs to neither
camp informed why either the uplink connection won't work or why the
subnet used for tethering won't stay the same all the time when all he
did was to (unnecessarily) pick an IPv4 subnet for tethering?
Anyway, as we're dealing with IPv4, DHCP is the only decent option
handing out IPv4 adresses used for connecting to remote systems. The
other option is not IPv4 link local addresses, as by definition they are
not routable outside of the subnetwork. Therefore the question really is
why ConnMan should ever think about allowing the user to nail down a
certain block of private IPv4 addresses to use, as it is a promise that
cannot be kept all times.