On 10/19/2015 11:40 AM, Patrik Flykt wrote:
I was thinking of any connection going to e.g. port 80 would be forced
to the locally used x.x.x.1 address on the tether interface. Like an
automatic proxy solution. This can then be refined to work only for a
subset of hosts, by looking up e.g. www.goo
On 10/16/2015 07:52 AM, Craig McQueen wrote:
I'm interested in this concept. I applied your patch to ConnMan 1.30, and I've
been testing it.
In my testing with DNS queries using the Linux 'dig' utility, I found it returns
malformed responses. That is because the 'dig' query includes an additio
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 mod
devices without failures.
Thanks for your reviews,
--
Alexandre Chataignon
>From b3d28e448b43c84b5fb4dd56a6384790ad4e498c Mon Sep 17 00:00:00 2001
From: Alexandre Chataignon
Date: Tue, 28 Jul 2015 12:05:16 +0200
Subject: [PATCH] Added captive portal possibility
---
src/connman.h|
