• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

[SOLVED] Ubuntu & radvd with HE tunnel to provide local network with IPV6

Started by samip, December 12, 2013, 10:32:33 AM

Previous topic - Next topic

samip

Hello all,

I'm trying to setup my server to provide IPV6 addresses from the tunnel and to get IPV6 connectifity on all PC's connected to that network.


ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:19:66:XX:XX:6d
         inet addr:88.195.XXX.XX  Bcast:88.195.XXX.255  Mask:255.255.240.0
         inet6 addr: fe80::219:66ff:fede:3a6d/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:13375504 errors:0 dropped:0 overruns:0 frame:0
         TX packets:21736056 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:2688176491 (2.6 GB)  TX bytes:29398824861 (29.3 GB)

eth1      Link encap:Ethernet  HWaddr 00:06:29:f7:a0:e8
         inet addr:192.168.1.101  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: fe80::206:29ff:fef7:a0e8/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:549878 errors:0 dropped:0 overruns:0 frame:0
         TX packets:209592 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:127961503 (127.9 MB)  TX bytes:31873647 (31.8 MB)

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:16436  Metric:1
         RX packets:167526 errors:0 dropped:0 overruns:0 frame:0
         TX packets:167526 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:84907969 (84.9 MB)  TX bytes:84907969 (84.9 MB)

sit0      Link encap:IPv6-in-IPv4
         inet6 addr: ::127.0.0.1/96 Scope:Unknown
         inet6 addr: ::192.168.1.101/96 Scope:Compat
         inet6 addr: ::192.168.122.1/96 Scope:Compat
         inet6 addr: ::88.195.XXX.XX/96 Scope:Compat
         UP RUNNING NOARP  MTU:1480  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)

sit1      Link encap:IPv6-in-IPv4
         inet6 addr: fe80::c0a8:165/64 Scope:Link
         inet6 addr: fe80::c0a8:7a01/64 Scope:Link
         inet6 addr: fe80::58c3:cc2d/64 Scope:Link
         inet6 addr: 2001:470:27:743::2/64 Scope:Global
         UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
         RX packets:22 errors:0 dropped:0 overruns:0 frame:0
         TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:2474 (2.4 KB)  TX bytes:2491 (2.4 KB)

virbr0    Link encap:Ethernet  HWaddr 9e:6f:XX:XX:99:94
         inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
         UP BROADCAST MULTICAST  MTU:1500  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)


radvd.conf:

interface eth1 {
   IgnoreIfMissing on;
   # We are sending advertisments (route)
   AdvSendAdvert on;
   # When set, host use the administered (stateful) protocol
   # for address autoconfiguration. The use of this flag is
   # described in RFC 4862
   AdvManagedFlag off;

   AdvDefaultPreference low;
   AdvHomeAgentFlag off;

   # When set, host use the administered (stateful) protocol
   # for address autoconfiguration. For other (non-address)
   # information.
   # The use of this flag is described in RFC 4862
   AdvOtherConfigFlag on;

   # Suggested Maximum Transmission setting for using the
   # Hurricane Electric Tunnel Broker.
   AdvLinkMTU 1480;


   MinRtrAdvInterval 30;
   MaxRtrAdvInterval 60;
   prefix 2001:470:28:743:1::/64 {
       AdvOnLink on;
       #Base6to4Interface sit0;
       AdvAutonomous on;
       AdvRouterAddr on;
   };
};


IPV6 routing table (ip -6 route show):

::/96 via :: dev sit0  metric 256
2001:470:27:743::/64 via :: dev sit1  proto kernel  metric 256
fe80::/64 dev eth1  proto kernel  metric 256
fe80::/64 dev eth0  proto kernel  metric 256 <- problem?
fe80::/64 via :: dev sit1  proto kernel  metric 256


Windows Client ipconfig:

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection 2:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :

Ethernet adapter Local Area Connection 8:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :

Ethernet adapter Local Area Connection 6:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :

Ethernet adapter Local Area Connection 5:

  Connection-specific DNS Suffix  . : cable.inet.fi
  IPv6 Address. . . . . . . . . . . : 2001:470:28:743:4923:c01c:c89a:567a
  Link-local IPv6 Address . . . . . : fe80::4923:c01c:c89a:567a%21
  IPv4 Address. . . . . . . . . . . : 192.168.1.103
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : fe80::206:29ff:fef7:a0e8%21
                                      192.168.1.1

