Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: [1] 2

Author Topic: External Ping Trouble  (Read 8183 times)

dshirsh

  • Newbie
  • *
  • Posts: 17
External Ping Trouble
« on: December 21, 2011, 05:13:20 AM »

Have the tunnel installed on W7 Pro 64-bit. Seems to be OK. I can ping out to he.net and ipv6.google.com with no problem. I assigned the workstation an IP from my /64 allocation. From the Internet I can ping my FIOS routers public IP and both endpoints of the tunnel. Firewall has been turned off on both the router and the workstation. When I try to ping the /64 IP from the Internet it just times out. I did a 'route print' on the workstation and the paths look OK to the gateway and my workstation. Routing issue?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2715
Re: External Ping Trouble
« Reply #1 on: December 21, 2011, 05:39:30 AM »

We're going to need more information....IP addresses, host names, ect
Logged

dshirsh

  • Newbie
  • *
  • Posts: 17
Re: External Ping Trouble
« Reply #2 on: December 21, 2011, 05:45:48 AM »

I'm away from my system right now but can you tell me what I should be using for the gateway IP on the adapter?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2715
Re: External Ping Trouble
« Reply #3 on: December 21, 2011, 05:47:02 AM »

Depends...on any host behind your router, your default gateway should be the inside interface of the router.  On your router, your default gateway should be the ::1 address of your tunnel /64
Logged

dshirsh

  • Newbie
  • *
  • Posts: 17
Re: External Ping Trouble
« Reply #4 on: December 21, 2011, 06:51:44 AM »

I'm a little confused. Does this mean that ALL my IPv4 & 6 traffic must now use the tunnel?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2715
Re: External Ping Trouble
« Reply #5 on: December 21, 2011, 06:55:18 AM »

No...your IPv4 traffic will be unaffected.

All of your IPv6 traffic would though
Logged

nickbeee

  • tunneld
  • Jr. Member
  • **
  • Posts: 72
  • I do this just for fun.
Re: External Ping Trouble
« Reply #6 on: December 21, 2011, 01:33:44 PM »

