Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: ipv6 routing linux server - client ping error  (Read 8847 times)

ashemta

  • Newbie
  • *
  • Posts: 6
ipv6 routing linux server - client ping error
« on: June 29, 2011, 04:49:47 AM »

hello
network architecture

internet >> debian server >> client 1 ubuntu >> client 2 ...

debian server ping6 ipv6.google.com ok

ip routing client does therefore not

config debien server

my config ipv6:
IPv6 Tunnel Endpoints
Server IPv4 Address:216.66.84.42
Server IPv6 Address:2001:470:1f12:9a8::1/64
Client IPv4 Address: 93.19.242.XX
Client IPv6 Address:2001:470:1f12:9a8::2/64

Routed IPv6 Prefixes
Routed /64:2001:470:1f13:9a8::/64

routeurs:~# ifconfig

eth0 = full net
eth1 = local
he-ipv6 = tunnelbroker

eth0      Link encap:Ethernet  HWaddr 00:0e:a6:82:d2:89  
          inet adr:93.19.242.XX  Bcast:93.19.242.255  Masque:255.255.255.0
          adr inet6: fe80::20e:a6ff:fe82:d289/64 Scope:Lien
          RX bytes:1282083536 (1.1 GiB)  TX bytes:65343641 (62.3 MiB)

eth1      Link encap:Ethernet  HWaddr 00:e0:29:05:72:7c  
          inet adr:192.168.1.2  Bcast:192.168.1.255  Masque:255.255.255.0
          adr inet6: fe80::2e0:29ff:fe05:727c/64 Scope:Lien
         RX bytes:73072945 (69.6 MiB)  TX bytes:1368826633 (1.2 GiB)

he-ipv6   Link encap:IPv6-dans-IPv4  
          adr inet6: 2001:470:1f12:9a8::2/64 Scope:Global
          adr inet6: fe80::c0a8:102/64 Scope:Lien
          RX bytes:764369 (746.4 KiB)  TX bytes:777979 (759.7 KiB)

lo        Link encap:Boucle locale  
          inet adr:127.0.0.1  Masque:255.0.0.0
          adr inet6: ::1/128 Scope:Hôte
          RX bytes:28579766 (27.2 MiB)  TX bytes:28579766 (27.2 MiB)

routeurs:~# ping6 ipv6.google.com
PING ipv6.google.com(fra07s07-in-x93.1e100.net) 56 data bytes
64 bytes from fra07s07-in-x93.1e100.net: icmp_seq=1 ttl=58 time=43.3 ms

--- ipv6.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 41.396/42.320/43.302/0.739 ms

my config radvd.conf
interface eth1

{

AdvSendAdvert on;
# Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump
AdvManagedFlag off;
AdvOtherConfigFlag on;
AdvReachableTime 0;
AdvRetransTimer 0;
AdvCurHopLimit 64;
AdvDefaultLifetime 300;
AdvHomeAgentFlag off;
AdvDefaultPreference medium;
AdvSourceLLAddress on;
AdvDefaultLifetime 900;

prefix  2001:470:1f13:9a8::/64 {


AdvValidLifetime 86400;
AdvPreferredLifetime 14400;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
}; # End of prefix definition
}; # End of interface definition

my config /etc/wide-dhcpv6/dhcp6s.conf

option domain-name-servers 2001:470:1f12:9a8::2 2001:4860:4860::8844;

option domain-name "nXXXXX.co.jp";
option refreshtime 900;

interface eth1 {
        address-pool pool1 3600;
};
pool pool1 {
        range 2001:470:1f13:9a8::1000 to 2001:470:1f13:9a8::2000;
};

ip dhcp attribute correctly and dns (except default route)

route --inet6
Table de routage IPv6 du noyau
Destination                    Next Hop                   Flag Met Ref Use If
2001:470:1f12:9a8::1/128       ::                         U    1024 0     1 he-ipv6
2001:470:1f13:9a8::/64         ::                         U    256 0     0 eth1
fe80::/64                      ::                         U    256 0     0 eth1
fe80::/64                      ::                         Un   256 0     0 he-ipv6
fe80::/64                      ::                         U    256 0     0 eth0
::/0                           2001:470:1f12:9a8::1       UG   1024 0   390 he-ipv6
::/0                           ::                         U    1024 0     0 he-ipv6
::/0                           ::                         !n   -1  1  5319 lo
::1/128                        ::                         Un   0   1  3732 lo
2001:470:1f12:9a8::/128        ::                         Un   0   1     0 lo
2001:470:1f12:9a8::2/128       ::                         Un   0   1    16 lo
fe80::/128                     ::                         Un   0   1     0 lo
fe80::/128                     ::                         Un   0   1     0 lo
fe80::/128                     ::                         Un   0   1     0 lo
fe80::c0a8:102/128             ::                         Un   0   1     0 lo
fe80::20e:a6ff:fe82:d289/128   ::                         Un   0   1     0 lo
fe80::2e0:29ff:fe05:727c/128   ::                         Un   0   1   165 lo
ff00::/8                       ::                         U    256 0     0 eth1
ff00::/8                       ::                         U    256 0     0 he-ipv6
ff00::/8                       ::                         U    256 0     0 eth0
::/0                           ::                         !n   -1  1  5319 lo

