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

How to add/set route from Routed /64 to Tunnel Endpoint?

Started by dawkco, April 03, 2010, 04:22:28 PM

Previous topic - Next topic

Sandertjuhh

Sorry I forgot to tell  :o my bad.

On my "server" system i could ping 2001:470:1f14:132f::1
On my second computer I can't

I've posted the routing table already in my first post in this topic

cholzhauer

Ah.  I had no idea what that routing table was from.

Your default route looks incorrect..how are you assigning addresses?  The default gateway should point to the fe80 address of your IPv6 tunnel server.

Sandertjuhh

#62
I'am assigning addresses with the commands dawkco posted before.

For the system where I post the routing table from is it just like:

netsh int ipv6 add address "Draadloze netwerkverbinding" 2001:470:1f14:132f::6
netsh int ipv6 set interface "Draadloze netwerkverbinding" forwarding=enabled nud=enabled routerdiscovery=enabled


[update]
I've put my fe80 address as the default gateway for my "Draadloze netwerkverbinding" IPv6 Protocol
I don't know where this Link-Lokal address came from but anyhow

My new route table looks like this:

C:\Users\Sandertjuhh>netsh int ipv6 show route

Public.  Type      Met  Voorvoegsel               Idx  Naam gateway/interface
-------  --------  ---  ------------------------  ---  ------------------------
Nee      Handmatig 256  ::/0                       12  fe80::f967:6fda:ee5:eebc
Nee      Handmatig 256  ::1/128                     1  Loopback Pseudo-Interface
1
Nee      Handmatig 256  2001:470:1f14:132f::/64    12  Draadloze netwerkverbinding
Nee      Handmatig 256  2001:470:1f14:132f::6/128   12  Draadloze netwerkverbinding
Nee      Handmatig 256  fe80::/64                  14  Bluetooth-netwerkverbinding
Nee      Handmatig 256  fe80::/64                  12  Draadloze netwerkverbinding
Nee      Handmatig 256  fe80::/64                  11  LAN-verbinding
Nee      Handmatig 256  fe80::25e3:b5f5:a977:6aad/128   14  Bluetooth-netwerkverbinding
Nee      Handmatig 256  fe80::415b:1088:4741:91dc/128   11  LAN-verbinding
Nee      Handmatig 256  fe80::f9bb:941e:531:e179/128   12  Draadloze netwerkverbinding
Nee      Handmatig 256  ff00::/8                    1  Loopback Pseudo-Interface
1
Nee      Handmatig 256  ff00::/8                   14  Bluetooth-netwerkverbinding
Nee      Handmatig 256  ff00::/8                   12  Draadloze netwerkverbinding
Nee      Handmatig 256  ff00::/8                   11  LAN-verbinding

[/update]

cholzhauer

I'm confused...why are you enabling routing on a machine that's not a router?  Furthermore, why are you assigning a static address if your intention is to use RA on your tunnel server to hand out addresses?

Sandertjuhh

I'm not enabling routing on my second computer as far as I know.
I only had enabled RRAS on my first computer where the tunnel works already.

I'm give my router computer and my second computer a static IPv6 address because without IPv6 don't even work on my "server" system. (Yeah I could ping without a static IPv6 but not browse). And dawkco told in his post to do so.. So I was trying to work out his solution.

Maybe RA doesn't hand out addresses. I'm only enabled that server and not configured anything on it (as dawkco told in his post).

___


But for some strange reason its working now. I didn't change anything!

Sandertjuhh

And for some reason it isn't really stable..

Sometimes it works... And sometimes it doesn't after a while its working again without doing anything! Does somebody has any tips for this problem?

dawkco

Quote from: Sandertjuhh
somebody has any tips for this problem?

Sandertjuhh - sorry, I did not include instructions for the other computers on your LAN.  There are two scenarios:  (1) the computers on your LAN connect to your tunnel server via a network switch; (2) the computers on your LAN connect to your tunnel server via a router.

The network switch scenario (1) is easy; the router scenario (2) is more complicated (requires a subnetted routed/48 and a local tunnel) and is apparently (from my experience) limited to a connection from one computer (because of the single external address on the router).  The following settings, along with those in my past post should help fill in the missing pieces.

Network Switch scenario;
Your (network switched) LAN computer IPv6 NIC Setup, including route to your tunnel server (Vista/WS2008/Win7):