Tunnel adapter IP6Tunnel:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

  Connection-specific DNS Suffix  . :
  IPv6 Address. . . . . . . . . . . : 2001:0:c38c:c38c:8f9:a2c:a73c:3334
  Link-local IPv6 Address . . . . . : fe80::8f9:a2c:a73c:3334%38
  Default Gateway . . . . . . . . . :


Ping to default ipv6 gateway from Windows PC (ping -6 fe80::206:29ff:fef7:a0e8%21):

Pinging fe80::206:29ff:fef7:a0e8%21 with 32 bytes of data:
Reply from fe80::206:29ff:fef7:a0e8%21: time<1ms
Reply from fe80::206:29ff:fef7:a0e8%21: time<1ms
Reply from fe80::206:29ff:fef7:a0e8%21: time=1ms

Ping statistics for fe80::206:29ff:fef7:a0e8%21:
   Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 0ms, Maximum = 1ms, Average = 0ms
Control-C


Ping to google.fi from Windows PC (ping -6 google.fi):

Pinging google.fi [2a00:1450:400f:802::1017] with 32 bytes of data:
Request timed out.

Ping statistics for 2a00:1450:400f:802::1017:
   Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C


Ping to google.fi from IPV6 gateway (ping6 -c 4 google.fi):

PING google.fi(bud02s01-in-x1f.1e100.net) 56 data bytes
64 bytes from bud02s01-in-x1f.1e100.net: icmp_seq=1 ttl=55 time=73.4 ms
64 bytes from bud02s01-in-x1f.1e100.net: icmp_seq=2 ttl=55 time=76.4 ms
64 bytes from bud02s01-in-x1f.1e100.net: icmp_seq=3 ttl=55 time=82.0 ms
64 bytes from bud02s01-in-x1f.1e100.net: icmp_seq=4 ttl=55 time=79.3 ms

--- google.fi ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 73.486/77.831/82.056/3.215 ms


In case it matters traceroute to google.fi from Gateway (traceroute6 google.fi):

traceroute to google.fi (2404:6800:4006:805::1018) from 2001:470:27:743::2, port 33434, from port 60688, 30 hops max, 60 bytes packets
1  samip-4.tunnel.tserv24.sto1.ipv6.he.net (2001:470:27:743::1)  21.650 ms  22.761 ms  27.412 ms
2  ge2-20.core1.sto1.he.net (2001:470:0:11e::1)  26.838 ms  27.430 ms  30.019 ms
3  10ge3-1.core1.cph1.he.net (2001:470:0:2ad::2)  34.919 ms  25.984 ms  23.691 ms
4  10ge16-1.core1.fra1.he.net (2001:470:0:2ac::1)  58.548 ms  60.532 ms  61.330 ms
5  de-cix10.net.google.com (2001:7f8::3b41:0:1)  90.816 ms  85.997 ms  152.006 ms
6  2001:4860::1:0:4ca3 (2001:4860::1:0:4ca3)  61.292 ms  106.110 ms  58.974 ms
7  2001:4860::8:0:5038 (2001:4860::8:0:5038)  100.939 ms  57.963 ms  63.961 ms
8  2001:4860::8:0:5e18 (2001:4860::8:0:5e18)  71.591 ms  77.804 ms  77.026 ms
9  2001:4860::8:0:6374 (2001:4860::8:0:6374)  151.612 ms  150.498 ms  143.865 ms
10  2001:4860::8:0:5900 (2001:4860::8:0:5900)  164.781 ms  158.812 ms  *
11  2001:4860::8:0:4cde (2001:4860::8:0:4cde)  169.326 ms  * 171.062 ms
12  2001:4860::8:0:3427 (2001:4860::8:0:3427)  183.142 ms  181.271 ms  181.808 ms
13  * 2001:4860::8:0:252d (2001:4860::8:0:252d)  208.359 ms  223.392 ms
14  2001:4860::8:0:61e0 (2001:4860::8:0:61e0)  208.190 ms  220.401 ms  312.050 ms
15  2001:4860::1:0:77d (2001:4860::1:0:77d)  238.376 ms  315.182 ms  352.414 ms
16  2001:4860::1:0:26fc (2001:4860::1:0:26fc)  437.782 ms  448.502 ms  308.367 ms
17  * 2001:4860::1:0:9f7 (2001:4860::1:0:9f7)  401.918 ms  444.829 ms
18  2001:4860:0:1::5f (2001:4860:0:1::5f)  406.530 ms  402.844 ms  417.158 ms
19  2404:6800:8000:2a::3 (2404:6800:8000:2a::3)  400.745 ms  413.192 ms  400.878 ms