server ping6 client ok fe80XXX
client ping6 ipv6 server ok fe80XXX

client ping6 ipv6.google.com

CLIENT:
ping6 -I eth0 ipv6.google.com
PING ipv6.google.com(fra07s07-in-x67.1e100.net) from 2001:470:1f13:9a8::1000 eth0: 56 data bytes
From 2001:470:1f13:9a8::1000 icmp_seq=2 Destination unreachable: Address unreachable

I can not found the error so that the customer comes to ping google

Thank you in advance for the great help you to bring me
I'm looking now for one week without rest, but to no avail

big thank you to you

Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2663
Re: ipv6 routing linux server - client ping error
« Reply #1 on: June 29, 2011, 05:09:34 AM »

I guess I'm not sure what you're asking.

You do need to assign an IPv6 address to your eth1 address though.
Logged

ashemta

  • Newbie
  • *
  • Posts: 6
Re: ipv6 routing linux server - client ping error
« Reply #2 on: June 29, 2011, 05:16:12 AM »

the real problem and that the

Linux Client
Jean-Baptiste Jean-Baptiste-@ laptop: ~ $ ping6-I eth0 ipv6.google.com
PING ipv6.google.com (fra07s07-in-x67.1e100.net) from 2001:470:1 f13: 9A8:: 1000 eth0: 56 data bytes
From 2001:470:1 f13: 9A8:: 1000 icmp_seq = 2 Destination unreachable: Address unreachable

and therefore it leads connected to the eth1 of server
Logged

snarked

  • Hero Member
  • *****
  • Posts: 729
Re: ipv6 routing linux server - client ping error
« Reply #3 on: June 29, 2011, 11:54:19 AM »

Routing is incomplete - eth1 needs to have an IPv6 address assignment from 2001:470:1f13:9a8::/64.  You need to define that address as the gateway if radvd doesn't do that for you.

This line looks wrong too:
Quote
::/0                           ::                         U    1024 0     0 he-ipv6
It should be gated via He's tunnel endpoint address.
Logged

ashemta

  • Newbie
  • *
  • Posts: 6
Re: ipv6 routing linux server - client ping error
« Reply #4 on: June 30, 2011, 01:46:12 AM »

I add the ip like these?

routeurs:~# ip -6 route add 2001:470:1f13:9a8::/64 via eth1

doije simply remove it: / 0:: U 1024 0 0 he-ipv6
via ip -6 route del  ::/0 via he-ipv6 ?
« Last Edit: June 30, 2011, 01:48:10 AM by ashemta »
Logged

ashemta

  • Newbie
  • *
  • Posts: 6
Re: ipv6 routing linux server - client ping error
« Reply #5 on: June 30, 2011, 12:06:18 PM »

when I give a theoretically IPv6 eth0, the net must pass to ping the address?
tested
routeurs:~# route -A inet6 add 2001:470:1f13:9a8::1000 dev eth0
routeurs:~# route -A inet6 add 2001:470:1f13:9a8::1001 dev he-ipv6

test ping et traceroute error 100% packet loss
via http://www.berkom.blazing.de/tools/ping.cgi
http://www.berkom.blazing.de/tools/traceroute.cgi

how to succeed pointed ping ??

Logged

snarked

  • Hero Member
  • *****
  • Posts: 729
Re: ipv6 routing linux server - client ping error
« Reply #6 on: June 30, 2011, 12:13:44 PM »

Quote
routeurs:~# ip -6 route add 2001:470:1f13:9a8::/64 via eth1
NO!  Do not use the "all zeros" address on eth1.  Try 2001:470:1f13:9a8::1/64.
Logged

ashemta

  • Newbie
  • *
  • Posts: 6
Re: ipv6 routing linux server - client ping error
« Reply #7 on: June 30, 2011, 12:24:37 PM »

ip -6 route add 2001:470:1f13:9a8::/64 via eth1
Error: an inet address is expected rather than "eth1".

routeurs:~# route -A inet6 add 2001:470:1f13:9a8::1/64 dev eth1
I test the ping
100% packet loss

route -A inet6 add 2001:470:1f13:9a8::1/64 dev eth0
100% packet loss (source http://www.berkom.blazing.de/tools/ping.cgi?)



the prefix 2001:470:1f13:9a8::/64 dev eth0 eth1 ou he-ipv6 ??


I test just the score on the router
« Last Edit: June 30, 2011, 12:31:24 PM by ashemta »
Logged