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

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

Cisco Router + Windows 7 on LAN

Started by mrtwrx, March 02, 2010, 06:52:30 PM

Previous topic - Next topic

mrtwrx

Hi All,

Tunnel is established on a Cisco 877, confirmed working, Windows XP PC is able to work via IPV6

Windows 7 PC is however having issues.

It receives its prefix from the router however is only intermittently able to access IPV6 sites.

debug ipv6 packet on the Cisco tells me that the packets are not hitting the Cisco.

The Windows 7 box is able to access the IPV6 sites for approx 30-60 seconds after the Cisco sends a Neighbor Discovery Packet to FF02::1 (all hosts).

I believe its a problem with the routing as the entire time the Cisco is able to ping the Windows 7 box via its Link Local address.
The Windows 7 box is able to intermittently ping the Cisco:

C:\Users\Marty>ping  fe80::21d:46ff:fe41:f583

Pinging fe80::21d:46ff:fe41:f583 with 32 bytes of data:
Destination host unreachable. (debug ipv6 packet shows the NDP packet going out now)
Reply from fe80::21d:46ff:fe41:f583: time=542ms
Reply from fe80::21d:46ff:fe41:f583: time=1ms
Reply from fe80::21d:46ff:fe41:f583: time=8ms

Ping statistics for fe80::21d:46ff:fe41:f583:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 542ms, Average = 183ms

My "guess" is that some of the inbuilt Windows7 tunnels/software is messing the routing up however it doesn't seem to show in the route table:

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination      Gateway
11    276 ::/0                     fe80::21d:46ff:fe41:f583
  1    306 ::1/128                  On-link
11     28 2001:470:d:41f::/64      On-link
11    276 2001:470:d:41f:1dc4:7d32:fd95:38de/128
                                    On-link
11    276 2001:470:d:41f:7061:3107:849d:1958/128
                                    On-link
11    276 fe80::/64                On-link
11    276 fe80::7061:3107:849d:1958/128
                                    On-link
  1    306 ff00::/8                 On-link
11    276 ff00::/8                 On-link
===========================================================================



-------

This is kind of making me go crazy :)






jimb

Seems like the issue is with the Win7 box if it works on the XP box.  I personally have no issues with XP or win7, but my router is a linux box.

My boxes also get a link local for the router (which is using radvd to advertise).  Works fine.

Seems like win7/cisco doesn't get along as far as ND.  Router discovery packets shouldn't be required except for autoconfiguration.  After that, the box should use ND to find the mac of the router, or whatever.

cholzhauer


dawkco

#3
I was having some similar problems with intermittent tunnel ops.  I was able to fix it by the following:

1.  Deleted the tunnel interface.
2.  netsh interface ipv6 reset; then reboot.
3.  Disabled the teredo and 6to4 interfaces (using netsh).
4.  Recreated the tunnel and added the routed /64 address to the NIC.

Note:  My Windows 7 is Pro 64-bit on a laptop, and it's behind a wireless NAT router.  The tunnel seems to be working fine now.  I was surprised to find that I did not have to set the IPEnableRouter registry setting, nor did I have to start and enable the Routing and Remote Access service in order to get the routed /64 to work on the NIC (the way that I had to on Windows Server 2008).

Correction Edit:  I gave HE the public external IPv4 address of the wireless router for the local tunnel endpoint; then, when I created the tunnel locally, I used the private internal gateway laptop NIC IPv4 address of the wireless router for the local tunnel endpoint, as follows:

netsh int ipv6 add v6v4tunnel "IP6Tunnel" 192.168.17.5 72.52.104.74
netsh int ipv6 add address "IP6Tunnel" 2001:470:1f04:b6c::2
netsh int ipv6 add route ::/0 "IP6Tunnel" 2001:470:1f04:b6c::1 publish=yes
netsh int ipv6 set interface "IP6Tunnel" forwarding=enabled nud=enabled routerdiscovery=enabled

The NIC settings:

netsh int ipv6 add address "Wireless" 2001:470:1f05:b6c::5
netsh int ipv6 set interface "Wireless" forwarding=enabled nud=enabled routerdiscovery=enabled
netsh int ipv6 add dnsserver "Wireless" 2001:470:1f05:a85::6
netsh int ipv6 add dnsserver "Wireless" 2001:470:1f05:a85::7 2

As I have the firewall on the Linksys wireless router disabled, I did not have to do anything regarding protocol 41.

Hope this helps somebody...

Edit:  sorry for any confusion caused prior to my correction above.
Dave W Kelly
DAWKCo(tm) Software

verdur0211

u need to telnet to the router. For telnet, go to your command prompt, type telnet IP address, if u do not know the IP address, type ipconfig first be given the IP address of the router, which is its default gateway, once u have this direction,and ask you for the pasword.