I have disabled the check, but the IPv6 check worked for a while and now it does not. I get the messages in the journal
:
connmand[262]: Failed to find URL:http://ipv6.connman.net/online/status.html

It is weird. ipv4 always works, but ipv6 worked for a while now it is not working any more.

If I ping it, I get no response. Curl can find both of them:
root@livingrune(rw):~# curl http://ipv4.connman.net/online/status.html
<html>
<head>
</head>
<body>
</body>
</html>
root@livingrune(rw):~# curl http://ipv6.connman.net/online/status.html
<html>
<head>
</head>
<body>
</body>
</html>
ping and wget fail:

root@livingrune(rw):~# wget http://ipv4.connman.net/online/status.html
--2020-09-07 15:28:31--  http://ipv4.connman.net/online/status.html
Resolving ipv4.connman.net (ipv4.connman.net)... 212.227.81.55
Connecting to ipv4.connman.net (ipv4.connman.net)|212.227.81.55|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 45 [text/html]
Saving to: ‘status.html.2’

status.html.2                 100%[=================================================>]      45  --.-KB/s    in 0s

2020-09-07 15:28:31 (652 KB/s) - ‘status.html.2’ saved [45/45]

root@livingrune(rw):~# wget http://ipv6.connman.net/online/status.html
--2020-09-07 15:28:37--  http://ipv6.connman.net/online/status.html
Resolving ipv6.connman.net (ipv6.connman.net)... 2001:8d8:8b4:c861:5826:fa5f:6690:0, 87.106.208.187
Connecting to ipv6.connman.net (ipv6.connman.net)|2001:8d8:8b4:c861:5826:fa5f:6690:0|:80... ^C

root@livingrune(rw):~# ping ipv4.connman.net
PING ipv4.connman.net (212.227.81.55) 56(84) bytes of data.
64 bytes from ipv4.connman.net (212.227.81.55): icmp_seq=1 ttl=54 time=119 ms
64 bytes from ipv4.connman.net (212.227.81.55): icmp_seq=2 ttl=54 time=121 ms
64 bytes from ipv4.connman.net (212.227.81.55): icmp_seq=3 ttl=54 time=121 ms
^C
--- ipv4.connman.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2010ms
rtt min/avg/max/mdev = 119.466/120.308/120.770/0.596 ms
root@livingrune(rw):~# ping -6 ipv6.connman.net
PING ipv6.connman.net(connman.com (2001:8d8:8b4:c861:5826:fa5f:6690:0)) 56 data bytes
^C
--- ipv6.connman.net ping statistics ---
17 packets transmitted, 0 received, 100% packet loss, time 16660ms

dig seens to be able to find both the ipv4 and ipv6 records:
root@livingrune(rw):~# dig ipv6.connman.net A

; <<>> DiG 9.16.6 <<>> ipv6.connman.net A
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20959
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ipv6.connman.net.              IN      A

;; ANSWER SECTION:
ipv6.connman.net.       7       IN      A       87.106.208.187

;; Query time: 0 msec
;; SERVER: 192.168.2.3#53(192.168.2.3)
;; WHEN: Mon Sep 07 15:32:39 CDT 2020
;; MSG SIZE  rcvd: 61

root@livingrune(rw):~# dig ipv6.connman.net AAAA

; <<>> DiG 9.16.6 <<>> ipv6.connman.net AAAA
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44189
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ipv6.connman.net.              IN      AAAA

;; ANSWER SECTION:
ipv6.connman.net.       12      IN      AAAA    2001:8d8:8b4:c861:5826:fa5f:6690:0

;; Query time: 0 msec
;; SERVER: 192.168.2.3#53(192.168.2.3)
;; WHEN: Mon Sep 07 15:32:43 CDT 2020
;; MSG SIZE  rcvd: 73

I do not know what is going on as this is way out of my depth, but it seems like something is not set quite right on the server end.




On Thu, Jul 30, 2020 at 12:58 AM Daniel Wagner <wagi@monom.org> wrote:
Hi,

On Wed, Jul 29, 2020 at 12:15:36PM -0400, Michael Sweet wrote:
> FWIW, my local testing configuration has the online checking disabled,
> since none of the AirPrint code needs it and it might potentially
> interfere with the BCT tests...

If you don't need rely on ConnMan reporting the ONLINE state, it's
properly better to disable online test. The online test has one big draw
back, it's a one shot. That means there is never a ONLINE -> READY state
transition. We cannot add this at this point as it would be a big API
break. One way to fix this, is to add a feature to disable if needed.

> > Thanks for forwarding this, This seems to have been fixed in the last couple days. I still find it strange that the ipv6.connman.net has an ipv6 *and* an ipv4 address.
> > Name:   ipv6.connman.net
> > Address: 87.106.208.187
> > Name:   ipv6.connman.net
> > Address: 2001:8d8:8b4:c861:5826:fa5f:6690:0

TBH, I don't know the server side code. But I suspect it just returns all
addresses for the interface it receives the request.

> > Regardless, I no longer get the:
> > connmand[267]: Failed to find
> > URL:http://ipv6.connman.net/online/status.html

I can't really debug this, currently no IPv6 setup here. IIRC, the was a
complaint on the mailing list about this. Maybe the server is not
working anymore. I'll ask Marcel (he runs the servers) if he could check
if all is up and running.

> > in my logs and we will see if it has any effect on the reconnection
> > and 'online' testing that connman does.

If you don't need the ONLINE state, I suggest to disable the online
check feature.

Thanks,
Daniel