Monday, January 31, 2011

Android 2.2 does IPv6, and ... answers ping's

Interesting: A HTC Wildfire with Android 2.2:
  • does IPv6 when it's provided via RADVD on a Wireless LAN
  • ... answers ping6-messages
Here's a dump from the webserver's logfile, and then a ping6 to that IPv6 address of the Android:

2001:838:3ba:a:baab:bbbb:aaaa:b - - [31/Jan/2011:23:46:21 +0100] "GET / HTTP/1.1" 200 1173 "" "Mozilla/5.0 (Linux; U; Android 2.2.1; nl-nl; HTC_Wildfire_A3333 Build/FRG83D) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1"

2001:838:3ba:a:baab:bbbb:aaaa:b - - [31/Jan/2011:23:46:22 +0100] "GET /favicon.ico HTTP/1.1" 200 5686 "http://www6.appelboor.com/" "Mozilla/5.0 (Linux; U; Android 2.2.1; nl-nl; HTC_Wildfire_A3333 Build/FRG83D) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1"



sander@vadmin648:~$ ping6 2001:838:3ba:a:baab:bbbb:aaaa:b
PING 2001:838:3ba:a:baab:bbbb:aaaa:b(2001:838:3ba:a:baab:bbbb:aaaa:b) 56 data bytes
64 bytes from 2001:838:3ba:a:baab:bbbb:aaaa:b: icmp_seq=1 ttl=52 time=1516 ms
64 bytes from 2001:838:3ba:a:baab:bbbb:aaaa:b: icmp_seq=2 ttl=52 time=516 ms
64 bytes from 2001:838:3ba:a:baab:bbbb:aaaa:b: icmp_seq=3 ttl=52 time=404 ms
64 bytes from 2001:838:3ba:a:baab:bbbb:aaaa:b: icmp_seq=4 ttl=52 time=296 ms
64 bytes from 2001:838:3ba:a:baab:bbbb:aaaa:b: icmp_seq=5 ttl=52 time=300 ms
^C
--- 2001:838:3ba:a:baab:bbbb:aaaa:b ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4012ms
rtt min/avg/max/mdev = 296.000/606.400/1516.000/461.895 ms, pipe 2
sander@vadmin648:~$ 


I think it would be better if the device would not ping back.

(FYI: the public IPv6 address has been changed for privacy reasons)

1 comment:

Anonymous said...

icmp is a requirement for ipv6, without which things break (unlike ipv6). so it's a good thing the phone responds to ping6