|
Very Odd Connectivity Issue (possibly relating to other issues)
![[us]](/s/countries/us.gif) Shadow Hawkins on Thursday, 29 October 2009 17:21:39
I've been trying to troubleshoot my AYIYA tunnel, thinking that it's broken or had routing issues. However, with more digging, the issue may not be me (or even related to me) at all. I've noticed that I can ping, traceroute, and even connect to some IPv6-enabled sites, but not to others (I can't connect to SixxS via IPv6, for example; however, kame.net and ipv6.google.com both work swimmingly). I've done reverse-traceroutes (via HE's LookingGlass) to my IPv6 IP successfully from everywhere *except* Equinix Tokyo (the problem is apparently unique to Equinix Tokyo, as iAdvantage Hong Kong, which is further out, and Equinix Fremont/Dallas/Ashburn also have no issues (I chose Equinix Ashburn as it is HE's closest PoP to OCCAID Ashburn, which is the SixxS PoP I use)). Three of OCCAID's POPs are down (but so far, Ashburn isn't affected, AFAIK). I'm running Windows 7 RTM (x64) with the latest Windows console version of AICCU and latest TUN/TAP of OpenVPN listed on the Vista x64 connectivity page. However, connectivity troubleshooting has gotten a lot harder with this sort of issue.
Very Odd Connectivity Issue (possibly relating to other issues)
I can't connect to SixxS via IPv6, for example
To "SixXS", which part of it? You do realize that "SixXS" is a pretty broad and quite distributed thing I hope?
Traceroutes and tracepath's would be very useful when making any kind of statement where "some things don't work".
I've done reverse-traceroutes (via HE's LookingGlass)
You do realize that there is this very nice Traceroute from the PoPs option on this very site I hope?
Which would mean you are tracing from the actual PoPs, not from some remote network.
Three of OCCAID's POPs are down
Three? Only usewr01 is having issues at the moment and usbos01 is sometimes flaky but it works fine at the moment.
I'm running ... latest ... latest...
What exactly is "Latest"? Latest from where. Exact numbers count.
However, connectivity troubleshooting has gotten a lot harder with this sort of issue.
Without actual information (traceroutes would be a good start) there is not much anybody else can give you hints at either...
Very Odd Connectivity Issue (possibly relating to other issues)
Shadow Hawkins on Monday, 02 November 2009 05:09:41
Weirdity upon weirdity.
By merely assigning a self-created IP from my /64 to my Ethernet adapter, I straightened out the connectivity woes (on the Windows 7 side). Naturally, I'll be doing the same for my wireless connection (which I use for testing), making sure it's different *enough* not to conflict with the wired connection.
Thank the connectivity gods I don't have to do the same in OpenSuSE (which, oddly enough, Just Works).
Very Odd Connectivity Issue (possibly relating to other issues)
Shadow Hawkins on Monday, 02 November 2009 14:20:53
This is how it was with Vista too. Unless you have an IPv6 address assigned to your LAN, you could not browse the Internet
Very Odd Connectivity Issue (possibly relating to other issues)
Shadow Hawkins on Monday, 02 November 2009 15:51:19
That's where I got the idea (a user with Vista 64-bit with the same problem).
There are *at minimum* 256 possible IPs assignable/creatable out of the initial /64 assigned (four groups of four, using hex digits 0-f; this counts simply the unused groups prior to the /64 in the IPv6 block). There may be more, for all I know.
Still, two hundred and fifty six is more than any sane small-business would usually use via a single router. (Most home or even small-business routers don't even have an IPv4 pool that big.)
Very Odd Connectivity Issue (possibly relating to other issues)
Shadow Hawkins on Monday, 02 November 2009 15:58:47
from IPv6 for beginners
Just to give you an idea of what we're talking about here, a /64 network has 18,446,744,073,709,551,616 (18 quintillion) unique IPs. Of course, the first and last are not used, so you lose 2. A /48 network has 65,536 times as many. For those obsessed with how large this number is, work it out and be amazed (it's on the order of 1.2*10^24).
Very Odd Connectivity Issue (possibly relating to other issues)
Shadow Hawkins on Monday, 02 November 2009 15:58:12
Guess that didn't work like i thought it would.
I'll just do it the easy way.
A /64 network has 18,446,744,073,709,551,616 (18 quintillion) unique IPs.
Very Odd Connectivity Issue (possibly relating to other issues)
Shadow Hawkins on Tuesday, 03 November 2009 16:46:23
As I said, *way* too many for a small business to use sanely. (Heck, does *Cisco System* use that many IPs on their campus entire, which is mostly pure IPv6?)
To put that number another way, there are four hundred million mobile wireless devices in use in the United States today. (This includes cell phones, mobile hotspots, portable computers, including netbooks/notebooks/laptops with mobile connectivity built in, etc.) A single /64 could give each one a unique IP, and have room left over for every console, every *wired* computer (from the humblest laptop to the biggest mainframe), every TV, every kitchen appliance, every automobile, along with every man/woman/child/pet across the Western Hemisphere. And that's just one. (And yes, I'm including the piranhas in Peoria.)
|
![[ch]](/s/countries/ch.gif)
on Thursday, 29 October 2009 17:39:02
Posting is only allowed when you are