Ticket ID: SIXXS #1323371 Ticket Status: User PoP: (not applicable)
New user.... sorry to be a bother.
Shadow Hawkins on Sunday, 10 January 2010 19:29:16
Kind sirs:
I'm stumped. First I tried connecting from Windows 7. That didn't work - possibly because Windows 7 creates a Taredo tunnel to Microsoft by default.
Because the MS default IPv6 address for the Tarendo tunnel take up the address space my Hurricane IPv6# wants, I'd need to delete that address. Unfortunately I don't know how to do that and can't locate clear, step by step instructions for command line - or a gui tool to do the job for me.
So I tried XP. I'm behind a DSL model (ATT ADSL w. Siemens 4100) and a router (DLINK DGL-4100). My LAN is behind the NAT in the DGL-4100 and I was unable to change my IP address for my Hurricane Tunnel to my lan-side address frm the DHCP server on my DGL-4100. That didn't work either.
I tried troubleshooting why your server could't ping my LAN-side address and decided that Norton Antivirus is probably the culprit.
My Windows Firewall is turned off by NAV and NAV doesn't give end users much discretionary control over adjusting NAV's firewall rules or creating exceptions. So unless you guys can help me figure out how to communicate successfully with your IPc6 server and DNA around my DSL modem and DGL-4100, I'm dead in the water.
Here's my account information so you know who I am on your side:
Logged in as Robert Louis Blomeyer Junior (RLBJ1-SIXXS)
SSL IPv4 connection from 70.131.127.251 (My Speedstream 4100's ex. address)
Tunnel Name My First Tunnel
PoP Name uschi02
PoP Location Chicago, Illinois, United States United States
PoP IPv4 216.14.98.22
TIC Server tic.sixxs.net (default in AICCU)
Your Location Lisle Illinois, United States United States
Your IPv4 AYIYA, currently 0.0.0.0
IPv6 Prefix 2001:4978:f:402::1/64
PoP IPv6 2001:4978:f:402::1
Your IPv6 2001:4978:f:402::2
Created 2010-01-07 16:37:02 CET
State AYIYA (automatically enabled on the fly)
uschi02
Location:Chicago, Illinois, United States United States (.us)
Hostname:uschi02.sixxs.net
Status:Up
Heartbeat support:Yes
AYIYA support:Yes
tinc support:No
Multicast support:No
m6bone connected:No
Active Tunnels:936
Active Subnets:351
Public:Yes
Statistics:Latency/Loss, Traffic
Issue Tracker:Issues?
This PoP provides tunnels from the following prefixes:
* 2001:4978:f::/48 of size /64
Subnets are allocated out of:
* 2001:4978:100::/40 of size /48
* 2001:4978:200::/40 of size /48
I don't know what additional information you guys will want. But I'm pretty sure you'll want to know more about my side of the router.
My initial attempts at using IPv6 employ wired connections, in an attempt to minimize additional complications from three wireless access points on my LAN.
Various machines in on the LAN can boot XP SP3, Windows 7 Ultimate & Pro, and Ubuntu linux.
One last thought... RIP is NOT activated on my DGL-4100. (Does it need to be?) My routing info is:
Destination IP Netmask Gateway Metric Interface Creator
70.131.127.0 255.255.255.00.0.0.01WANSystem
0.0.0.00.0.0.0 70.131.127.25015 WANSystem
192.168.123.0 255.255.255.00.0.0.01LANSystem
Get back to me with whatever else you need to know and I'll try to work through whatever it may be with you.
Thanks for your patient consideration.
Bob Blomeyer (BobBl)
P.S. It would really be great if someone would publish a GNU or other Open Source tool or script to remove the default Teredo tunnel address from Windows 7 and set the address from IPv6 providers like yourselves (NOT MS) into the available Windows 7 IPv6 address space. Something like that would assist lots of new Windows 7 users to make the switch to IPv6 without unnecessary muss, fuss or bother.
State change: user
Jeroen Massar on Sunday, 10 January 2010 23:54:10
The state of this ticket has been changed to user
New user.... sorry to be a bother.
Jeroen Massar on Monday, 11 January 2010 00:25:39
[Please use the forums for these kind of questions, as there is nothing wrong with our side.]
I'm stumped. First I tried connecting from Windows 7. That didn't work - possibly because Windows 7 creates a Taredo tunnel to Microsoft by default.
The Wiki explains exactly how to do that. Also, Teredo tunnels are not 'created to Microsoft', please read the Wikipedia entry on Teredo for a good description of how it works.
Microsoft only provides the server which is used for bootstrapping Teredo, actual data goes through an anycasted node.
Because the MS default IPv6 address for the Tarendo tunnel take up the address space my Hurricane IPv6# wants, I'd need to delete that address.
What is "Hurricane"?
Unfortunately I don't know how to do that and can't locate clear, step by step instructions for command line - or a gui tool to do the job for me.
Try Google, the forums here and of course read the Wiki.
So I tried XP. I'm behind a DSL model (ATT ADSL w. Siemens 4100) and a router (DLINK DGL-4100). My LAN is behind the NAT in the DGL-4100 and I was unable to change my IP address for my Hurricane Tunnel to my lan-side address frm the DHCP server on my DGL-4100. That didn't work either.
What is a "Hurricane Tunnel"?
I tried troubleshooting why your server could't ping my LAN-side address and decided that Norton Antivirus is probably the culprit.
You will have to either upgrade it to an IPv6 capable version or completely de-install it for IPv6 to work.
My Windows Firewall is turned off by NAV and NAV doesn't give end users much discretionary control over adjusting NAV's firewall rules or creating exceptions. So unless you guys can help me figure out how to communicate successfully with your IPc6 server and DNA around my DSL modem and DGL-4100, I'm dead in the water.
See the forums.
One last thought... RIP is NOT activated on my DGL-4100. (Does it need to be?) My routing info is:
Unless your IPv4 operator requires you to use that you won't need it.
P.S. It would really be great if someone would publish a GNU or other Open Source tool or script to remove the default Teredo tunnel address from Windows 7 and set the address from IPv6 providers like yourselves (NOT MS) into the available Windows 7 IPv6 address space. Something like that would assist lots of new Windows 7 users to make the switch to IPv6 without unnecessary muss, fuss or bother.
Teredo actually solves that problem completely already as it is capable of automatically creating a properly working IPv6 connection. The only problem is that your anti-virus tool is most likely breaking a lot of programs that actually want to use it.
As for removing Teredo: netsh int ipv6 teredo disable
See the wiki & FAQ for more details.
Posting is only allowed when you are logged in. |