Welcome to Hurricane Electric's Tunnelbroker.net forums!
Started by rotxed, June 03, 2010, 02:34:32 AM
Quote from: jimb on June 03, 2010, 04:13:05 AMThere's nothing special you need to do. If you have RA set up so that the laptop is automatically configuring IPv6 addresses, then the Win7 VM box should also. If you don't have RA set up, you simply need to manually set up an IPv6 address and default router (pointed to the server's IPv6) on the Win7 VM and it should work (presuming the VM's NIC is in "bridged" mode).Of course you'll also need a DNS server which can speak IPv6.
Quote from: cholzhauer on June 03, 2010, 10:31:27 AMYeah, that makes sense.I found this page, but it only mentions linuxhttp://tldp.org/HOWTO/Linux+IPv6-HOWTO/chapter-configuring-ipv6-in-ipv4-tunnels.html
Quote from: jimb on June 03, 2010, 01:19:27 PMI presumed your server/router already had IPv6 connectivity to the internet via an HE tunnel.
Quote from: jimbNow, if for some reason that VM isn't bridged, but routed, you'll need a routed /48, and something to act as a LAN router between the VM and the LAN. Another possibility is setting up a 6in4 tunnel to the server/router, but is a bit silly on the LAN since an ethernet LAN can simply carry the IPv6 packets directly. If you need to do that though, it's very similar to the process you use to set up the HE tunnel. You set up 6in4 tunnel interface on each box with IPv6 addresses, then you can point routes through them.
Quote from: jimb on June 04, 2010, 02:21:31 AMWhat I'm really trying to tell you is that if you're running IPv6 on the LAN interface of the server/router, and the VM's NIC is bridged to that same LAN (typical), you don't need a tunnel. It should be able to send packets to the server/router directly over the ethernet, regardless of whether the laptop itself has IPv6 connectivity.If the NIC on the VM is bridged through the LAN interface on the laptop, you can think of the Win7 VM as a separate machine plugged into the same ethernet switch as the laptop and the server/router. Both IPv4 and IPv6 can be used on that LAN.A 6in4 tunnel probably isn't what you need if I understand your network topology. And if you needed to use it, the win7 box would have to be dual-stack since 6in4 uses IPv4. Or you could use something like ISATAP possibly, but that gets even more complicated.
Quote from: jimb on June 04, 2010, 03:11:28 AMAh. I sort of forgot your original intentions of a "testbed". To do what you want, that'd be either via tunneling, or something like ISATAP.Both of those can connect IPv6 islands in a sea of IPv4 only. Tunneling is typically used over the internet, WAN links, etc. 6in4 and GRE are popular methods. Setting up a tunnel is fairly trivial. It works similarly to how you set up your tunnel to HE, except you're setting up two sides. Basically, you set up the tunnels the same way, reversing the local/remote IPv4 addresses on each side, then add IPv6 addresses to each side from some /64 (typically ::1 and ::2). Now you have a virtual IPv6 link/NIC over which you can route traffic. So you can add static routes through the link, etc, for the IPv6 networks. Or run a dynamic routing protocol like OSPF. And of course as soon as you add the tunnel links to a system already running IPv6 on the LAN side, both of those boxes become routers, so now you have to make sure that forwarding is enabled, the firewall is configured to pass the traffic, etc, etc.ISATAP is intended for the LAN, to connect separate IPv6 LANs separated by an IPv4 only routing infrastructure. It uses IPv4 as a "link layer" to get IPv6 traffic across IPv4 only routers. I haven't actually implemented it so I'm not very familiar with it. I know it requires hosts which can do ISATAP (I know windows can), and uses DNS entries to find routers and/or relays used for it.Obviously, you'd want to simulate separate LANs for this, otherwise there'd be no point since IPv6 can speak natively over an ethernet LAN (ethertype 0x86DD).If you googled around, I'm sure you'd find "cookbook" instructions on how to set up tunnels or ISATAP.I doubt there are many people using ISATAP anymore though, since most LAN routers produced in the last five years or so can already route IPv6, so it's easier just to enable it (I'm talking real routers here, not consumer grade edge/internet type routers).
Quote from: jimb on June 04, 2010, 03:30:57 PMCross-OS 6in4 tunnels are entirely possible and are in use all the time.Under linux you use "ip", under Windows use use "netsh". They also have different procedures for allowing IP forwarding, etc. Just different ways to do the same exact thing under different OSes, but the resultant tunnels work the same way.
Quote from: rotxed on June 08, 2010, 12:40:16 AMOK, now I'm facing the last issue on my network configuration, that is to say: I cannot resolve names from the Win7 VM. Since this VM has only IPv6 stack enabled, I think I have two solutions:give the Win7 VM an IPv6 address for my DNS server - I can do that, and I have already tried as follows. I have assigned the IPv6 address of one of the server/router NICs, which has an IPv6 address. I can ping6 that address from the Win7 VM, but I'm still not able to resolve names.install a resolver on the dual-stack laptop with CentOS - the resolver should act simply as a query forwarder, from the Win7 VM to the server/router; I didn't try yet, I wanted to know if there are better solutions to this.What is more, I have faced a strange behaviour. If I ping6, from the Win7 VM, one of the server/router's NIC, let's say eth1 which has a static IPv6 address, nothing goes wrong. ping6 works flawlessly. The weird thing is that, if I tcpdum on eth1 while ping6 is still active, I cannot see any ICMPv6 request/reply. How come?