HNHacker News
TopNewBestAskShowJobs

zaphoyd

890 karma · joined February 12, 2010

email: hackernews@zaphoyd.com web: https://www.zaphoyd.com

[ my public key: https://keybase.io/zaphoyd; my proof: https://keybase.io/zaphoyd/sigs/7AwrXTTBUkPTzTgg12WEOisWDxg1xGo8hftKyhNPImI ]

submissionscomments
zaphoyd··on World IPv6 Day: firing up the engines on the new Internet protocol
This is referred to as NAT64/DNS64 (http://en.wikipedia.org/wiki/IPv6_transition_mechanisms#NAT6...) and is the strategy many mobile phone networks (such as T-Mobile USA) are taking.

Effectively they give devices IPv6 addresses only and run a DNS server that makes up "fake" IPv6 addresses for all of the v4 only DNS records. It works well except when applications embed IPv4 literals (as they won't go through the DNS system and get translated)

zaphoyd··on World IPv6 Day: firing up the engines on the new Internet protocol
Sorry, I meant DIR-615/825 not 655/855. You are correct, the 655 does not support IPv6 at the moment. According to Dlink support forums in 2009 there were plans for the 655 to get upgraded but I haven't heard anything since.

Note: the way Dlink has done the IPv6 upgrades on the other models is by releasing a new hardware revision. So DIR-615 Rev C,D, and E supports IPv6, but Rev A and B don't. =\

zaphoyd··on World IPv6 Day: firing up the engines on the new Internet protocol
It makes sense only in the abstract. Once you look at the details of how IPv4 was implemented, it is clear that such an idea makes no sense at all. All IPv4 devices and software are hard coded to use 32 bit addresses. No more and no less. No amount of "design" can make 128 bits fit into 32 short of having designed IPv4 with bigger (or variable length) addresses in the first place.

To have an "extended IPv4 space" you must change all hardware and all software to be aware of that extended space. Hardware/software/networks that haven't been changed yet won't be able to use or route "extended" IPv4 packets. Such a situation has all of the same problems as IPv6.

Given those fundamental limitations plenty has been done to make inter-operating between protocols work as well as possible.

The ::ffff:/96 space was set aside as the "IPv4 embedded in IPv6" space (http://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses) so that IPv6 aware software can talk about IPv4 addresses. Though cannot talk to them because there is no way to encode the 128 bit return address in the 32 bit field.

IPv4 was extended with the protocol 41 header option to allow two IPv6 systems to exchange IPv6 packets over the existing IPv4 network (this is how 6to4 and teredo/6in4(tunnelbroker) systems work). This effectively means that anyone with a public IPv4 address (or in the case of teredo even some systems behind NAT4) can talk to IPv6 machines albeit through translation mechanisms that can hurt performance.

zaphoyd··on World IPv6 Day: firing up the engines on the new Internet protocol
Lets hope "World IPv6 Day" goes smoothly enough that they can drop some of those restrictions. =)
zaphoyd··on World IPv6 Day: firing up the engines on the new Internet protocol
This is actually not true anymore.

Off the top of my head all Apple Airport Express/Extreme/Time Capsule routers, DLink 601/655/855, linksys WRT610N/E3000. All support IPv6, most of those let you configure the router as 6to4 or 6in4 (tunnelbroker, etc) tunnel endpoint as well. The DLink ones even support a stateful DHCPv6 server to provide specific v6 address ranges to your LAN clients.

The support on the most recent revisions often isn't just limited to firmware either. The Dlink routers have IPv6 ready logos on the box and instructions for IPv6 features in the manual. You can pick these routers up in your local Best Buy or Office Depot and the v6 support is not limited to the high end ones either.

I am sure there are more than those that I have listed, they are just the ones that I have personally used for home IPv6 stuff.

zaphoyd··on World IPv6 Day: firing up the engines on the new Internet protocol
That counter is when global registries have allocated everything, not strictly when all useable addresses are in use. IPv4 addresses will never "run out", they will just get more expensive and complicated to use until the point where IPv6 is cheaper and easier. IANA exhaustion is just one big milestone along that path.
zaphoyd··on World IPv6 Day: Solving the IP Address Chicken-and-Egg Challenge
The risk is much smaller today than it was when the ipv6 whitelists for google, etc were originally set up. All patched modern operating systems and browsers have corrected the behavior that originally caused this (preferring automatic v6 tunnels over native v4) so that the only brokenness remaining in theory is outdated software and improperly configured manual tunnels.

See http://fud.no/ipv6/ for more information on measurements of this issue as browsers and oses fixed this problem.

zaphoyd··on World IPv6 Day: firing up the engines on the new Internet protocol
http://test-ipv6.com/ gives you a bit more info about exactly what is working and what isn't in regards to your v6 connection.
zaphoyd··on [dead]
In general, a /64 is being assigned in a similar way to a single IPv4 address is used today. Blacklisting a /64 would be similar to blacklisting a single IPv4 with multiple machines behind a NAT.

If anything this gives us more control. You can start by blacklisting individual v6 addresses, and if you notice an above average number are from the same /64 knock off the whole thing.

zaphoyd··on Why Wesabe Lost to Mint
I completely agree here. Mint is too simple and automates too much that shouldn't be automated. I have been toying around a web based finance project of my own and if you'd be interested I'd love to talk more about what exactly you might find useful.
zaphoyd··on Why Wesabe Lost to Mint
I firmly agree with Marc on the issue that to be truly effective personal finance requires people to work more closely with their data. I have been working on a web project of my own for my own personal finance use, as neither Mint, Wesabe, or other web based product do what I needed. The most common response from people I show it to is that it looks really helpful but that they don't have the discipline to organize their finances enough to be useful.

Mint definitely got the "no user thought required" down and this path has brought them [some] financial success. Is their overly simplified view of a complex process actually useful? The consensus for mass market web based personal finance systems so far seems to be

- Users don't care about privacy.

- Users don't care about data accuracy

- Users don't care about digging into their data at all.

- Users will pay for pretty graphs/charts with questionably-useful automatic analysis that is unlikely to make a significant difference in their financial situation.

What is the best thing to do in this case? Just give users what they want? Sell illusions because reality is too hard to deal with? I know there are some people who do care, how do you find them?

zaphoyd··on Ask HN: What does your development environment look like?
There is a lot more to a monitor than it's physical dimensions. The 27 inch display that you linked has a similar or lower resolution than most 23/24 inch displays and is a tn panel with limited viewing angle, color reproduction, and overall clarity. There are many good options for quality 24 inch (1920x1200) panels at reasonable prices but 27/30 inch panels at resolutions that make those inches worth having (2560x1600) are still quite pricy.
← PreviousPage 9 of 9