Output of command " tcpdump -i eth0 -n proto 41 -vv" (While pinging google.fi via IPV6):

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
20:34:52.887926 IP (tos 0x0, ttl 64, id 1079, offset 0, flags [DF], proto IPv6 (41), length 124)
   88.195.XXX.XX > 216.66.80.90: IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:470:27:743::2 > 2607:f8b0:4002:c01::5e: [icmp6 sum ok] ICMP6, echo request, seq 1
20:34:53.046438 IP (tos 0x0, ttl 249, id 0, offset 0, flags [DF], proto IPv6 (41), length 124)
   216.66.80.90 > 88.195.XXX.XX: IP6 (hlim 53, next-header ICMPv6 (58) payload length: 64) 2607:f8b0:4002:c01::5e > 2001:470:27:743::2: [icmp6 sum ok] ICMP6, echo reply, seq 1
20:34:54.100642 IP (tos 0x0, ttl 64, id 1080, offset 0, flags [DF], proto IPv6 (41), length 124)
   88.195.XXX.XX > 216.66.80.90: IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:470:27:743::2 > 2607:f8b0:4002:c01::5e: [icmp6 sum ok] ICMP6, echo request, seq 2
20:34:54.261450 IP (tos 0x0, ttl 249, id 0, offset 0, flags [DF], proto IPv6 (41), length 124)
   216.66.80.90 > 88.195.XXX.XX: IP6 (hlim 53, next-header ICMPv6 (58) payload length: 64) 2607:f8b0:4002:c01::5e > 2001:470:27:743::2: [icmp6 sum ok] ICMP6, echo reply, seq 2
20:34:55.101873 IP (tos 0x0, ttl 64, id 1081, offset 0, flags [DF], proto IPv6 (41), length 124)
   88.195.XXX.XX > 216.66.80.90: IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:470:27:743::2 > 2607:f8b0:4002:c01::5e: [icmp6 sum ok] ICMP6, echo request, seq 3
20:34:55.292956 IP (tos 0x0, ttl 249, id 0, offset 0, flags [DF], proto IPv6 (41), length 124)
   216.66.80.90 > 88.195.XXX.XX: IP6 (hlim 53, next-header ICMPv6 (58) payload length: 64) 2607:f8b0:4002:c01::5e > 2001:470:27:743::2: [icmp6 sum ok] ICMP6, echo reply, seq 3
20:34:56.101578 IP (tos 0x0, ttl 64, id 1082, offset 0, flags [DF], proto IPv6 (41), length 124)
   88.195.XXX.XX > 216.66.80.90: IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:470:27:743::2 > 2607:f8b0:4002:c01::5e: [icmp6 sum ok] ICMP6, echo request, seq 4
20:34:56.262769 IP (tos 0x0, ttl 249, id 0, offset 0, flags [DF], proto IPv6 (41), length 124)
   216.66.80.90 > 88.195.XXX.XX: IP6 (hlim 53, next-header ICMPv6 (58) payload length: 64) 2607:f8b0:4002:c01::5e > 2001:470:27:743::2: [icmp6 sum ok] ICMP6, echo reply, seq 4
20:34:57.102342 IP (tos 0x0, ttl 64, id 1083, offset 0, flags [DF], proto IPv6 (41), length 124)
   88.195.XXX.XX > 216.66.80.90: IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:470:27:743::2 > 2607:f8b0:4002:c01::5e: [icmp6 sum ok] ICMP6, echo request, seq 5
20:34:57.263189 IP (tos 0x0, ttl 249, id 0, offset 0, flags [DF], proto IPv6 (41), length 124)
   216.66.80.90 > 88.195.XXX.XX: IP6 (hlim 53, next-header ICMPv6 (58) payload length: 64) 2607:f8b0:4002:c01::5e > 2001:470:27:743::2: [icmp6 sum ok] ICMP6, echo reply, seq 5
^C
10 packets captured
24 packets received by filter
0 packets dropped by kernel


