Hi again,
Ok, I found this bug XWALK-2060, and followed its instructions to:
Add proxy Environment in /usr/lib/systemd/user/xwalk.service :
Environment=http_proxy=http://your_proxy_address:port/
Environment=https_proxy=https://your_proxy_address:port/
This worked, but for the life of me I can't figure out why it won't work as it
did when I set the proxy from /etc/profile, or even now as it is set in connman.
Hope this helps someone.
Mike
________________________________________
From: Dev [[email protected]] on behalf of Michael Johnson
[[email protected]]
Sent: 06 November 2014 2:37 PM
To: Carsten Haitzler; Thiago Macieira
Cc: [email protected]
Subject: Re: [Dev] Nameserver in connmanctl
Hi all,
Thank you for your comments. I didn't realize that /etc/resolv.conf was not
being used anymore, and I don't think many people do. Geoffroy was correct in
that if I set the DNS IPs in that file manually, it gets overwritten after a
reboot with the default below. However, if connman generates the resolv.conf
file, shouldn't it show the nameservers after they are set, especially if some
applications read that file?
Anyhow, I've set the proxy and nameservers (both using connmanctl, and with the
test scripts in /usr/lib/connman/test), but I can't open a page to
www.google.com, even after a reboot. I get connection refused. So I'm still
working on it.
I'm curious though, what would happen if I moved from a network using a proxy,
to one that doesn't, and what if the DNS changes from the ones I've set up
using connman?
So I probably don't need to file a bug, but I do need to get
xwalk-launcher http://www.google.com
working.
Regards
Mike
MICHAEL JOHNSON
Embedded Software Engineer
Symphony Teleca
Sunley House, 46 Jewry Street, Winchester, Hampshire, SO23 8RY
Phone: +441962868866, Fax: +441962868867
mailto:[email protected]
http://www.symphonyteleca.com
Teleca Limited, a company registered in England & Wales, registration number
2773878, registered office at Sunley House, 46 Jewry Street, Winchester,
Hampshire SO23 8RY. VAT registration number GB 674 6583 90
Follow what's going on at Symphony Teleca's blog on
http://www.symphonyteleca.com/blog. Please consider the environment before you
print.
Notice to recipient: This e-mail (including any attachments) is meant for the
intended recipient only, may contain confidential and proprietary information,
and is protected by law. If you received this e-mail in error, please
immediately notify the sender of the error by return e-mail, delete this
communication and any attachments, and shred any printouts. Unauthorized
review, use, dissemination, distribution, copying or taking of any action based
on this communication is strictly prohibited.
________________________________________
From: Dev [[email protected]] on behalf of Carsten Haitzler
[[email protected]]
Sent: 06 November 2014 12:19 AM
To: Thiago Macieira
Cc: [email protected]
Subject: Re: [Dev] Nameserver in connmanctl
On Wed, 05 Nov 2014 15:36:46 -0800 Thiago Macieira <[email protected]>
said:
> On Wednesday 05 November 2014 16:40:13 Michael Johnson wrote:
> > Hi All,
> >
> > I'm just checking if setting the nameservers with connamnctl does work on
> > tizen. The command I'm using is:
> >
> > connmanctl config <myservice> --nameservers <mydns>
> >
> > but I'm not getting a change in the file /etc/resolv.conf which has:
> >
> > #Generated by Connection Manager
> > nameserver 127.0.0.1
> > nameserver ::1
>
> That's the expected behaviour. Connman is the caching name server for local
> applications and it will forward the requests to the name servers you
> specified in the command above. You won't need nscd.
>
> This is the right way to do it, as opposed to changing /etc/resolv.conf like
> other systems do. With the old style, applications need to monitor
> /etc/resolv.conf for changes and call res_init() if it changed (per-thread!).
and i am not so sure everyone realizes just how majorly this kind of thing
sucks. connman is definitely doing it right not just for itself but for
everyone else involved.
--
Carsten Haitzler (The Rasterman) <[email protected]>
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
