Tuesday, December 22, 2015

IPv6 in NL per 9th December 2015



The IPv6 percentages of the Netherlands ISPs as of December 9, 2015:

XS4ALL 58.10%
KPN 5.52%
ZeelandNet 4.51%
Solcon 4.22%
Ziggo 0.32%
UNET 0.22%

Xs4all has risen 5% in only 2 months (http://ipv6-or-no-ipv6.blogspot.nl/2015/11/kpn-is-now-above-5-ipv6-deployment.html) ... impressive! Oh, wait ... Xs4all's measurement is going up and down:




Source: http://www.worldipv6launch.org/measurements/


Monday, November 2, 2015

KPN is now above 5% IPv6 deployment

KPN is now (October 2015) above 5% IPv6 deployment. Not much IPv6 development on Ziggo's side.


$ lynx --dump "http://www.worldipv6launch.org/apps/ipv6week/measurement/timeline-nets.html" | egrep -i -e "kpn|ziggo|xs4all|solcon|telfort|upc|zeeland|caiw" | awk '{ print $2 " " $NF }' | sort -u -k2,2 -r

XS4ALL 53.91%
KPN 5.13%
Solcon 3.94%
ZeelandNet 3.77%
Ziggo 0.24%




XS4ALL 53.91%
KPN 5.13%
Solcon 3.94%
ZeelandNet 3.77%
Ziggo 0.24%

Friday, September 25, 2015

Newsservers with IPv6

I'm quite impressed by the amount of newsservers with IPv6 on port 563 or 119:

news.alibis.com has IPv6 2001:4de0:401:7::146 with succesful connect on port 563
news.atlantisnews.com has IPv6 2001:4de0:401:7::147 with succesful connect on port 563
news.bulknews.eu has IPv6 2a02:d28:10:1c:0:407:ff02:164 with succesful connect on port 563
news.cheapnews.eu has IPv6 2a02:d28:10:1b:0:431:ff02:164 with succesful connect on port 563
block.cheapnews.eu has IPv6 2a02:d28:10:1b:0:431:ff02:165 with succesful connect on port 563
news.easynews.com has IPv6 2001:4de0:401:7::170 with succesful connect on port 119
news.iload-usenet.com has IPv6 2001:4de0:1::222 with succesful connect on port 119
news.newsdemon.com has IPv6 2001:4de0:401:7::146 with succesful connect on port 563
eu.newsdemon.com has IPv6 2001:4de0:401:7::147 with succesful connect on port 563
us.newsdemon.com has IPv6 2001:4de0:2101:119e::23 with succesful connect on port 119
eu.newsgroup-binaries.com has IPv6 2001:4de0:1::236 with succesful connect on port 119
secure.newsgroup-binaries.com has IPv6 2001:4de0:2101:119e::22 with succesful connect on port 563
news.newsgroupdirect.com has IPv6 2001:4de0:401:7::147 with succesful connect on port 563
us.newsgroupdirect.com has IPv6 2001:4de0:2101:119e::23 with succesful connect on port 563
news.panic.com has IPv6 2001:4de0:401:7::146 with succesful connect on port 563
news.prepaid-usenet.de has IPv6 2001:4de0:1::236 with succesful connect on port 119
news.redorbnews.com has IPv6 2001:4de0:2101:119e::20 with succesful connect on port 119
eu.redorbnews.com has IPv6 2001:4de0:1::236 with succesful connect on port 119
news.shemes.com has IPv6 2001:4de0:1::222 with succesful connect on port 119
news.simonews.com has IPv6 2001:4de0:1::222 with succesful connect on port 119
reader.snelnl.com has IPv6 2001:4de0:401:7::147 with succesful connect on port 563
news.snelnl.com has IPv6 2001:4de0:1::236 with succesful connect on port 119
secure.thenewsgroups.com has IPv6 2001:4de0:2101:119e::22 with succesful connect on port 563
news.thundernews.com has IPv6 2001:4de0:401:7::146 with succesful connect on port 563
eu.thundernews.com has IPv6 2001:4de0:401:7::146 with succesful connect on port 563
us.thundernews.com has IPv6 2001:4de0:2101:119e::22 with succesful connect on port 563
secure.eu.thundernews.com has IPv6 2001:4de0:401:7::146 with succesful connect on port 563
secure.us.thundernews.com has IPv6 2001:4de0:2101:119e::23 with succesful connect on port 119
news.tigerusenet.com has IPv6 2001:4de0:2101:119e::23 with succesful connect on port 563
news.usenetnewsserver.com has IPv6 2001:4de0:401:7::146 with succesful connect on port 563
news.xlusenet.nl has IPv6 2001:4de0:1::222 with succesful connect on port 119
secure.xlusenet.nl has IPv6 2001:4de0:401:7::147 with succesful connect on port 563
news.xs4all.nl has IPv6 2001:888:0:4::119 with succesful connect on port 119
eu.z51.biz has IPv6 2001:4de0:1::236 with succesful connect on port 119


So ... domains with functional newsservers on ipv6:

alibis.com
atlantisnews.com
bulknews.eu
cheapnews.eu
easynews.com
iload-usenet.com
newsdemon.com
newsgroup-binaries.com
newsgroupdirect.com
panic.com
prepaid-usenet.de
redorbnews.com
shemes.com
simonews.com
snelnl.com
thenewsgroups.com
thundernews.com
tigerusenet.com
usenetnewsserver.com
xlusenet.nl
xs4all.nl
z51.biz




Thursday, September 24, 2015

KPN op 4,65% IPv6 deployment


Zo, mooie score van KPN: op 4,65% IPv6 deployment (meting september 2015). En "deployment" betekent hier daadwerkelijk gebruik, dus tot op computer/tablet die het daadwerkelijk gebruikt.

KPN had in april 2015 (5 maanden geleden) nog geen IPv6 deployment (tenminste: blijkbaar minder dan 0.00%). Zie http://ipv6-or-no-ipv6.blogspot.nl/2015/04/ipv6-deployment-by-isps-in-netherlands.html





Ziggo zit op 0,17%, dus dat schiet niet op.

One-liner om de gegevens te achterhalen van http://www.worldipv6launch.org/measurements/

$ lynx --dump "http://www.worldipv6launch.org/apps/ipv6week/measurement/timeline-nets.html" | egrep -i -e "kpn|ziggo|xs4all|solcon|telfort|upc|zeeland" | awk '{ print $2 " " $NF }' | sort -u -k2,2 -r

XS4ALL 53.69%
KPN 4.65%
ZeelandNet 3.71%
Solcon 3.52%
Ziggo 0.17%

Sunday, August 30, 2015

Chrome on Linux does not use teredo IPv6?

What happened? It seems Chrome and Chromium on Linux don't use IPv6 if the IPv6 is provided by teredo / miredo.

Everything works in Firefox, Miredo, lynx, ping6, etc with ipv6.google.com.

It looks like Chromium does not do a IPv6 DNS lookup; if I use a literal IPv6 address, it still works in Chromium.

I'm quite sure it all worked earlier on. Is Chrome/Chromium going the Windows way, so "if teredo, do not lookup IPv6 addresses"?


Saturday, July 11, 2015

Check IPv6 enabled tracker in torrent

Here's an ugly oneliner to see if a torrent has IPv6 enabled trackers in it:

$ strings ubuntu-14.04.2-desktop-amd64.iso.torrent | head -1 | tr '/' '\n' | awk -F: ' $1 ~ /\./ { print "host -t aaaa "  $1 }' | /bin/sh | grep -vi "has no AAAA"

ipv6.torrent.ubuntu.com is an alias for ubuntuv6tracker.bit.nl.
ubuntuv6tracker.bit.nl has IPv6 address 2001:7b8:3:37::21:3

So, yes, this torrent has an IPv6 enabled tracker.

I got this torrent from http://ipv6.torrent.ubuntu.com/, which only works via IPv6.

Openwrt: Allow all incoming IPv6 traffic

I run OpenWrt Barrier Breaker 14.07 on my router. Default it blocks all incoming IPv6 traffic. To accept all incoming IPv6 traffic, I did this:

In the file /etc/firewall.user put this:

ip6tables -F
ip6tables -X
ip6tables -A INPUT -p icmpv6 -j ACCEPT
ip6tables -P INPUT ACCEPT
ip6tables -P OUTPUT ACCEPT
ip6tables -P FORWARD ACCEPT

Saven and exit. Then

/etc/init.d/firewall restart

And that's it! All my IPv6 hosts are open to Internet.

Starting Nmap 6.40 ( http://nmap.org ) at 2015-07-11 12:05 CEST
Nmap scan report for 2001:bad:cafe::1
Host is up (0.0055s latency).
Not shown: 988 closed ports
PORT     STATE    SERVICE
22/tcp   open     ssh
25/tcp   filtered smtp
80/tcp   open     http
139/tcp  open     netbios-ssn
445/tcp  open     microsoft-ds
6666/tcp filtered irc
6667/tcp filtered irc
6668/tcp filtered irc
6669/tcp filtered irc
7000/tcp filtered afs3-fileserver
8080/tcp open     http-proxy
9999/tcp filtered abyss

Nmap done: 1 IP address (1 host up) scanned in 18.02 seconds

As that's a bit too much, I'll now close down the firewall a bit.


Monday, May 11, 2015

IPv6 Newsservers

Based on http://ipv6-or-no-ipv6.blogspot.com/2015/05/newsprovider-xsnews-offers-ipv6-access.html I wrote an oneliner to find out Xsnews resellers that provide IPv6 NNTP access. Oneliner plus result:

$ python lusje.py | awk '{ print "./nntptester.py " $1 }' | /bin/sh  | grep -vi unconfigured | grep -i -B1 -e "^200"


Newsserver is 2001:67c:174:101:0:65:ff02:1
200 Welcome to Usenet2go
--
Newsserver is 2001:67c:174:101:0:65:ff02:121
200 Welcome to Astinews
--
Newsserver is 2001:67c:174:101:0:65:ff02:122
200 Welcome to Newsxs
--
Newsserver is 2001:67c:174:101:0:65:ff02:126
200 Welcome to Bullcat
--
Newsserver is 2001:67c:174:101:0:65:ff02:129
200 Welcome to Unet
--
Newsserver is 2001:67c:174:101:0:65:ff02:131
200 Welcome to XS News
--
Newsserver is 2001:67c:174:101:0:65:ff02:132
200 Welcome to I-Telligent
--
Newsserver is 2001:67c:174:101:0:65:ff02:133
200 Banner Welcome to Aviteo Ltd DE
--
Newsserver is 2001:67c:174:101:0:65:ff02:135
200 Welcome to Its Hosted

Better formatting


To get a better formatting, I fed the above list into another oneliner:

$ cat xsnews-resellers-with-ipv6.txt  | grep -vi "\-\-" | awk ' /Newsserver/ { print $NF } /Welcome/ { print substr($0,4+index($0," to ")) }'  | paste - - -d' '

2001:67c:174:101:0:65:ff02:1 Usenet2go
2001:67c:174:101:0:65:ff02:121 Astinews
2001:67c:174:101:0:65:ff02:122 Newsxs
2001:67c:174:101:0:65:ff02:126 Bullcat
2001:67c:174:101:0:65:ff02:129 Unet
2001:67c:174:101:0:65:ff02:131 XS News
2001:67c:174:101:0:65:ff02:132 I-Telligent
2001:67c:174:101:0:65:ff02:133 Aviteo Ltd DE
2001:67c:174:101:0:65:ff02:135 Its Hosted


So, if you have an account with one of these news providers, you can now access them via IPv6. And if these resellers do not publish a FQDN for their IPv6 newsserver, you can just fill out the IPv6 address in your IPv6 capable newsreader (like SABnzbd)


Newsprovider Xsnews offers IPv6 access

Nice: Newsprovider Xsnews (www.xsnews.com) offers IPv6 access via its news server readeripv6.xsnews.nl.


$ telnet readeripv6.xsnews.nl nntp
Trying 2001:67c:174:101:0:65:ff02:131...
Connected to readeripv6.xsnews.nl.
Escape character is '^]'.
200 Welcome to XS News
quit
205 Bye. 24 bytes written, 0 accounted.
Connection closed by foreign host.

I did a download test, and got line speed (100 Mbps).

Further analysis


readeripv6.xsnews.nl has IPv6 address 2001:67c:174:101:0:65:ff02:131
reader.xsnews.nl has address 94.232.116.131

Note the last "131" ... that is probably the link.

Xsnews is a wholesaler offering its services to resellers. The list on https://vergelijkusenetproviders.nl/usenet-provider-lijst/ shows the resellers of Xsnews.

Aeton XSNews
AstiNews XSNews
Bulknews XSNews
EasyUsenet XSNews
Easynews XSNews
Gebruikhet XSNews
NewsConnection XSNews
NewsGrabber XSNews
NewsXS XSNews
Power News XSNews
SimplyUsenet XSNews
SMSUsenet XSNews
SnelNL XSNews
SSL-News XSNews
Surfino XSNews
Usebits XSNews
Usenet2Go XSNews
Usenet4U XSNews
UsenetBucket XSNews
UsenetXL XSNews
Wondernews XSNews
XsNews XSNews
YabNews XSNews

So let's check Yabnews:
news.yabnews.nl has address 94.232.116.127

So same IP address as reader.xsnews.nl, except the last byte: 127 instead of 131. So let's check the 'corresponding' IPv6:

$ telnet 2001:67c:174:101:0:65:ff02:127 nntp
Trying 2001:67c:174:101:0:65:ff02:127...
Connected to 2001:67c:174:101:0:65:ff02:127.
Escape character is '^]'.
200 Welcome to an unconfigured NNTP server.
quit
205 Bye. 45 bytes written, 0 accounted.
Connection closed by foreign host.

Bingo. Still "unconfigured NNTP server", but probably reserved for Yabnews.

Old free service ... not anymore


FWIW: in the old days, Xsnews offered free access IPv6, but that NNTP server is not providing news services anymore:


$ telnet reader.ipv6.xsnews.nl nntp
Trying 2001:67c:174:101::1337...
Connected to reader.ipv6.xsnews.nl.
Escape character is '^]'.
500 Thank you for testing IPv6. XSNews now offers IPv6 on all packages. Register now at www.xsnews.com
Connection closed by foreign host.

Note the subtle difference: readeripv6.xsnews.nl versus reader.ipv6.xsnews.nl ... so just one dot.






Sunday, April 12, 2015

IPv6 usage by German ISPs

IPv6 usage by German ISPs:

$ ./show-ipv6-usage-sorted-on-percentage.sh | grep -e "^DE"
DE  --- SPEEDPARTNER SpeedPartner GmbH  --- 88.66%
DE  --- DE-DGW FL!NK GmbH  --- 41.94%
DE  --- INTERSCHOLZ-AS interscholz Internet Services GmbH & Co. KG  --- 36.01%
DE  --- DEGNET DegNet GmbH  --- 27.61%
DE  --- DELUNET inexio Informationstechnologie und TelekommunikationKGaA  --- 23.81%
DE  --- DTAG Deutsche Telekom AG  --- 20.12%
DE  --- MWN-AS Leibniz-Rechenzentrum  --- 19.84%
DE  --- KIT Karlsruhe Institute of Technology (KIT)  --- 18.16%
DE  --- BELWUE Landeshochschulnetz Baden-Wuerttemberg (BelWue)  --- 9.66%
DE  --- MANITU manitu GmbH  --- 5.77%
DE  --- IKS IKS Service GmbH  --- 1.12%
DE  --- SCALEUP ScaleUp Technologies GmbH & Co. KG  --- 1.11%
DE  --- FILOO-ASN filoo GmbH Autonomous System  --- 0.19%
DE  --- ADDIX-AS ADDIX Internet Services GmbH  --- 0.10%

ISPs with highest percentage IPv6 usage

ISPs with highest percentage IPv6 usage ... including country code:

SI  --- GO6 Zavod za IPv6 - go6  --- 100.00%
PL  --- ORANGE-PL Orange Polska Spolka Akcyjna  --- 100.00%
US  --- DNIC-AS-00022 - Navy Network Information Center (NNIC)  --- 93.10%
CH  --- SNOWFLAKE snowflake productions gmbh  --- 91.75%
DE  --- SPEEDPARTNER SpeedPartner GmbH  --- 88.66%
MX  --- Centros Culturales de Mexico, A.C.  --- 84.19%
BR  --- FUNDACAO PARQUE TECNOLOGICO ITAIPU - BRASIL  --- 78.68%
US  --- LSU-1 - Louisiana State University  --- 74.27%
IT  --- TOPIX-AS Consorzio Topix - Torino e Piemonte Exchange Point  --- 73.86%
US  --- MARIST - Marist College  --- 68.62%
CZ  --- VUTBR-AS Brno University of Technology  --- 68.49%
BR  --- UNIVERSIDADE ESTADUAL DE PONTA GROSSA  --- 67.97%
US  --- PRGMR - prgmr.com, Inc.  --- 67.92%
US  --- GOOGLE-FIBER - Google Fiber Inc.  --- 65.84%
US  --- CELLCO-PART - Cellco Partnership DBA Verizon Wireless  --- 61.87%
IT  --- FUSOLAB Fusolab Onlus  --- 61.37%
CZ  --- CZNIC-AS CZ.NIC, z.s.p.o.  --- 60.46%
US  --- BUFFALO-ASN - University of Buffalo  --- 60.03%
BE  --- ASBRUTELE Brutele SC  --- 57.78%
US  --- UVM-EDU-AS - University of Vermont  --- 56.84%
SE  --- NETNOD-IX Netnod Internet Exchange Sverige AB  --- 56.68%
NL  --- XS4ALL-NL XS4ALL Internet BV  --- 55.23%
US  --- UPENN - University of Pennsylvania  --- 54.07%
US  --- RPI-AS - Rensselaer Polytechnic Institute  --- 52.94%
BE  --- TELENET-AS Telenet N.V.  --- 52.62%
US  --- VA-TECH-AS - Virginia Polytechnic Institute and State Univ.  --- 52.05%
CH  --- MIRONET-AS MiroNet AG  --- 50.62%

IPv6 deployment by ISPs in the Netherlands

Based on the info on http://www.worldipv6launch.org/apps/ipv6week/measurement/timeline-nets.html I was able to analyze the IPv6 deployment (if any) by ISPs in the Netherlands:


$ ./show-ipv6-usage-per-ISP-for-TLD.sh NL
NL  --- XS4ALL-NL XS4ALL Internet BV  --- 55.23%
NL  --- COMPUKOS-AS DirectVPS B.V.  --- 49.38%
NL  --- AMS-IX1 Amsterdam Internet Exchange B.V.  --- 43.66%
NL  --- PCEXTREME PCextreme B.V.  --- 4.48%
NL  --- ZEELANDNET ZeelandNet BV  --- 4.20%
NL  --- NL-SOLCON SOLCON  --- 3.45%
NL  --- NL-BIT BIT BV  --- 2.94%
NL  --- DUOCAST-AS Duocast B.V.  --- 1.43%
NL  --- SURFNET-NL SURFnet, The Netherlands  --- 1.41%
NL  --- SIGNET-AS Signet B.V.  --- 0.75%
NL  --- OXILION-AS Oxilion B.V.  --- 0.46%

So ... in April 2015 still no KPN, UPC, Ziggo, Tele2, Unet, Caiway ...

Tuesday, April 7, 2015

Dutch cable ISP Ziggo starts IPv6

Good news: Ducth cable ISP "Ziggo" has started the rollout of IPv6. See article (in Dutch) on http://tweakers.net/nieuws/102311/ziggo-begint-met-uitrol-van-ipv6.html

Ziggo spokesperson Gradus Vos confirms the rollout has started last week (around beginning of April 2015), and so far 6.000 users have been assigned IPv6 connectivity.




Netflix and "This webpage has a redirect loop"

Suddenly Netflix was not working anymore: my Chrome on Ubuntu Linux said "This webpage has a redirect loop" on www.netflix.com.

Netflix advised to clear my cookies.

The real cause was different: IPv6, and possibly my Hurricane Electric IPv6 tunnel.

After disabling IPv6 in Chrome with the startup command "google-chrome --disable-ipv6", Netflix was working again.

Great. Not.

EDIT: I found a dirty workaround: I put this into my /etc/hosts

54.197.238.114 www1.netflix.com

... and now a plain google-chrome startup (so with IPv6 enabled) leads to a working Netflix!

EDIT 2:

Thijs Kroesbergen (@TheIceCoMa) reports a Netflix problem with Sixxs IPv6:

https://twitter.com/TheIceCoMan/status/585829217046294528

@NetflixNL IPV6 on the http://netflix.com  site is broken (connection timeout on the first HTTPS request) coming from a SiXXS tunnel.

EDIT 3:

Windows 7 & Chrome on the same LAN (so: with tunneled IPv6) correctly works with Netflix. Strange
Ubuntu & Netflix with Pipelight works too with Netflix



Screenshot of the not-working Netflix:



Tuesday, February 17, 2015

Docker 1.5 and IPv6 on Ubuntu

Docker 1.5 offers IPv6. Here's how I got it working on my Ubuntu VPS.

First of all: my VPS provider (thanks, Philip!) was so friendly to provide & route a separate IPv6 subnet to my VPS, which I used for Docker:

  • Separate subnet provided by my VPS provider: 2001:AAAA:FF00:1700::/56
  • Sub-subnet used for Docker: 2001:AAAA:FF00:1700::/64 


(Note: AAAA is a placeholder for the real hex digits)

First check you have at least docker 1.5:

sander@makreel:~$ sudo docker --version
Docker version 1.5.0, build 7e803ba

Stop de docker daemon:

sudo service docker stop

To avoid

FATA[0000] bridge IPv6 does not match existing bridge configuration fe80::1

do this:

sudo apt-get install bridge-utils
sudo ifconfig docker0 down
sudo brctl delbr docker0

Then start the docker daemon with IPv6 and the IPv6 subnet:

sudo docker -d --ipv6 --fixed-cidr-v6="2001:AAAA:FF00:1700::/64"

And that's it! The docker daemon is ready, and you don't need any special settings in the docker container. Let's check that:

Check IPv6 within a ubuntu container:

sander@makreel:~$ sudo docker run -it ubuntu bash -c "ifconfig"
eth0      Link encap:Ethernet  HWaddr 02:42:ac:11:00:0a
          inet addr:172.17.0.10  Bcast:0.0.0.0  Mask:255.255.0.0
          inet6 addr: fe80::42:acff:fe11:a/64 Scope:Link
          inet6 addr: 2001:aaaa:ff00:1700:0:242:ac11:a/64 Scope:Global
          UP BROADCAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:110 (110.0 B)  TX bytes:90 (90.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Looks good. 
Check you have outside IPv6 connectivity

sander@makreel:~$ sudo docker run -it ubuntu bash -c "ping6 -c5 ipv6.google.com"
PING ipv6.google.com(2a00:1450:400c:c07::64) 56 data bytes
64 bytes from 2a00:1450:400c:c07::64: icmp_seq=3 ttl=56 time=7.12 ms
64 bytes from 2a00:1450:400c:c07::64: icmp_seq=4 ttl=56 time=7.05 ms
64 bytes from 2a00:1450:400c:c07::64: icmp_seq=5 ttl=56 time=7.28 ms

--- ipv6.google.com ping statistics ---
5 packets transmitted, 3 received, 40% packet loss, time 4019ms
rtt min/avg/max/mdev = 7.056/7.152/7.280/0.116 ms
sander@makreel:~$

Good! So IPv6 is working!

Speedtest:


$ sudo docker run -it ubuntu bash -c "apt-get update && apt-get install -y wget && wget -6 'http://ftp.belnet.be/ubuntu.com/ubuntu/releases/precise/ubuntu-12.04.4-desktop-i386.iso' -O /dev/null"
...
100%[======================================>] 766,509,056 8.25MB/s   in 97s
2015-02-17 12:16:50 (7.52 MB/s) - '/dev/null' saved [766509056/766509056]
sander@makreel:~$



Note: the official documentation https://docs.docker.com/articles/networking/#ipv6-with-docker does not state you need a separate IPv6 subnet. Strange.




Wednesday, January 14, 2015

One-liner to check (and ping6) IPv6 devices

A one-line to check IPv6 devices on your LAN:

$ ping6 -c3 -I wlan0 ff02::1 | awk ' /bytes from/ { print $4 }' | sort -u | sed 's/:$//'

fe80::1af4:6aff:fe9c:ced4
fe80::212:40ff:fe8a:8e38
fe80::66d1:a3ff:fe31:9c57
fe80::c24a:ff:fe2c:dcbc
fe80::d263:b4ff:fe00:2a61

So: 5 IPv6-enabled devices on my LAN. At least: 5 devices that react on the broadcast ping6.


You can feed that into ping6 to see if they are ping6-able:

$ ping6 -c3 -I wlan0 ff02::1 | awk ' /bytes from/ { print $4 }' | sort -u | sed 's/:$//' | awk '{ print "ping6 -c3 -I wlan0 " $1 }'  | /bin/sh | awk ' /PING/ { print $2 } /packets transmitted/ { print $0 "\n" }  '  

fe80::1af4:6aff:fe9c:ced4(fe80::1af4:6aff:fe9c:ced4)
3 packets transmitted, 3 received, 0% packet loss, time 2000ms

fe80::212:40ff:fe8a:8e38(fe80::212:40ff:fe8a:8e38)
3 packets transmitted, 3 received, 0% packet loss, time 2004ms

fe80::66d1:a3ff:fe31:9c57(fe80::66d1:a3ff:fe31:9c57)
3 packets transmitted, 3 received, 0% packet loss, time 2002ms

fe80::c24a:ff:fe2c:dcbc(fe80::c24a:ff:fe2c:dcbc)
3 packets transmitted, 3 received, 0% packet loss, time 2004ms

fe80::d263:b4ff:fe00:2a61(fe80::d263:b4ff:fe00:2a61)
3 packets transmitted, 3 received, 0% packet loss, time 2002ms

So ... they are all ping6-able.