Text only | Text with Images

Hurricane Electric's IPv6 Tunnel Broker Forums

General IPv6 Topics => IPv6 on Windows => Topic started by: Dakara on March 19, 2014, 10:30:27 PM

Title: Windows 7 Behind a Cisco ASA-5505
Post by: Dakara on March 19, 2014, 10:30:27 PM
Hi Guys,

Just wanted to play around with IPv6 and as the ASA doesn't support Tunnel Interfaces, I tried on Win7 to no avail.

I have a rule in the ASA for any Internal Device to Tunnel Protocol 41 to the HE IPv4 Endpoint and I can see the Hits on this rule Increment, so the routes for Windows must be right, I just don't see any response come back?

Any help would be appreciated. If you need more info from my end, just let me know.


Thanks.


Title: Re: Windows 7 Behind a Cisco ASA-5505
Post by: broquea on March 19, 2014, 10:35:07 PM
What commands did you run on your windows machine?
What was the rule you wrote on the ASA?
Title: Re: Windows 7 Behind a Cisco ASA-5505
Post by: cholzhauer on March 20, 2014, 05:18:02 AM
What version of the OS are you running?
Title: Re: Windows 7 Behind a Cisco ASA-5505
Post by: Dakara on March 20, 2014, 09:47:54 AM
Win7 commands:

netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 192.168.0.2 (HE IPv4 Address)
netsh interface ipv6 add address IP6Tunnel 2001:470:x:x::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:x:x::1


ASA is 9.1(4)

access-list Internal_access_in extended permit object Protocol_41 192.168.0.0 255.255.255.0 object tserv1.nyc4.he.net


Thanks.


Title: Re: Windows 7 Behind a Cisco ASA-5505
Post by: broquea on March 20, 2014, 10:35:38 AM
And your object of "Protocol_41" is actually specified how, like below?

Code Select
object service Protocol_41
service 41
Title: Re: Windows 7 Behind a Cisco ASA-5505
Post by: Dakara on March 20, 2014, 08:08:08 PM
Correct.

Thanks.


Text only | Text with Images