Windows 7 does not route packets between interfaces (you'll need W2008 server with Routing and Remote Access configured) so you will not be able to route to your /64. Your host IPv6 address will be your end of the tunnel (ending in ::2) and default route should be the far end of the tunnel, as defined in the sample HE script.

If you want to use your routed /64 or /48 then you will need either a router or an OS that does IPv6 routing.

HTH,


Logged
Nick B.

Tunnelling with [Open|Net|Free]BSD and IOS.
IPv6 courtesy of   HE and   Sixxs.

dshirsh

  • Newbie
  • *
  • Posts: 17
Re: External Ping Trouble
« Reply #7 on: December 21, 2011, 02:10:15 PM »

I was pretty sure that RRAS is only needed if you want dynamic routing (RIP or OSPF). Static routing is always supported.

Here's my ipconfig and routing table:


Windows IP Configuration

   Host Name . . . . . . . . . . . . : WS7
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : home

Wireless LAN adapter Wireless Network Connection 3:

   Connection-specific DNS Suffix  . : home
   Description . . . . . . . . . . . : Linksys WUSB600N Dual-Band Wireless-N USB
 Network Adapter #2
   Physical Address. . . . . . . . . : 00-1C-10-EC-30-D6
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:8:c31::2(Preferred)
   Link-local IPv6 Address . . . . . : fe80::18b8:f661:5918:73f%20(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, December 21, 2011 6:01:42 AM
   Lease Expires . . . . . . . . . . : Thursday, December 22, 2011 6:01:42 AM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 385883152
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-EF-EF-56-00-1C-10-EC-30-D6

   DNS Servers . . . . . . . . . . . : 192.168.1.1
                                       71.252.0.12
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 1C-6F-65-CC-9C-57
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::8904:962d:6155:193c%24(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.175.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 369119318
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-EF-EF-56-00-1C-10-EC-30-D6

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
8
   Physical Address. . . . . . . . . : 00-50-56-C0-00-08
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::4579:43c9:52c5:12f4%25(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.58.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 385896534
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-EF-EF-56-00-1C-10-EC-30-D6

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{7B00BC0D-3FF7-4E61-A93F-34AAE2B4235F}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter IP6Tunnel:

   Connection-specific DNS Suffix  . : home
   Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:7:c31::2(Preferred)
   Link-local IPv6 Address . . . . . : fe80::e0ef:1c7a:c57a:2377%27(Preferred)
   Default Gateway . . . . . . . . . : 2001:470:7:c31::1
   DNS Servers . . . . . . . . . . . : 192.168.1.1
                                       71.252.0.12
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{3ED2CC55-8496-4FD8-8401-FEE1BB3C4AD3}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.home:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : home
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{01AE18EE-4A2A-4FBA-B1F7-AD6B5F8783F8}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #6
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Dave>route print
===========================================================================
Interface List
 20...00 1c 10 ec 30 d6 ......Linksys WUSB600N Dual-Band Wireless-N USB Network
Adapter #2
 19...1c 6f 65 cc 9c 57 ......Realtek PCIe GBE Family Controller
 24...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
 25...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
  1...........................Software Loopback Interface 1
 16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
 27...00 00 00 00 00 00 00 e0 Microsoft Direct Point-to-point Adapater
 15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
 28...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5
 26...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #6
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1      192.168.1.3     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.1.0    255.255.255.0         On-link       192.168.1.3    281
      192.168.1.3  255.255.255.255         On-link       192.168.1.3    281
    192.168.1.255  255.255.255.255         On-link       192.168.1.3    281
     192.168.58.0    255.255.255.0         On-link      192.168.58.1    276
     192.168.58.1  255.255.255.255         On-link      192.168.58.1    276
   192.168.58.255  255.255.255.255         On-link      192.168.58.1    276
    192.168.175.0    255.255.255.0         On-link     192.168.175.1    276
    192.168.175.1  255.255.255.255         On-link     192.168.175.1    276
  192.168.175.255  255.255.255.255         On-link     192.168.175.1    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link     192.168.175.1    276
        224.0.0.0        240.0.0.0         On-link      192.168.58.1    276
        224.0.0.0        240.0.0.0         On-link       192.168.1.3    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link     192.168.175.1    276
  255.255.255.255  255.255.255.255         On-link      192.168.58.1    276
  255.255.255.255  255.255.255.255         On-link       192.168.1.3    281
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0         10.1.1.1  Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 27    261 ::/0                     2001:470:7:c31::1
  1    306 ::1/128                  On-link
 27    261 2001:470:7:c31::/64      On-link
 27    261 2001:470:7:c31::2/128    On-link
 20    281 2001:470:8:c31::/64      On-link
 20    281 2001:470:8:c31::2/128    On-link
 27    261 fe80::/64                On-link
 24    276 fe80::/64                On-link
 25    276 fe80::/64                On-link
 20    281 fe80::/64                On-link
 20    281 fe80::18b8:f661:5918:73f/128
                                    On-link
 25    276 fe80::4579:43c9:52c5:12f4/128
                                    On-link
 24    276 fe80::8904:962d:6155:193c/128
                                    On-link
 27    261 fe80::e0ef:1c7a:c57a:2377/128
                                    On-link
  1    306 ff00::/8                 On-link
 27    261 ff00::/8                 On-link
 24    276 ff00::/8                 On-link
 25    276 ff00::/8                 On-link
 20    281 ff00::/8                 On-link
===========================================================================
Persistent Routes:
 If Metric Network Destination      Gateway
  0 4294967295 ::/0                     2001:470:7:c31::1
===========================================================================
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2715
Re: External Ping Trouble
« Reply #8 on: December 21, 2011, 02:19:02 PM »

I was pretty sure that RRAS is only needed if you want dynamic routing (RIP or OSPF). Static routing is always supported.

That's what I thought too

I think you're right...there's a routing problem with your /64.  I would email ipv6@he.net and see what they can do for you

Also, I would disabled all that isatap stuff on your computer...at the very least it'll make things easier to read
Logged

dshirsh

  • Newbie
  • *
  • Posts: 17
Re: External Ping Trouble
« Reply #9 on: December 21, 2011, 02:43:27 PM »

Thanks. BTW, RRAS is required only if you are routing between subnets.
Logged

nickbeee

  • tunneld
  • Jr. Member
  • **
  • Posts: 72
  • I do this just for fun.
Re: External Ping Trouble
« Reply #10 on: December 21, 2011, 04:07:02 PM »

Thanks. BTW, RRAS is required only if you are routing between subnets.

As I understood it you were wanting to route between subnets - your tunnel /64 and your routed /64 block(on your wireless LAN adaptor)?

Quote
27    261 ::/0                     2001:470:7:c31::1
Looks like your default route points to the tunnel /64 (OK) but I don't see a route anywhere for your routed /64.

Quote
IPv6 Address. . . . . . . . . . . : 2001:470:8:c31::2(Preferred)
I can't see any routes to this one - your routed /64 - in the routing table.



I stand corrected on the routing configuration  :-\ apparently there is a registry hack mentioned here to enable routing for IPv4, as well as a useful link to MS tcp/ip reference book. (yeah I forgot about the old Windows Internet Connection Sharing...) And as for dynamic routing - they did away with OSPF in 2008 server and left us with RIP v2  :'(

Logged
Nick B.

Tunnelling with [Open|Net|Free]BSD and IOS.
IPv6 courtesy of   HE and   Sixxs.

dshirsh

  • Newbie
  • *
  • Posts: 17
Re: External Ping Trouble
« Reply #11 on: December 21, 2011, 04:31:46 PM »

OK, Broque in tech support rechecked my route setting at the top end. Looked fine.

I was sure there was a route listed in the table. If you look below you'll see the /64 and /128 entry for the address as on-link. Do I need some other route specified?
Logged

dshirsh

  • Newbie
  • *
  • Posts: 17
Re: External Ping Trouble
« Reply #12 on: December 22, 2011, 05:06:52 AM »

Hmmm...... do I really want to assign the /64 address to my wireless adapter or do I need to add it to the tunnel adapter instead? This should be a rather vanilla scenario but it's got me somewhat frazzled.
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2715
Re: External Ping Trouble
« Reply #13 on: December 22, 2011, 05:14:31 AM »

Assuming you have two /64's :

2001:470:db8:1234::/64 is your tunnel /64
2001:470:db8:abcd::/64 is your routed /64

The ONLY place 2001:470:db8:1234::/64 is used is on your tunnel interface.  2001:470:db8:1234::1/64 is used on the HE side, and you assign 2001:470:db8:1234::2/64 to the tunnel interface on your side.  The default gateway on your tunnel adapter is 2001:470:db8:1234::1/64
You can use 2001:470:db8:abcd::1/64 on your wireless interface.  Your default gateway is your tunnel adapter (I don't know if you can route to an interface in Windows or not)  (I may have messed that up earlier)

Logged

dshirsh

  • Newbie
  • *
  • Posts: 17
Re: External Ping Trouble
« Reply #14 on: December 22, 2011, 06:39:47 PM »

Out of curiousity I went back and rechecked how I did the web server exercise for the cert test. Turns out that I used the IPv6 client endpoint address for the web server address. Worked fine for that exercise as well as the mail server exercise. Why wouldn't HE require the user to make use of their /64 address bank and set up a real IPv6 address? Probably because it's not real feasible.

Am I chasing my tail here? It has to be a routing issue but at what level?
Logged
Pages: [1] 2