netsh interface teredo set state disabled
netsh interface ipv6 6to4 set state disabled
netsh interface ipv6 isatap set state disabled
netsh interface ipv6 add address "Local Area Connection" <your_other_/64_ipv6_addr>
netsh interface ipv6 add route ::/0 "Local Area Connection" <your_tunnelsrv_/64_ipv6_addr> publish=yes
netsh interface ipv6 add route <your_/64_ipv6_prefix> "Local Area Connection"
netsh interface ipv6 set interface "Local Area Connection" forwarding=enabled nud=enabled routerdiscovery=enabled
netsh interface ipv6 add dnsserver "Local Area Connection" <dns_server1_ipv6_addr>
netsh interface ipv6 add dnsserver "Local Area Connection" <dns_server1_ipv6_addr> 2


Example excerpt from our setup:


netsh interface ipv6 add address "Local Area Connection" 2001:470:1f05:a85::7
netsh interface ipv6 add route ::/0 "Local Area Connection" 2001:470:1f05:a85::6 publish=yes
netsh interface ipv6 add route 2001:470:1f05:a85::/64 "Local Area Connection"


Here's the Local Router scenario;
Your tunnel server to Local Router IPv6-in-IPv4 Tunnel Setup:


netsh interface ipv6 add v6v4tunnel "Router IPv6 Tunnel" <your_tunsrv_endpt_ipv4_addr> <local_router_ext_ipv4_addr>
netsh interface ipv6 add address "Router IPv6 Tunnel" <your_tunsrv_endpt_/64#2(from/48)_ipv6_addr> preferredlifetime=0s
netsh interface ipv6 add route <your_/64#3(from/48)_ipv6_prefix> "Router IPv6 Tunnel" <your_machine_endpt_/64#2(from/48)_ipv6_addr> publish=yes
netsh interface ipv6 set interface "Router IPv6 Tunnel" forwarding=enabled nud=enabled routerdiscovery=enabled


Example excerpt from our setup:


netsh interface ipv6 add v6v4tunnel "Router IPv6 Tunnel" 65.168.232.6 65.168.232.5
netsh interface ipv6 add address "Router IPv6 Tunnel" 2001:470:8224:1::1 preferredlifetime=0s
netsh interface ipv6 add route 2001:470:8224:2::/64 "Router IPv6 Tunnel" 2001:470:8224:1::2 publish=yes


Your computer (on routed LAN) to your tunnel server IPv6-in-IPv4 Tunnel Setup (Vista/WS2008/Win7):


netsh interface teredo set state disabled
netsh interface ipv6 6to4 set state disabled
netsh interface ipv6 isatap set state disabled
netsh interface ipv6 add v6v4tunnel "Router IPv6 Tunnel" <your_machine_private_endpt_ipv4_addr> <your_tunsrv_endpt_ipv4_addr>
netsh interface ipv6 add address "Router IPv6 Tunnel" <your_machine_endpt_/64#2(from/48)_ipv6_addr> preferredlifetime=0s
netsh interface ipv6 add route ::/0 "Router IPv6 Tunnel" <your_tunsrv_endpt_/64#2(from/48)_ipv6_addr> publish=yes
netsh interface ipv6 set interface "Router IPv6 Tunnel" forwarding=enabled nud=enabled routerdiscovery=enabled


Example excerpt from our setup:


netsh interface ipv6 add v6v4tunnel "Router IPv6 Tunnel" 192.168.17.5 65.168.232.6
netsh interface ipv6 add address "Router IPv6 Tunnel" 2001:470:8224:1::2 preferredlifetime=0s
netsh interface ipv6 add route ::/0 "Router IPv6 Tunnel" 2001:470:8224:1::1 publish=yes


Your computer (on routed LAN) IPv6 NIC Setup:


netsh interface ipv6 add address "Local Area Connection" <your_machine_/64#3(from/48)_ipv6_addr>
netsh interface ipv6 set interface "Local Area Connection" forwarding=enabled nud=enabled routerdiscovery=enabled
netsh interface ipv6 add dnsserver "Local Area Connection" <dns_server1_ipv6_addr>
netsh interface ipv6 add dnsserver "Local Area Connection" <dns_server2_ipv6_addr> 2


Example excerpt from our setup:


netsh interface ipv6 add address "Local Area Connection" 2001:470:8224:2::5

Dave W Kelly
DAWKCo(tm) Software

dawkco

Quote from: Sandertjuhh
And for some reason it isn't really stable..

Sometimes it works... And sometimes it doesn't...


Sandertjuhh, if you've been fooling around with different settings (adding, changing, removing, re-adding etc.), you may have to reset the IPv6 configuration and start over.  It works best if you start from scratch and apply the correct settings in a step-by-step methodical manner.  Then, don't touch it again.  If you do a reset, be ready to redo the setup with your notes in hand because it literally wipes out everything from IPv6.

To reset the IPv6 configuration:


netsh int ipv6 reset


Note:  If I remember correctly, it makes you reboot the computer after the reset.

Dave W Kelly
DAWKCo(tm) Software