David,

I think there is some mis-configuration with something at the server/registration. Shouldn't it only have an ipv6 addres? ipv6.google.com does.

If this is a regular test of link functionality at service start, shouldn't it be disable-able? How do I do that?

# host ipv6.google.com
ipv6.google.com is an alias for ipv6.l.google.com.
ipv6.l.google.com has IPv6 address 2607:f8b0:4009:810::200e

# nslookup ipv6.google.com
Server:         192.168.2.1
Address:        192.168.2.1#53

Non-authoritative answer:
ipv6.google.com canonical name = ipv6.l.google.com.
Name:   ipv6.l.google.com
Address: 2607:f8b0:4009:810::200e

Versus:

# host ipv6.connman.net
ipv6.connman.net has address 87.106.208.187
ipv6.connman.net has IPv6 address 2001:8d8:8b4:c861:5826:fa5f:6690:0

# nslookup ipv6.connman.net
Server:         192.168.2.1
Address:        192.168.2.1#53

Non-authoritative answer:
Name:   ipv6.connman.net
Address: 87.106.208.187
Name:   ipv6.connman.net
Address: 2001:8d8:8b4:c861:5826:fa5f:6690:0

I cannot ping it.
# ping 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 ---
4 packets transmitted, 0 received, 100% packet loss, time 88ms

but can its ipv4 address...
# ping -4 ipv6.connman.net
PING ipv6.connman.net (87.106.208.187) 56(84) bytes of data.
64 bytes from senator.holtmann.net (87.106.208.187): icmp_seq=1 ttl=43 time=126 ms
64 bytes from senator.holtmann.net (87.106.208.187): icmp_seq=2 ttl=43 time=125 ms
64 bytes from senator.holtmann.net (87.106.208.187): icmp_seq=3 ttl=43 time=125 ms
^C
--- ipv6.connman.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 3ms
rtt min/avg/max/mdev = 124.676/125.263/126.122/0.684 ms

pinging ipv6 does work...
# ping ipv6.google.com
PING ipv6.google.com(ord30s31-in-x0e.1e100.net (2607:f8b0:4009:801::200e)) 56 data bytes
64 bytes from ord30s31-in-x0e.1e100.net (2607:f8b0:4009:801::200e): icmp_seq=1 ttl=54 time=20.6 ms
64 bytes from ord30s31-in-x0e.1e100.net (2607:f8b0:4009:801::200e): icmp_seq=2 ttl=54 time=12.3 ms
^C
--- ipv6.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 5ms
rtt min/avg/max/mdev = 12.262/16.431/20.600/4.169 ms

On Thu, Jun 4, 2020 at 8:50 AM David Woodhouse <dwmw2@infradead.org> wrote:
On Wed, 2020-05-27 at 15:12 -0500, KeithG wrote:
> DOn't know if this is the right place or not, but since moving to
> connman, I have noticed that the ipv6 test page is down. the ipv4 one
> works fine, but I get a mention in the log:
> "connmand[254]: Failed to find URL:
> http://ipv6.connman.net/online/status.html"
>
> If I try to get to it from a browser, I get a '502 bad gateway error'
>
> If I use curl on the cli, I get this:
> # curl ipv4.connman.net/online/status.html
> <html>
> <head>
> </head>
> <body>
> </body>
> </html>
> # curl ipv6.connman.net/online/status.html
> <html>
> <head><title>502 Bad Gateway</title></head>
> <body bgcolor="white">
> <center><h1>502 Bad Gateway</h1></center>
> <hr><center>nginx</center>
> </body>
> </html>
>
> I think something is not set right on the server...

Amusingly it works for me but only over Legacy IP.

$ curl -v http://ipv6.connman.net/online/status.html
*   Trying 2001:8d8:8b4:c861:5826:fa5f:6690:0:80...
*   Trying 87.106.208.187:80...
* Connected to ipv6.connman.net (87.106.208.187) port 80 (#0)
> GET /online/status.html HTTP/1.1
> Host: ipv6.connman.net
> User-Agent: curl/7.69.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx
< Date: Thu, 04 Jun 2020 13:48:57 GMT
< Content-Type: text/html
< Connection: close
< X-ConnMan-Status: online
<
<html>
<head>
</head>
<body>
</body>
</html>
* Closing connection 0