On 05/08/2013 12:52 AM, Patrik Flykt wrote:
On Tue, 2013-05-07 at 08:04 -0700, Gary Oliver wrote:
1) Have a way for the dnsproxy in connman to search (as a
last-resort)
the contents of /etc/hosts, which will be populated with a domain
name
that will be used to connect by the clients to the devic
On 07/05/13 16:04, Gary Oliver wrote:
> 2) Write a plugin that will always respond with the AP address for
> 'localhost' when a DNS request is made.
That sounds wrong... 'localhost' should always resolve to point back to
the machine making the request (127.0.0.1 and/or ::1), not to a distinct
mach
On Tue, 2013-05-07 at 08:04 -0700, Gary Oliver wrote:
> 1) Have a way for the dnsproxy in connman to search (as a
> last-resort)
> the contents of /etc/hosts, which will be populated with a domain
> name
> that will be used to connect by the clients to the device.
If the use case really is an "i
Hi Gary,
On 07.05.2013 18:04, Gary Oliver wrote:
I have a need for a different DNS mechanism than is currently provided
by connman. I'm using 1.13 which I've added to the v2012.12 Angstrom
distribution I'm using for my application (1.4 was missing a few
features I needed.) The device running c
I have a need for a different DNS mechanism than is currently provided
by connman. I'm using 1.13 which I've added to the v2012.12 Angstrom
distribution I'm using for my application (1.4 was missing a few
features I needed.) The device running connman will spend *most* of
it's time as an isol
