Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: 1 [2] 3

Author Topic: ipv6 tests - created tunnel now what?  (Read 12011 times)

SE1

  • Newbie
  • *
  • Posts: 20
Re: ipv6 tests - created tunnel now what?
« Reply #15 on: October 11, 2011, 02:50:35 PM »

Sorry. Here it is attached.

I can ping the ipv6 address on the windows machine from the VM, but can't access the internet.
Logged

SE1

  • Newbie
  • *
  • Posts: 20
Re: ipv6 tests - created tunnel now what?
« Reply #16 on: October 11, 2011, 05:33:23 PM »

My topology is as shown in the jpeg.


The default GW for the ubuntu VM is 138.111.56.12 and ipv6 2001:470:67:47::3

i am able to ping client side of the tunnel but not the server side of the tunnel, so cant get to the web.

everything is working perfectly on windows.

P.S. I have also attached the ip address config, please let me know where i went wrong.
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2732
Re: ipv6 tests - created tunnel now what?
« Reply #17 on: October 12, 2011, 04:13:21 AM »

Everything looks good to me.

I assume your tunnel works from the Windows side?

Are you able to ping the windows machine from your Ubuntu VM?
Logged

SE1

  • Newbie
  • *
  • Posts: 20
Re: ipv6 tests - created tunnel now what?
« Reply #18 on: October 12, 2011, 11:10:55 AM »

yes the tunnel works from the windows side.

I can ping the windows machine from the ubuntu vm but can't access the tunnel from the ubuntu vm.

What could be wrong?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2732
Re: ipv6 tests - created tunnel now what?
« Reply #19 on: October 13, 2011, 04:11:34 AM »

I'm wondering if there's a setting you need to make on the Windows side to tell it to route traffic
Logged

SE1

  • Newbie
  • *
  • Posts: 20
Re: ipv6 tests - created tunnel now what?
« Reply #20 on: October 13, 2011, 11:56:59 AM »

I m not sure about that.

Do you know where i can find information about that.
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2732
Re: ipv6 tests - created tunnel now what?
« Reply #21 on: October 13, 2011, 12:12:18 PM »

Found it

Below is a copy of a document written by a college friend that he used to make Windows act as a router.  He wrote it for Vista, but I'm guessing the steps are the same for Win7

Code: [Select]
Steps below were done in Vista.  Steps for Windows 7 might be a little different.

1.  Open Regedit, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters
Add STRING value called ‘DisabledComponents’ and set its value to 0; Reboot
Open the LAN adapter properties and open the IPv6 properties
Manually add an address from this subnet: 2001:db8:1f07:e9a::/64
Keep the prefix at 64
Add this gateway: 2001:db8:1f06:e9a::1
Add this DNS server: 2001:db8:200::2 (this is one of HE’s DNS servers)
Click OK and OK to save the changes
Open ‘cmd’ and type the following commands
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel <your local IP address> 216.66.22.2
netsh interface ipv6 add address IP6Tunnel 2001:db8:1f06:e9a::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:db8:1f06:e9a::1

10.  Test IPv6 connectivity by pinging or opening a website like ipv6.google.com

Steps to configure host to act as IPv6 router

1.  In CMD type: netsh int ipv6 set interface IP6Tunnel forwarding=enabled
2.  Next, type: netsh int ipv6 set interface "Local Area Connection" forwarding=enabled advertise=enabled
3.  Next, add the first address of the routed IP address to the Local Area Connection
netsh int ipv6 add address "Local Area Connection" 2001:db8:8:a0a::1
4.  Next, add the default route and next hop for the tunnel and Local Area Connection, then publish it:
netsh int ipv6 set route 2001:db8:8:a0a::/64 "Local Area Connection" publish=yes
5.  Next, add the default route for the tunnel and publish it:
netsh interface ipv6 set route ::/0 IP6Tunnel 2001:db8:7:a0a::1 publish=yes

I've changed all addresses to use the documentation prefix, so you'd obviously need to use your ranges to make it work
Logged

SE1

  • Newbie
  • *
  • Posts: 20
Re: ipv6 tests - created tunnel now what?
« Reply #22 on: October 13, 2011, 12:52:21 PM »

hey thanks for the reply.


I am able to get to the internet through the vm but i cant ping the server tunnel endpoint: 2001:470:66:47::1; why is that?
I check the with testipv6.com; it passes all the tests however the ipv6 address shown differs from the static one i configured.


IPv6 Tunnel Endpoints
Server IPv4 Address:64.62.134.130
Server IPv6 Address:2001:470:66:47::1/64
Client IPv4 Address:138.111.56.12
Client IPv6 Address:2001:470:66:47::2/64
Available DNS Resolvers
Anycasted IPv6 Caching Nameserver:2001:470:20::2
Anycasted IPv4 Caching Nameserver:74.82.42.42
Routed IPv6 Prefixes
Routed /64:2001:470:67:47::/64
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2732
Re: ipv6 tests - created tunnel now what?
« Reply #23 on: October 13, 2011, 12:54:44 PM »

What IPv6 address is it showing?

I wouldn't worry about pinging that ::1 address if your tunnel is working.  Can you ping ipv6.google.com from your VM?
Logged

SE1

  • Newbie
  • *
  • Posts: 20
Re: ipv6 tests - created tunnel now what?
« Reply #24 on: October 13, 2011, 01:04:35 PM »

I can ping ipv6.google.com.

The address shown is 2001:470:67:47:a00:27ff:fe89:7feb. My VM is getting that address, but the interfaces file has eth0 inet6 --> 2001:470:67:47::4

seuser@seuser-desktop:~$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:27:89:7f:eb 
          inet addr:138.111.56.10  Bcast:138.111.56.127  Mask:255.255.255.128
          inet6 addr: 2001:470:67:47:a00:27ff:fe89:7feb/64 Scope:Global
          inet6 addr: fe80::a00:27ff:fe89:7feb/64 Scope:Link
          inet6 addr: 2001:470:67:47::4/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:41 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3513 (3.5 KB)  TX bytes:7887 (7.8 KB)


what could be the issue?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2732
Re: ipv6 tests - created tunnel now what?
« Reply #25 on: October 13, 2011, 01:08:42 PM »

That address you listed is your RA assigned address

If you want to use the ::4 address, tell the VM to not do RA
Logged

SE1

  • Newbie
  • *
  • Posts: 20
Re: ipv6 tests - created tunnel now what?
« Reply #26 on: October 13, 2011, 01:21:49 PM »

Thanks a lot for your help. It is working.

Can I setup a Ipv6 LAN running on the VM and send traffic through the tunnel ?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2732
Re: ipv6 tests - created tunnel now what?
« Reply #27 on: October 13, 2011, 01:24:08 PM »

Quote
Can I setup a Ipv6 LAN running on the VM and send traffic through the tunnel ?

I guess I'm not sure what you mean by this

Logged

SE1

  • Newbie
  • *
  • Posts: 20
Re: ipv6 tests - created tunnel now what?
« Reply #28 on: October 13, 2011, 01:28:09 PM »

Is it possible to have multiple interfaces on the VM each in a different IPv6 network, and send the traffic through the tunnel outside?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2732
Re: ipv6 tests - created tunnel now what?
« Reply #29 on: October 13, 2011, 01:30:06 PM »

Sure.

This is where you'd need your /48.

Simply pick a /64 for use on each interface (assuming you wanted the interfaces to be on different subnets/networks) and away you go.
Logged
Pages: 1 [2] 3