crash report (P2P related?)

2015-02-10 Thread Jussi Kukkonen
Hi, I'm not sure when the below abort happened, but I had been testing P2P earlier and found connman like this when I resumed from suspend. Connman was pulled on Jan 26 (499a424d), supplicant is a couple of weeks older. HTH, Jussi connmand[8129]: p2p-wlan0-3 {newlink} index 12 address

Re: [PATCH 2/3] network: fix eternal associating/connecting with IPv6-only

2015-02-10 Thread Patrik Flykt
Hi, On Mon, 2015-02-09 at 10:40 +0200, pasi.sjoh...@jolla.com wrote: From: Pasi Sjöholm pasi.sjoh...@jollamobile.com It was possible with IPv6-only networks to have eternal associating/connecting variable set as true, especially when ipv4 configuration method was OFF. ---

Re: [RFC] ofono: Set ipconfig off if indicated that the protocol is not used

2015-02-10 Thread Patrik Flykt
On Mon, 2015-02-09 at 11:45 +0200, Pasi Sjöholm wrote: And by this I mean the two lines below could be removed. :) +if (modem-active) +set_connected(modem); I'll remove those from the patch, thanks! Patrik

Online status

2015-02-10 Thread Thomas Green
When a service transitions from ready to online status, connman makes an http request to ipv[4,6].connman.net/online/status.html. I have been asked if this is a requirement or is there a way to prevent this from happening? Tom ___ connman mailing

Re: Online status

2015-02-10 Thread Marcel Holtmann
Hi Tom, When a service transitions from ready to online status, connman makes an http request to ipv[4,6].connman.net/online/status.html. I have been asked if this is a requirement or is there a way to prevent this from happening? how else would you do it? You need to ensure that you are

Re: Online status

2015-02-10 Thread Sven Schwedas
On 2015-02-10 20:40, Marcel Holtmann wrote: Hi Tom, When a service transitions from ready to online status, connman makes an http request to ipv[4,6].connman.net/online/status.html. I have been asked if this is a requirement or is there a way to prevent this from happening? how else

1.26 dnsproxy's domain removal is incompatible with certain DNS servers' answers

2015-02-10 Thread Hiro Sugawara
1.26 src/dnsproxy.c fails to process (probably CNAME) answers from certain types of external DNS servers, and thus it cannot resolve host-only queries such as www at all or at least correctly depending on the answer content and format. If the default domain list has company.com, it is expected