Slashdot Mirror

Sure there are good routers out there -- but do they have all of the protocol support the Apple routers have?

I mean, it if doesn't have Bonjour Sleep Proxy or Wide Area Bonjour (and yes, I use both), regular Bonjour advertisements (for services provided by the router itself), and doesn't have Airplay support, then I'm _losing functionality_. A small speed bump doesn't make up for that.

Besides which, Amplifi's IPv6 support is anemic compared to Apple's. According to their own docs they only support DHCPv6 and 6to4. It doesn't appear to support setting up a manual tunnel to something like tunnelbroker.net. I can only assume it supports ICMPv6 RA's (it would seem to be pretty dumb if it didn't), but that doesn't seem to be an option in their configuration.

So "blows out of the water" seems a rather overblown statement right now. I agree however that it would be awesome if Apple teamed up with Amplifi to get these technologies into their routers as a suitable replacement to Apple's APs (the code for all of them is Open Source, so there are no reasons why it can't be done).

Yaz

err tunnelbroker

http://tunnelbroker.net/

I'll be interested in the Internet of Things as soon as I can get an IPv6 address for my balls.

Then rejoice! Hurricane Electric will give you your own /48 for free. Just set up a box to accept and route it and you can assign an IP to every single sperm in your beloved balls.

I've been getting up to speed on IPv6 and have a tunnel from he.net (tunnelbroker.net). It seems to pop out somewhere on the other side of the Atlantic, judging from geographically targeted advertising. Several big sites are already IPv6 enabled (Firefox plugin SixOrNot), e.g. Facebook, Google, Youtube.

http://en.wikipedia.org/wiki/NAT64

Interestingly, it was discussed in a forum topic on Tunnelbroker:
http://www.tunnelbroker.net/forums/index.php?topic=2419.0

I run the Firefox plugin SixOrNot. Google - a green 6. Youtube and Facebook ditto. Slashdot, a red 4. There are major sites out there running IPv6.

I have a free tunnel from Hurricane Electric. The only issue is that Google thinks I'm in the USA, which can't be a bad thing.

Now that there are no more IPv4 addresses available in Europe, it's in the interests of the established players to suppress IPv6 and lock out disruptive new startups: e.g. ISP's or Co-Lo's.

You can always set up a tunnel broker if you want to play around with IPv6. It's ugly and messy, but it gets you on the network. I've been using this very service for over two years now and have never had a problem with it. As far as supported devices, I have an original 2G iPhone, a Nintendo Wii, an ancient Sharp Zarius, and a pair of TiVos that don't support IPv6, but everything else was able to autoconfigure an address and use it right away.

Also, it is entirely possible to run a pure IPv6 network today though a combination of DNS and packet translation. Basically, your IPv6 only hosts do a name lookup for a host using the local DNS server. The server queries but only finds a A record, which it then translates into a AAAA record by appending a well known prefix and returns that to the host. That host then opens a socket to the IPv6 address specified and sends the packet through a static NAT setup on your gateway to translate the packets back to IPv4, and also translate return packets to IPv6. It sounds esoteric, but this setup works (I use it in an IPv6 only test environment) and isn't hard to configure at all if you're using a Linux gateway. I've been using the Trick or Treat Daemon for DNS conversions and Tayga for the IP packet translation.

Forgot to hit the "Post Anonymously" button again?

For the benefit of others.

Try visiting http://[::ffff:216.34.181.45]/ - didn't link it as slashdot fucks up IPv6 literals.

For quality IP6 connectivity, you also need to accept the multicast address space in INPUT chain, or at least parts of it. Good old ICMP is also nice, your policy allowing:

    ip6tables -A INPUT -d ff00::/8 -j ACCEPT # Multicasts are necessary and nice
    ip6tables -A INPUT -p icmpv6 -j ACCEPT # ICMPs make us all quite happy

