On Wed, 2015-02-04 at 17:11 +0200, Tomasz Bursztyka wrote:
> No, afaik you need to disable dnsproxy. Or then you will end up with:
>
> dnsproxy configured to use 127.0.0.53 as nameserver, and resolv.conf
> with 127.0.0.1 as nameserver. Duplicated local dns cache/forwarder.
>
> If dnsproxy is disa
On Wed, 2015-02-04 at 16:20 +0100, Martin Tournoij wrote:
> It's not magic :-) But it queries the root server, then .com from
> that, and then example.com from that, insofar as I understand DNS. Or
> maybe I misunderstood something?
>
> I have no lines with forward-zone in /etc/unbound/unbound.con
Hi All,
I am trying to understand the call flow sequence when we try to do a
connection using connman connect service. I see the below logs.
connmand[2769]: src/network.c:connman_network_get_bool() network 0x2cbde138
key WiFi.UseWPS
connmand[2769]: src/network.c:connman_network_get_string() netwo
On Wed, Feb 4, 2015, at 16:06, Jukka Rissanen wrote:
> You might be able to configure connman to use your 127.0.0.53 server by
> configuring it to each service you are using (have not tested this
> thou). Example: connmanctl config your_service_id --nameservers
> 127.0.0.53
> and then running connm
On Wed, Feb 4, 2015, at 16:06, Tomasz Bursztyka wrote:
> Hi,
>
> > It makes sense to me to
> > not use every random DNS server out there...
>
> Sure, but your ubound does not magically resolve names by itself: it
> does forward the
> DNS queries to whatever has been configured (check
> /etc/unb
Hi,
You might be able to configure connman to use your 127.0.0.53 server by
configuring it to each service you are using (have not tested this
thou). Example: connmanctl config your_service_id --nameservers
127.0.0.53
and then running connman with dnsproxy enabled.
No, afaik you need to disabl
On ke, 2015-02-04 at 15:53 +0100, Martin Tournoij wrote:
> On Wed, Feb 4, 2015, at 15:41, Jukka Rissanen wrote:
> > Just wondering where do you get the nameserver IP addresses in this
> > case? Are you manually updating resolv.conf?
>
> Not sure if I understand this question?
I mean where does un
Hi,
It makes sense to me to
not use every random DNS server out there...
Sure, but your ubound does not magically resolve names by itself: it
does forward the
DNS queries to whatever has been configured (check
/etc/unbound/unbound.conf keyword "forward-zone")
and cache the results relevantl
On Wed, Feb 4, 2015, at 15:41, Jukka Rissanen wrote:
> Just wondering where do you get the nameserver IP addresses in this
> case? Are you manually updating resolv.conf?
Not sure if I understand this question?
Let me explain my setup in more detail:
- Run unbound on 127.0.0.54
- Run adsuck on 1
Hi Martin,
On ke, 2015-02-04 at 15:34 +0100, Martin Tournoij wrote:
> On Wed, Feb 4, 2015, at 15:28, Patrik Flykt wrote:
> >
> > Hi,
> >
> > On Wed, 2015-02-04 at 15:23 +0100, Martin Tournoij wrote:
> > > > How do you pick up the DNS servers when changing networks if ConnMan
> > > > never wr
On Wed, Feb 4, 2015, at 15:28, Patrik Flykt wrote:
> So if you do a lookup for 'slashdot.org', how is unbound configured to
> properly resolve that name from any network you visit? Google?
If you wanted to, you could still get the DNS servers the DHCP dishes
out with:
$ connmanctl services wifi
On Wed, Feb 4, 2015, at 15:28, Patrik Flykt wrote:
>
> Hi,
>
> On Wed, 2015-02-04 at 15:23 +0100, Martin Tournoij wrote:
> > > How do you pick up the DNS servers when changing networks if ConnMan
> > > never writes the ones obtained via DHCP anywhere? How do you update
> > the
> > > DNS ser
Hi,
On Wed, 2015-02-04 at 15:23 +0100, Martin Tournoij wrote:
> > How do you pick up the DNS servers when changing networks if ConnMan
> > never writes the ones obtained via DHCP anywhere? How do you update
> the
> > DNS servers at the moment when using your own resolver?
>
> I don't. I
On Wed, Feb 4, 2015, at 14:59, Patrik Flykt wrote:
> On Tue, 2015-01-06 at 05:01 +0100, Martin Tournoij wrote:
> > This is useful because my laptop runs it's own resolver. Every time I
> > connect, Connman overwrites /etc/resolv.conf, and I need to script
> > around this by overwriting it again aft
On Tue, 2015-01-06 at 05:01 +0100, Martin Tournoij wrote:
> This is useful because my laptop runs it's own resolver. Every time I
> connect, Connman overwrites /etc/resolv.conf, and I need to script
> around this by overwriting it again after this...
How do you pick up the DNS servers when changin
On Fri, 2015-01-30 at 09:14 +, Priyaranjan Singh wrote:
> But as I understood from you, priority ordering is decided by:
There is a case zero, which in normal circumstances doesn't even try to
autoconnect if there already is a connected service. This happens when
PreferredTechnologies is unset
Hi,
Is there any response on this?
I don't want to badger anyone, but I'm subscribed to the connman mail
list just for this issue. It would like to give my INBOX a break ;-)
Thanks a lot!
Martin
___
connman mailing list
connman@connman.net
https://list
Hello All,
Call to MoveBefore/MoveAfter is not changing the default gateway where service
moved to top is in ready state.
Point I want to highlight is the outcome of moveBefore/moveAfter (outcome of
step 5):
1. Wifi is not becoming default gateway
2. Drop in connection status from
18 matches
Mail list logo
