On 10/19/2015 09:55 AM, Patrik Flykt wrote:
A captive portal is easier to implement by setting a NAT rule that
redirects incoming connections to a desired port on the local x.x.x.1
tethering interface. Once the captive portal stuff is cleared out, the
redirecting NAT rule for that host can be modified not to capture
connections. It's much simpler than having to rewrite DNS replies from
ConnMan. Your patch enforces captive portal implementation for each and
every device all the time, for sure other use cases include letting
hosts through that have completed the steps enforced by the captive
portal.
Hi,
This solution was the first I implemented (no need to modify connman
source code).
The problem is that in your case, DNS requests are answered by a remote
DNS server. However, as I said, the tethering mode here is in fact a «
hotspot » mode, i.e. we don't have internet connection on the other end.
So your solution will work if we want to access device via any IP
address (for exemple http://1.2.3.4) but not via a DNS request (for
example http://device.config or even http://www.google.fr), which is
much more practical.
Alexandre
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