Any advices?

---------------------------------------------------
About censored IP:

I have censored some of my (IPV4) ip address as I don't wish to share it as it's no longer needed if it even needed in any point of time.

broquea

Quick hints:

prefix 2001:470:28:743:1::/64 {

should be

prefix 2001:470:28:743::/64 {

eth1 needs 2001:470:28:743::1/64 configured on it

make certain sysctl.conf has ipv6 forwarding enabled

and be certain to disable the Teredo on your Windows machines. just to keep it clean.

---------------------------------------------------------------------------------------------------------------------

Long version:

eth1 needs an ip on it, or at least a route to your routed /64 (ip on interface creates that local route). If you look at your routing table on the gateway device, you see it doesn't have a local route back to the SLAAC hosts. With no return path route to the clients, the replying packets just fall to the floor.

Also you don't seem to have a default route either. Make certain to add one.

samip


broquea

Quote from: samip on December 12, 2013, 11:40:19 AM
Quote from: broquea on December 12, 2013, 11:23:12 AM
make certain sysctl.conf has ipv6 forwarding enabled

Even when using Ubuntu?

of course. It can't function as a router if it isn't forwarding packets. This is true for any linux distro.

samip

Quote from: broquea on December 12, 2013, 11:42:24 AM
Quote from: samip on December 12, 2013, 11:40:19 AM
Quote from: broquea on December 12, 2013, 11:23:12 AM
make certain sysctl.conf has ipv6 forwarding enabled

Even when using Ubuntu?

of course. It can't function as a router if it isn't forwarding packets. This is true for any linux distro.

Did that and still unable to access IPV6 from local network attached machine.

----------------------------------------------------------

Output of "tcpdump -ni eth1 ip6":

root@Ubuntu-Server:~# tcpdump -ni eth1 ip6
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
22:01:09.811779 IP6 fe80::4923:c01c:c89a:567a.61991 > ff02::c.1900: UDP, length 146
22:01:12.812908 IP6 fe80::4923:c01c:c89a:567a.61991 > ff02::c.1900: UDP, length 146
22:01:15.813144 IP6 fe80::4923:c01c:c89a:567a.61991 > ff02::c.1900: UDP, length 146
22:01:19.812484 IP6 fe80::4923:c01c:c89a:567a.61991 > ff02::c.1900: UDP, length 146
22:01:21.273721 IP6 2001:470:28:740:4923:c01c:c89a:567a > 2a00:1450:400f:802::1017: ICMP6, echo request, seq 34, length 40
22:01:22.813576 IP6 fe80::4923:c01c:c89a:567a.61991 > ff02::c.1900: UDP, length 146
22:01:23.406275 IP6 fe80::206:29ff:fef7:a0e8 > ff02::1: ICMP6, router advertisement, length 64
22:01:25.813799 IP6 fe80::4923:c01c:c89a:567a.61991 > ff02::c.1900: UDP, length 146
22:01:26.133684 IP6 fe80::4923:c01c:c89a:567a > fe80::206:29ff:fef7:a0e8: ICMP6, neighbor solicitation, who has fe80::206:29ff:fef7:a0e8, length 32
22:01:26.133767 IP6 fe80::206:29ff:fef7:a0e8 > fe80::4923:c01c:c89a:567a: ICMP6, neighbor advertisement, tgt is fe80::206:29ff:fef7:a0e8, length 24
22:01:26.133785 IP6 2001:470:28:740:4923:c01c:c89a:567a > 2a00:1450:400f:802::1017: ICMP6, echo request, seq 35, length 40
22:01:29.814231 IP6 fe80::4923:c01c:c89a:567a.61991 > ff02::c.1900: UDP, length 146
^C
12 packets captured
13 packets received by filter
0 packets dropped by kernel



broquea

Quote
Did that and still unable to access IPV6 from local network attached machine.

did you do the rest that I mentioned?

-edit- I see 2001:470:28:743::1 replies, any progress with the lan clients?

samip

Quote from: broquea on December 12, 2013, 12:18:12 PM
Quote
Did that and still unable to access IPV6 from local network attached machine.

did you do the rest that I mentioned?

-edit- I see 2001:470:28:743::1 replies, any progress with the lan clients?

I did and your suggestion to ravdv.conf did not fix it, but here are the updated details:

Gateway ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:19:66:de:3a:6d  
         inet addr:88.195.XXX.XX  Bcast:88.195.XX.255  Mask:255.255.240.0
         inet6 addr: fe80::219:66ff:fede:3a6d/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:21173777 errors:0 dropped:0 overruns:0 frame:0
         TX packets:33948308 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:4306848194 (4.3 GB)  TX bytes:45806534848 (45.8 GB)

eth1      Link encap:Ethernet  HWaddr 00:06:29:f7:a0:e8  
         inet addr:192.168.1.101  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: fe80::206:29ff:fef7:a0e8/64 Scope:Link
         inet6 addr: 2001:470:28:743::1/64 Scope:Global
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:737486 errors:0 dropped:0 overruns:0 frame:0
         TX packets:318895 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:166052725 (166.0 MB)  TX bytes:156571769 (156.5 MB)

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:16436  Metric:1
         RX packets:226775 errors:0 dropped:0 overruns:0 frame:0
         TX packets:226775 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:90970735 (90.9 MB)  TX bytes:90970735 (90.9 MB)

sit0      Link encap:IPv6-in-IPv4  
         inet6 addr: ::127.0.0.1/96 Scope:Unknown
         inet6 addr: ::192.168.1.101/96 Scope:Compat
         inet6 addr: ::192.168.122.1/96 Scope:Compat
         inet6 addr: ::88.195.XXX.XX/96 Scope:Compat
         UP RUNNING NOARP  MTU:1480  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)

sit1      Link encap:IPv6-in-IPv4  
         inet6 addr: fe80::c0a8:165/64 Scope:Link
         inet6 addr: fe80::c0a8:7a01/64 Scope:Link
         inet6 addr: fe80::58c3:cc2d/64 Scope:Link
         inet6 addr: 2001:470:27:743::2/64 Scope:Global
         UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
         RX packets:105386 errors:0 dropped:0 overruns:0 frame:0
         TX packets:66558 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:128045217 (128.0 MB)  TX bytes:8462007 (8.4 MB)



radvd.conf:

interface eth1 {
   IgnoreIfMissing on;
   # We are sending advertisments (route)
   AdvSendAdvert on;
   # When set, host use the administered (stateful) protocol
   # for address autoconfiguration. The use of this flag is
   # described in RFC 4862
   AdvManagedFlag off;

   AdvDefaultPreference low;
   AdvHomeAgentFlag off;

   # When set, host use the administered (stateful) protocol
   # for address autoconfiguration. For other (non-address)
   # information.
   # The use of this flag is described in RFC 4862
   AdvOtherConfigFlag on;

   # Suggested Maximum Transmission setting for using the
   # Hurricane Electric Tunnel Broker.
   AdvLinkMTU 1480;


   MinRtrAdvInterval 30;
   MaxRtrAdvInterval 60;
# 2001:470:28:743::/64
   prefix ::/64 {
       AdvOnLink on;
    #Base6to4Interface sit0;
       AdvAutonomous on;
       AdvRouterAddr on;
   };
};


Gateway IPV6 routing table (ip -6 r):

::/96 via :: dev sit0  metric 256
2001:470:27:743::/64 via :: dev sit1  proto kernel  metric 256
2001:470:28:743::/64 dev eth1  proto kernel  metric 256
fe80::/64 dev eth1  proto kernel  metric 256
fe80::/64 dev eth0  proto kernel  metric 256
fe80::/64 via :: dev sit1  proto kernel  metric 256
default dev sit1  metric 1


Ping to google.fi via IPV6 from Linux Client (ping6 -c4 google.fi):

PING google.fi(par03s03-in-x17.1e100.net) 56 data bytes
64 bytes from par03s03-in-x17.1e100.net: icmp_seq=1 ttl=52 time=71.8 ms
64 bytes from par03s03-in-x17.1e100.net: icmp_seq=2 ttl=52 time=70.9 ms
64 bytes from par03s03-in-x17.1e100.net: icmp_seq=3 ttl=52 time=67.7 ms
64 bytes from par03s03-in-x17.1e100.net: icmp_seq=4 ttl=52 time=73.4 ms

--- google.fi ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 67.728/70.992/73.450/2.105 ms


Thanks a lot @Dagger2 in  #networking on FreeNode IRC network!
Thanks too for the replies to this thread! :)