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

Can't access ipv6 internet on client

Started by cssdesign, May 13, 2013, 02:15:21 PM

Previous topic - Next topic

cssdesign

I installed the tunnel on the server. From there i can visit IPv6 only sites.
Then i went ahead to enable forwarding in sysctl, and setup radvd.
I've did the same steps previously and all was good, but for some reason i had to take down the tunnel and start again.
But now, i can't access IPv6 only sites at the tunnel side.
I can ping the static address i assigned for the server side, but that's about it.

Can anyone please tell me what i am doing wrong?

broquea

Did you use the ROUTED prefix for the LAN client machines? Paste some configs.

cssdesign

#2
my radvd configuration is like this


interface eth0 {
   IgnoreIfMissing on;
   AdvSendAdvert on;
   MinRtrAdvInterval 30;
   MaxRtrAdvInterval 60;
   prefix 2001:470:7c:12e::/64 {
       AdvOnLink on;
       AdvAutonomous on;
       AdvRouterAddr on;
   };
};

broquea

Ok based on testing 2001:470:7b:12e::1, I see that what you are using is indeed your ROUTED prefix. Make certain you've configured an address out of the /64 on eth0, like 2001:470:7c:12e::1/64

cssdesign

i have this line there:

iface eth0 inet6 static
   address 2001:470:7c:12e::1
   netmask 64

broquea

Before it wasn't reachable. now it is!

HOST: ipvsixme                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 2001:470:1:9::1            0.0%     2    0.6   0.6   0.6   0.6   0.0
  2.|-- 10gigabitethernet8-4.core  0.0%     2    0.6   0.6   0.6   0.6   0.0
  3.|-- 10gigabitethernet1-1.core  0.0%     2    1.0   1.0   1.0   1.0   0.0
  4.|-- 10gigabitethernet3-3.core  0.0%     2   28.0  28.0  28.0  28.0   0.0
  5.|-- 10gigabitethernet5-5.core  0.0%     2   39.6  39.6  39.6  39.6   0.0
  6.|-- tserv1.mci3.he.net         0.0%     2   40.0  40.1  40.0  40.3   0.2
  7.|-- 2001:470:7c:12e::1         0.0%     2   99.5  86.0  72.5  99.5  19.1


That solve the issue for your clients sitting on the LAN?

cssdesign

Thanks a lot.I figured i had to delete the inet6 address in the eth0 and restart the network and it kinda solved the problem.