For example, the IPv6 replacement of IPv4 ARP is performed using IPv6 link-local multicast, among other thingies.
Firewall policies on (even the upstream) links must understand the IPv6 specific requirements for accepting inbound multicasts for the fullest IPv6 experience.

When your local ISP still does not offer native IPv6 addressing and traffic, a good way to start using IPv6 is to get a free 6to4-tunnel from Hurricane Electric .

Try it, with a tunnel.

IPv6 works pretty well with XP, there are quite a few sites already available over IPv6. A lot more are ready for IPv6 but don't enable it because about 0.1% of clients have broken IPv6 connections that look like they should work, but don't.

Of course, IPv4 won't be turned off for a VERY long time, I'd bet at least 20 years, probably longer.

[Disclaimer: I am a pfSense developer, so I'm a bit biased. For those of you who don't know what pfSense is, it's a BSD-based firewall distribution.]

pfSense 2.0 won't officially support IPv6, but there is a branch available that does IPv6 which will later become 2.1. I'm running it on my home router with a GIF tunnel to Hurricane Electric ( http://he.net/ http://tunnelbroker.net/) to get IPv6 even though my ISPs do not have any native IPv6 support yet. The IPv6 support is a work in progress but is complete enough that it will do what most people want/need.

Instructions for the setup and more info can be found on the pfSense IPv6 board here: http://forum.pfsense.org/index.php/board,52.0.html

I get a 10/10 on the IPv6 tests from http://test-ipv6.com/ on all my PCs as well as my Droid X running 2.3.3. If you're already using pfSense 2.0, give the IPv6 code a try, setup a tunnel to he.net, and enjoy. Doesn't take too long at all to setup.

If you want IPv6 before lame, slow ISPs finally get it, try using tunnels through someone like,

http://tunnelbroker.net/

I've been using Hurricane Electric to tunnel IPv6 for years and it works well.

See my comment later in the post here. You can get a free IPv6 tunnel from http://tunnelbroker.net/ if you have a router/firewall capable of establishing a GIF tunnel. pfSense (2.0 with the IPv6 code branch), m0n0wall, and DD-WRT and friends can do this.

I posted a comment much like this in the last IPv6 thread, but here it goes again. :-)

[Disclaimer: I am a pfSense developer, so I'm a bit biased. For those of you who don't know what pfSense is, it's a BSD-based firewall distribution.]

pfSense 2.0 won't officially support IPv6, but there is a branch available that does IPv6 which will later become 2.1. I'm running it on my home router with a GIF tunnel to Hurricane Electric (http://he.net, http://tunnelbroker.net/) to get IPv6 even though my ISPs do not have any native IPv6 support yet. The IPv6 support is a work in progress but is complete enough that it will do what most people want/need.

Instructions for the setup and more info can be found on the pfSense IPv6 board here: http://forum.pfsense.org/index.php/board,52.0.html

I get a 10/10 on the IPv6 tests from http://test-ipv6.com/ on all my PCs as well as my Droid X running 2.3.3.

SixXS
Hurricane Electric
And others.

Not yet, Comcast is currently trialling IPv6 in select locations (i.e. San Francisco, NYC, Boston, etc.). They expect to roll out IPv6 to the rest of us some time this year. (You can keep up with their progress here.)

Meanwhile, if you really want IPv6 for whatever reason, I set up a tunnel with Hurricane Electric. After configuring my computers and router (DD-WRT, IPv6 is fully supported), I had IPv6 both internally and externally (i.e. IPv6 DHCP and access to the IPv6 Internet). You can set your own up here.
(I took it down shortly afterward, because I don't know about any security ramifications this would have.)

What tunnel providers have you looked into? I use the IPv6 Tunnel Broker from Hurricane Electric and routinely am able to reach 12 Mbps speeds, which I'm pretty sure is maxing out my home broadband. If you haven't looked into them before, or if you have but ran into problems, it may be worth checking out again.

If you're running a modern OS, it's fairly easy to set up a tunnel.

Register on either http://tunnelbroker.net/ or http://www.sixxs.net/main/ and create a new tunnel for yourself. There are instructions on how to start the tunnel which will put that single machine on the IPv6 network.

From there, you can look into setting up RAdvD (if *nix) to act as an endpoint on your network, supplying IPv6 IPs to everything on it automatically.

The next step would be to have an ISP which supplies an IPv6 address to your router (which would need to support it, most cheap ones don't currently), which removes the need for a tunnel and RAdvD, but this step is going to be some time coming..

Playing with IPv6 is ok, but please for the sake of spreading good experiences about IPv6, please don't recommend SixXS. They have many problems with their service, mostly with admins who care more about their own ego than the users. There are other tunnel providers available, I've heard good especially about Hurricane Electric, but anything else than SixXS works fine.

I always had a hard time understanding IPv6 until I read the Running IPv6 in practice howto on Debian-administration and tried it at home. The next move is configuring the office where I work to use such a tunnel, then a friend's colo server, then our hosting environment. It's really not hard. Get over the adressing scheme. IPv6 is much easier to manage than NAT.

Tunnelbroker by Hurricane-Electric also does a great job of making IPv6 easy to use and fun to learn (the "certification" games). They also throw in free DNS hosting, and announcing IPv6 addresses using BGP is possible.

Now stop whining and bite the bullet :-)

I know I am not using IPv6 at the moment. How can I test whether it is my setup that fails, or my ISP that fails (or any other part)?

If you're using Windows 7 or a recent Linux, your PC supports it. Mac OS X Leopard will also (it's broken in Snow Leopard unfortunately).

If you're using a router, it probably doesn't support it although you may get lucky. There are a handful of IPv6 WiFi routers on the market, luckily they are all mainstream and pretty widely available.

A few ISPs offer it--you may check with them, but if you're plugged in directly (not through a router) and are using one of the above operating systems and still aren't seeing it then you can be fairly sure that they don't. If not, you can still get IPv6 through a static tunnel (eg from from HE) if you're located close to a tunnel server. If you do sign up with HE you'll want to point your PC or router to their DNS servers in order to connect to Google and Youtube over IPv6. (Google only offers that service to ISPs, such as HE, that have specifically requested it.)

I've had no trouble with Hurricane Electric. They're a commercial outfit, but their tunnel broker service is free. They even have a support forum.

IPv6 is easy to implement, it takes 5 mn to setup a tunnel (Tunnel Broker) and switch on IPv6 (you don't need to wait for your ISP to provide you with IPv6). And yes tunnel is the recommended way of getting IPv6 (the OECD in a report about IPv6 says so too). So get a tunnel, switch it on and enjoy IPv6. What is more difficult is to get your servers on IPv6, but client side is is done in no time. So get your users on IPv6 today then when they are more familiar, you can start to migrate your servers to IPv6.

We have 7% of ASN (the backbone Internet) which are IPv6, we need 1,000 more to reach 10% of ASN, then snowball effect will took place.

Any other attitude is procrastination, FUD, and misconceived ideas.

A blog about IPv6 and other issues in the Pacific Islands and the rest of the world

IT professionals -- the sort of people who would be reading Slashdot, or PC Pro -- should be past the stage of just reading about IPv6. They should be using it on the systems they can experiment upon. IT professionals should be ahead of regular users in understanding and using new technologies. This is doubly true for a technology whose implementation is already certain to occur in the next few years, and for which the infrastructure is already in place.

If you haven't already, go get an IPv6 tunnel set up, via Tunnelbroker, and start configuring IPv6 connectivity on your system.

I expect a lot of corporations are going to suddenly become irritated when they find they need IPv6, and it hasn't already been set up, when it could have been years in advance.

To tell the truth, those clauses are in the contract are mainly an excuse to charge/kick the heavy users.

Consumer Internet Access restrictions

Instead at the current situation you have to figure out how and were to get an IPv6 address, and either keep an IPv4 as well (and switch between the two as the situation demands) or work out how you are going to talk to the 90+% of the world that doesn't have an IPv6 address. Either of those require extra work, for every person trying to connect to the network.

The issue of where to get an IPv6 address is false one, unless you have an ISP who is dragging their feet. It is a short-term problem and once the infrastructure is in place the apparent issues will go away. Sure it is not IPv4, but no one said it was. There are plenty of solutions to give your computers names, so there should be fewer and fewer cases where you will need to access you machines using numbers.

For example of an ISP who is not dragging their feet, in France there is an ISP called free.fr that provides IPv6 to their customers at no extra cost. Once enabled the router (users are given modem-router hybrids) advertises the IPv6 subnet prefix to all the computers in the subnet. If the computers are IPv6 aware then they will self configure the address ( subnet prefix + MAC address ) and start routing all IPv6 addresses through the announced router.

If you have an ISP who is dragging their feet and you are behind a NAT, then you need to establish a tunnel to an IPv6 Tunnel broker. There are a number of places to do this, including but not limited to: Sixxs.net, Freenet6 and Hurricane Electric.

The only thing I would like to see now are more home router manufacturers providing IPv6 gateway/routers. Apple's Airport and the Fritz!Box are two of the few that do.

If you have your doubts about IPv6, then at least give yourself two months with it and then come back and tell me whether you are still of the same opinion.

Every time something on IPv6 comes out, there's a thundering herd of people who've never used it but are certain that it's awful and won't ever work. What's wrong with you people? Do you feel threatened because you're used to being the networking expert among your clique and don't want to lose that reputation? If not that, then what is it that's making you sneer at a cool new technology without even trying it first?

I'm not addressing people who tried to make IPv6 work but had problems along the way, or who otherwise had bad experiences with it. That's totally understandable and I'm not going to tell such a person that they're wrong. I am talking directly to the people who've read old articles talking about why it won't work, or who are trotting out the same tired, invalid reasons to dislike it.

Here's what you need to know about IPv6:

1. It's here and working today, and a lot of people are starting to adopt it.
2. You can run IPv4 and IPv6 on the same network and machines. I don't know of any IPv6 implementation that can't run alongside IPv4.
3. DNS works perfectly fine for IPv6. I have a long address on my machines at home and work, but ever have to manually type them anywhere after adding them to DNS.
4. If you enable IPv6 alongside IPv4 and try to connect to another host, and that host has an IPv6 DNS record, then your machine will try to connect to that address and then fall back to IPv4 if that fails. If it doesn't have an IPv6 DNS record, then you'll connect via IPv4. There's no penalty for enabling it.
5. NAT sucks. It might seem like a reasonable idea until you're reminded how nice it is not to have to mess with it, then you'll come to loathe it.
6. There are plenty of good, free, reliable IPv6 tunnels available. I use Hurricane Electric, but there are lots of others to choose from.
7. All modern OSes support IPv6 out of the box.
8. Many/most consumer routers do not support IPv6 natively (although you can still tunnel through those routers from your Linux or Windows or Mac server or desktop). Some do, though, and an Airport Extreme is still a consumer product even if it's more expensive than some of the others.

I think that about covers it. There's no reason to be afraid of IPv6. If you haven't tried it, give it a shot before bragging about how smart you are for recognizing that it can't work. Again, if you've tried it and had problems, I can understand why you're leery of the idea. If you haven't at least used a free tunnel to see what IPv6 is like, though, then you don't have a lot of room to comment on the subject.

Comcast ISP, by the way, does not support IPv6. If IPv6 is here and working today, I should be able to use it. How do I do that?

Switch to an ISP that provides IPv6 (you're surprised that Comcast is behind the times?), or spent 5 minutes enabling an IPv6 tunnel to someone like Hurricane Electric from your Linux box.

Use a IPv6 tunnel broker until your ISP gets with it. It will not be as fast as your "raw" connection, but it will get you started and get you important experience. Most of the tunnel providers seem excited to expand IPv6 usage.

D-Link and Cisco support IPv6. The D-Link-supported routers (a firmware update may be needed) are: DI-784 abg, DI-524 bg, DI-624 bg, WBR-1310 g, WBR-2310 g rangebooster, DIR-615 n. See p. 16 of Ref: http://www.ipv6.org.tw/summit2008/doc/1-4-4.pdf

On p. 15, they say: "Not only [does D-Link] meet IPv6 Ready logo requirements, but also upper layer IPv6 connection mechanisms: Static IP, DHCPv6 (Stateful), DHCPv6 (Stateless), PPPoE, IPv6/IPv4 Tunneling, 6to4 Tunneling, Autoconfiguration, Link-Local connection."

Personally, I use a free IPv6 tunnel service from http://www.tunnelbroker.net/ provided by Hurricane Electric.

I don't use Cisco at home, but IPv6 information is at http://www.cisco.com/ipv6/

D-Link DIR-615 Hardware Revision C

http://www.tunnelbroker.net/forums/index.php?topic=296.0

I bought 2, they work mint both for native and tunneled.

You *are* wrong.

* Ability to get your own /48 prefix once your tunnel is up
Via: http://tunnelbroker.net/

Get your IPv6 addresses here: Tunnelbroker.net

They've got a ton of presences all over the place, so latency is not too bad. It's really nice to be able to SSH directly to your boxes behind your router. Every address you get contains the square of the IPv4 address space for your own use.

Then bug your ISP to give you native connectivity.

FWIW though, I know I need to dive into some reading material and a Lab.

Here's your lab. Get a connection up and running and start experimenting!

It depends on the region you're in. ARIN and RIPE have slightly different policies. In general, you can't get a block for a person the way you could with IPv4 in the early 90's. However, if your org can get PI space in IPv4, odds are very high that you'll qualify for the same in IPv6.

If you just want some IPv6 addresses sub-assigned to you to play with, have a look at Hurricane Electric...they're running one of the biggest tunnel broker ( http://tunnelbroker.net/ )setups out there, and are giving out /64s (and /48s, I think) for folks to experiment with IPv6.

I've been using IPv6 since about 2001, but after the BT Exact Tunnel Broker stopped, I was lost as to where I could get access from. I signed up with Sixxs, but they have rather tight (anal, some would say) policies. They'll give you access, etc, but a single bounced/rejected email, and they disable your account. http://www.sixxs.net/faq/account/?faq=bounces.
Then I gave Hurricane Electric's Tunnel Broker a try. What a breath of fresh air. It takes about 2 mins from sign-up to being connected - they give you the relevant commands to run too, if you're not familiar with it. If you've got 2 mins to try it out, give them a go.

And Slashdot - how can you be one of the top tech sites, and not be accessible over Ipv6? And throw in SSL too, while you're joining the 21st century.

Moving to IPv6 means that I can't use NAT anymore for my home network.

You technically can, but there are few sane reasons for wanting to.

That means I need a block of IP addresses assigned to me. So does my telco/cable company have this set up and will it cost me a huge amount to get a block of IPs?

Correct, yes (they will), and no (it won't). I have a free /48 allocation from Hurricane Electric, giving me a home netblock of 2^80 addresses. If your ISP tries to rake you over the coals, I could probably peel off 2^64 or so of those to lend you.

Don't switch. Instead, get an IPv6 tunnel and run both protocols in parallel. It's relatively easy and costs nothing, and you'll have access to everything in both address spaces.

If I, senior tech guy at a large bandwidth customer couldn't get it done, why do we think every home user, T1 user, and average Joe Slashdot User could get it done.

I got it done perhaps because I'm not running a giant network. I set up tunnels from Hurricane Electric at home and at work, let our {Free,Open}BSD firewalls announce routes, and started using it. See my home page next to my name? There's no dancing turtle, but you can get to it over either protocol.

One of the huge wins for me as netadmin is that I can stop screwing around with port forwarding just to be able to SSH or make VOIP calls from home to work or vice versa. I'm loving me some end-to-end connectivity again.

First find out all the ISPs in your area and ask them about IPv6 support. Second to get on board while waiting for them to get their act together (assuming they haven't already done so), choose a transition solution. Some include:
    - Freenet6 - http://go6.net/4105/freenet.asp
    - Aiccu - https://www.sixxs.net/wiki/Aiccu
    - Teredo
    - Hurricane Electric - http://tunnelbroker.net/

I've asked before if /. is truly geek enough to be the first major tech site to start testing IPv6 connectivity. It's time to ask again, so slashdot people, consider it asked, again.

Slashdot has good admins and programmers behind it. Certainly CmdrTaco seems to be constantly improving the slashcode base, and for those of us with low IDs we can see the improvements being rolled out on a regular basis (and it's all appreciated, despite occasional grumbling, thanks all).

What needs to happen is for one of their more competent OSTG network admins to obtain a tunnel from either Hurricane Electric or Sixxs. If they were to send an email to one of the people at either HE or Sixxs, there would probably be all kinds of technical assistance offered. Both tunnel providers have ubergeeks behind them, and a high profile site like /. would be a major win for them.

Putting the tunnel on one of their Cisco 3745 routers is about 9 lines in IOS for the routing and interface addressing, and a handful of ACLs to protect the router on the new addresses. Finish it off by providing a /64 subnet to the VLAN where one of their test or development webserver machines resides.

After that, the fun begins. They can put a static IPv6 address onto one of the test or development machines, make Apache bind to it, and they will be off and running. More like off and limping, because there will be work to do before they are ready to make any kind of announcements or even put the AAAA record into DNS. They'll have to make sure the local firewall also deals with IPv6 addresses, and a ton of other little sysadmin things to make sure badness doesn't sneak in on the new connectivity.

First off, CmdrTaco will probably find bugs or deficiencies in the slashcode and database structures when dealing with a new address family. There WILL be bugs found in perl network modules and in mySQL. Logging scripts may need to be updated. Statistical packages run against logs may choke or ignore longer addresses. Some functions may mangle colon delimited addresses. RSS feeds may not deal with square brackets around v6 addresses. Although there will be some things needing fixing, a surprising amount will just work with IPv6 with no modification.

When most of it seems to be functional, they can stick a separate AAAA record in their DNS for something like ipv6.slashdot.org and ask those of us with connectivity to test for a while. No need yet to add it to the main A record of slashdot.org. Just get it out for those of us with IPv6 to test.

Even if the network admins were to have the tunnel up by next week, I wouldn't expect to see even basic functionality before mid-summer, and if limited testing all went well to just put a AAAA record in parallel by the end of 2008. It takes a while, but it can be done.

When /. does have a working IPv6 code base, they can put pressure on their upstream provider to get native v6 connectivity, because a tunnel isn't going to hold up for too long.

All website upgrades are going to follow a path like what I've just described. The networking takes almost no effort, but the coding of website functionality will require some work, work that can be rolled into ongoing website maintenance.

I've been thinking about this post for the last few IPv6 stories on /., this seemed like a good time to point out the easy and hard parts for a dual-stack rollout. After this, we can only wait and hope...

the AC

This will probably be redundant by the time I end up posting, but then again, maybe not.

It seems like there are a few things that are causing confusion. Also, I want to rant about ipv6 adoption.

First of all, this looks like it's probably the printer's (or printer driver's) fault and not Microsoft's.

Second, about ipv6 in general...

It hurts me a bit to see people saying "Just disable ipv6 whenever you install vista." I think MS is doing a great thing by enabling ipv6 by default. If the instructions to support desk people, or some "best practice" becomes to disable ipv6 right away, ipv6 will take *another* 10 years to enter the mainstream.

This is pretty bad considering that ipv4 addresses are running out in the next 5 years.

It is exactly these kind of firmware/driver bugs (not having ipv6 support in a network appliance should now be considered a bug) that need to be flushed out before the internet is thrust into ipv6 adoption when the address space runs out.

IPv6 *does* solve problems, and it *will* be the primary mode of accessing the internet for consumers. Shaking out bugs by actually using ipv6 is necessary.

So, MS should *not* be berated because of this. This particular instance is not their fault, and they're doing the right thing by putting ipv6 up front in vista.

Lastly, I'd like to say that deploying ipv6 in the home is actually ridiculously easy. I have a tunnel through hurricane electric. Stateless autoconfig, which happens with ipv6 by default, assigns addresses without a dhcp server, and allows things to run right away.

IPv6 and OS support is not the problem. Application and network hardware vendors *have* to get with the program and start to support ipv6 in a very real way.

Another free IPv6 tunnel service is Hurricane Electric, and no I don't work for them. I used their service about a year ago, but I have since moved onto a router that doesn't have native IPv6 support. Also there were hardly any websites to browse to using IPv6. When I used it though, I was able to get anywhere between 5-10Mbps sustained throughput using IPv6 from my connection in Sacramento to theirs in the Bay Area. Not too bad. They also offer BGP, which I think uses a "private" AS number.

I honestly doubt that alot of the big high end router manufacturers will make alot of money off the switches. Most high end routers are alot of software and some of them even run Linux. And the WRT54G(s)(l) is a consumer grade router. The big boys already can support it and probably do.

It's the ISP's that it's going to kill. For a "true" ipv6 connection they would have to make sure there consumers are using a fully ipv6 compatable operating system, have a fully compatable cable / dsl modem (im not sure if most of the current ones are compatable but im pretty sure there not). ipv6 doesn't need a router so all the money Joe Servicepack spent on his nice "D-Link" router or his 2.99 bargin bin special ... it's not all bad it could switch his network. The consumer really doesn't pay anything it's the people "behind the scenes". There is no "ipv6" button on most ISP equiptment so there not going to go "oh lets press the button" then boom the net is on ipv6. If it where that easy im sure it would be done by now.

Anywho, im not in a big rush NAT is a hack but it seems to work alright. You really need to tweak some things to work behind it (like FTP) but other then that for most end users they really don't care. Plus it keeps securing a network easy being that there is only one device to take care of for many computers.

I have stepped into the 6bone world and I think it's really cool. Being able to setup RDNS and have 18 quintillion IP's to my name. Of course once the ISP's get to it im sure it won't be as fun, but still im sure going "well your house only gets 10 IP's or somthing of the such won't be taken lightly considering a /64 is the smallest chunk you can route (18 quintillion IP's) and the compeition will simply outdo them. I can't wait till I get to press the button on my linksys router to "AP" and not router :) im sure alot in here are too.

If your intrested in ipv6 and have a WRT I made a nifty little site on configuring it. Here is the link it deals with setting up your WRT with radvd to broadcast ipv6 all over your network. Few things to edit ... sign up to Hurricane Electrics Tunnel broker and set it to run on starting then enable ipv6 on your clients and bam ... your on the 6bone. The best thing is it's free.

I even happen to setup my website on ipv6 too so if you have ipv6 This should show you

Had the increased address space (and simplification of the header) been all that IPv6 did, I would embrace it whole heartedly. Oh well, second system syndrome and all that.

I'm using IPv6 right now, happily connecting to v4 and v6 sites. It's a simple matter of intelligent use of private v4 space and "try v6 first" DNS.

Go to http://tunnelbroker.net/ and get yourself one too. Oh, BTW, the tunnel doesn't work through NAT.

I agree, my ISP refused to even talk about it. All they said was, "Maybe you should look into a business account." Luckly, http://tunnelbroker.net/ from Hurricane Electric is available for you to turn up IPv6 yourself today.

The last time I was working on peerings at the MAEs, IPv6 was not being handled natively, has that changed?

Through networks like Hurricane Electric, Freenet6 and (on a more serious level) OCCAID people are experimenting with IPv6 today. I recently colocated a server and for no additional cost receive native, dual stacked IPv6 service. Do many people use it? No, but it is a start. The trick will be to get as many servers working on this dual stacked service as possible. Eventually ISPs will start supplying dual stacked service.

Earthlink even offers a custom WRT54G firmware which will automatically set up an IPv6 tunnel for you. What are you waiting for? Now is the time to support both protocols so we can begin the very lengthy transition.

Many thanks. I had not heard thought to search for the phrase "tunnel broker", that worked. I have a tunnel from Hurricane Electric, I think, although I'm having difficulty enabling it through NAT at this moment.

They do have great tools, though, I recommend them. http://tunnelbroker.net/

Well, there are already several 6-to-4 and 4-to-6 gateway sites. This one is one example. If there was a site that was only accessable through IPv6 you could use a service like that to access it over any IPv4 host.

Also, if you have an IPv6-capable host you can use a tunnel broker (such as Hurricane Electric's free service) to achieve connectivity to IPv6 sites over IPv4.

So you really don't need an IPv6-capable ISP to access IPv6 hosts, although it's cleaner that way of course.

1. You must compile IPv6 Support into your kernel
2. You must register with an IPv6 Tunnel Broker. Fortunatly enough there are quite a few free ones, and I list two below:
3. 
   
   
   • Hurricane Electric: http://tunnelbroker.net (Based In California)
   • Bt Exact: https://tb.ipv6.bt.com (Based in the UK)
   Due to the predominate IPv4 nature of the Internet, you must tunnel your IPv6 packets encapsulated into IPv4 packets and send them off to your tunnel broker who will then route them nativly within the sixbone. Therefore you want your tunnel broker as close as possible, so choose accordingly. Unfortunatly HE recently banned IRC traffic due to abuse, so If you want to join an IPv6 enabled IRC server you are forced to use Bt Exact which is what im currently using.
   
   
4. Once you register with the Tunnel Broker they will issue you a /64 subnet. That's right a /64 subnet which allows you to have up to 2^64 (18.4 million-billion) IP's!!
   One of the other cool features of IPv6 is that you are currently allowed to host your own reverse DNS for your IPv6 addresses. Thus if you want to spoof your IP on IRC without having to resort to running your own hosting company or doing illegal activities this is how you would do it. My hostname on IRC currently resolves to 0.0.0.0
5. Download my init script at www.identityflux.com/ipv6 (Slashdot effect here I come!)
6. Once you get all the information from the Tunnel broker, simply edit my init script and start'er up. Here are the 5 variables you must edit:
   
   
   • LOCAL4: This is simply just your IPv4 address
   • LOCAL6: This is the IPv6 /64 subnet address that I was talking about earlier
   • REMOTE6:. This is the IPv6 address of the server on the other end of the tunnel
   • NUM_ALIAS: This is how many aliases you want to bind to your new IPv6 interface. You can assign a differnt host name to each one, www/ns/mail etc etc.
   
   All but LOCAL4 will be given to you by the tunnel broker.

[root@maximus][~]# ping6 www.kame.net
PING www.kame.net(orange.kame.net) 56 data bytes
64 bytes from orange.kame.net: icmp_seq=1 ttl=55 time=31 ms
64 bytes from orange.kame.net: icmp_seq=2 ttl=55 time=14 ms
64 bytes from orange.kame.net: icmp_seq=3 ttl=55 time=15 ms
64 bytes from orange.kame.net: icmp_seq=4 ttl=55 time=51 ms