Slashdot Mirror
Slashdot over IPv6
fuzzel writes "Even though Slashdot has run a number of articles about IPv6 (1|2|3) it apparently isn't reachable over IPv6 directly.
But for the people that do already have IPv6 they can use http://slashdot.org.sixxs.org and they will be automaticaly gatewayed. This trick works for most sites by simply appending .sixxs.org to the domain part of a url, eg http://www.google.com.sixxs.org, the gateway will the rewrite url's to have it appended automatically so that everything goes over IPv6. Full information is available on http://ipv6gate.sixxs.net. Oh and yes if you don't have IPv6, those domains under sixxs.org won't work :)"
uh.. or it could just be slashdotted :P uhm, wait..
I don't know.
"And in other news, Slashdot managed to bring down the entire IPv6 network today..."
This Sig Kills Fascists
I'm not entirely clear on why IPv6 such a cool/neccesary thing. As far as I, in my limited knowledge, know, IPv6 will allow for more IP address, but is that it? I'm not questioning its usefullness, but am simply curious if there are any other benefits that come along with IPv6.
I think sixxs.org just found out the ultimate solution to prevent a site from becoming slashdotted. :-)
Beware: In C++, your friends can see your privates!
If not, then shame on us.
I get a feeling in my gut that says sixxs.org is not as impervious to slashdotting as slashdot itself,
so maybe we will finally be able to slashdot slashdot, or at least the IPv6 gateway,
BUT maybe there are not enough slashdotters using IPv6 to be able to connect to the IPv6 slashdot in order to slashdot slashdot's IPv6 gateway,
and... [head explodes]
My life in the land of the rising sun.
I think I get the general idea, but it took me some time. Funny how a couple of spelling mistakes can lead to a quite obfuscated sentence. Anyway, here is what I now think (after checking the site: boggled at that sentence in vain!
I code, therefore I am.
This whole discussion and the support of IPv6 is completely pointless. There are 101 ways to bridge your IPv6 to IPv4 and the other way round. There is no chicke and egg problem. The real reason why IPv6 is not widely deployed is that nobody really needs it.
This is just like HDTV, yes, it's better, cooler, has nifty features, but the old thing does most of the job for much less money/effort.
With IP this situation 'might' (not necessarily 'will') change with the vanishing IP address space, but I am convinved it's perfectly safe to wait till we get there.
If any ISP really thinks he needs v6 he will just install it. Why should I (as a user) try to convince any ISP to use v6. It's just nothing that matters to me. (Multicast?? ha!) I can tell you, that I (as an ISP) don't even know why I should convince anybody. This whole discussion is probably sponsored by cisco's PR department.
Cheers.
KdenLive/PIAVE - non-linear video editing
hey Taco. dont you have sense. In this oil scarce world you are going on V6s!!. guys dont listen to these nerds, stay on V4 and save the earth.
My Aurora : http://www.youtube.com/watch?v=o91ZsGwJYyg
FB : https://www.facebook.com/TanveersPhotography
Use a tunnel broker. It lets you tunnel ipv6 connections over ipv4 to another endpoint. Two of the most popular are Freenet6 and Hurricane Electric. Hurricane Electric requires a static ipv4 IP, but Freenet6 works with dynamic IPs.
The best way currently to use IPv6 is via tunnel brokers, who give you a range of ips (/64 or /48, both of which will vastly outnumber any number of electrical components in your house).
/64 (thats 18,446,744,073,709,551,616 distinct ips :) ) and delegates full forward and reverse DNS to you for this range.
These work by creating a ipv6 GIF tunnel over ipv4, to a server which has either further tunnels to the 6bone or native connectivity. Once you have this setup (and its preety easy to do on Linux, Windows, and very easy to do on the BSDs) then any ipv6 traffic can be routed automatically. This way you dopnt need to use a gateway, and you can use pretty much any app over ipv6, including ftp, ssh, www, email etc.
Disclaimer: I help run ipng.org.uk, which is a UK tunnel broker, who gives you a
Its fully usable, and is no longer experimental. There are a number of practical uses, although they vary from person to person. I use a ipv6 range for a number of different reasons, one of which is to protect me from attack when on irc (a ipv6 tunnel is a lot easier and more convenient to drop than your ipv4 connection :) ). The other reason is that you can assign IPv6 ips to machines behind a NAT gateway, and have fully routable addresses, which is handy if your broadband providor doesnt issue you with multiple ips.
Disclaimer: i help run ipng.org.uk, a UK tunnel broker.
See this link for more info regarding IPv6 and it's advantages in today's networks.
My limited understanding of IPv6 is that you can deploy v6 addresses locally, and advertise them globally via DNS using AAAA records. You can then talk over the larger Internet using a 6-over-4 tunnel.
Assuming this is correct, why doesn't Slashdot simply advertise an AAAA record, then accept connections through a 6-over-4 tunnel (or natively, if their bandwidth provider can speak it)? What are the technical considerations preventing this from working?
Schwab
Editor, A1-AAA AmeriCaptions
>who gives you a
Great! And for those of us in the States (especially California), Hurricane Electric offers a free tunnel broker with these characteristics that I would recommend.I have been using it for more than 6 months, and find it quite stable. You do lose your /64 if HE can't ping you for 24 hours, but a new one is only a mouse click away. And what kind of geek would leave their computer inaccessible for that long anyway? ;). Initial activation does take a day or so.
-Fyodor
Concerned about your network security? Try the free Nmap Security Scanner
But for the people that do already have IPv6 they can use
What exactly does it take to 'have' IPv6? What stuff neds to be upgraded? Application software? OS? Router? Does your ISP need to 'have' or 'support' it? It also seems a hell of a lot more complex to type in an IPv6 address than an IPv4 one, but I guess that only matters if you're not using a domain. Then again, with so many IP addresses available with IPv6 this may be the case, as there won't be nearly enough domains to hold everyone's IP!
I'm sorry that this will sound ignorant, but if I'm asking the question and I'm not exactly dumb, it's no wonder all the AOLers aren't using IPv6! I don't even know how you use it, and there are barely any servers using it either, no?
== Jez ==
Do you miss Firefox? Try Pale Moon.
I have a few machines at home and things like a tivo and a Zaurus that need IP addresses. Ideally they all should have proper routable IP addresses so the internet can be used as it is intended. Luckily my ISP (Andrews & Arnold) provide as many IP adresses for my ADSL as I want for no extra cost. But I'm still limited to 5 usable addresses. But they also provide Ipv6 access to the internet and give you a range of addresses. But instead of five addresses I get a whole /64 range which is 2^64 usable addresses.
Anyway, if anyone in the UK wants ADSL and to use IPV6 I can recomment A&A as an ISP for this
Sig is taking a break!
An IPv6 address is 128 bits long. Of these 128 bits, 64 bits are reserved for the host part. Usually it's a somewhat mangled version of your ethernet MAC address (a router will broadcast a prefix, and client machines will simply append the mangled version of their MAC to the prefix -- this is called autoconfiguration).
This means you need a /64 subnet on each segment.
Usually providers will assign you a /48 addressspace, giving you roughly enough space for 65000 subnets.
Of course these addresses are routable: you don't need NAT and your machines are reachable from the internet.
This is your sig. There are thousands more, but this one is yours.
Everyone knows the Chicken and the Egg story (which came first), with IPv6 it's the same:
*) IPv6 is ready to deploy, however not much ISP's are supporting IPv6.
*) ISP's are not supporting IPv6 because there are no customers who uses it.
*) Customers aren't using IPv6 because there are no applications who uses it.
*) Software developers aren't creating software because nobody uses it.
As you can see there's a loop. The main thing is to break this loop and this project is a step in the good direction.
I'd like to encourage all ISP's to actively implement and promote IPv6. And you as 'consumer' can also promote IPv6, play with it even when you ISP doesn't support IPv6 yet (with IPv6 Tunnels for example).
Just my 2 cents.
Daxy's Networking Blog
Lets face it , unless you've got a Phd in networking chances are that some facet of IP4 routing , setup etc still confuses you. This goes for network admins too. Now multiply the complexity of ip4 by 10 and you get the nightmare that is IP6. I've tried to set up a home ip6 network that linked out to the internet but , oh my god , what kind of idiots invented this system? I'm sorry , but even computer admins are human (yes its true) and we REALLy don't want to have to mess around with 128 bit meaningless entries in routing tables that were complex enough with 32 bits! Yes ip6 does some autocofiguration but someone has to set up the system so that some host does the autoconfig. Ever tried it? Don't , not unless you want to end up in a padded cell. Even networking protocols should be designed for people to be able to use and I'm afraid with ip6 that simply hasn't happened. Back to the dsrawing board guys!
It was an experimental protocol that never made it out of the lab. At least that was what my networking prof in college told me :-P
1. There are some things you can't do with NAT. For example, some VPN tunneling solutions can't be used over NAT.
2. What if you want to run a service on the same port on multiple machines. With NAT you can only forward a port to a single machine. With fully routable, there are no problems.
3. What if you NAT an office and some idiot is poking around other peoples networks. With NAT, all you know is that the connection came from your office. With fully routable IPs you may be able to tell whos machine was the culprit.
These are just three. There are many more...
Even if your local network infrastructure does not support IPv6, all installations of MacOSX 10.2 have and IPv6 stack. The following is taken from doing an 'ifconfig' at the command line:
T ICAST> mtu 1500
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MUL
inet6 fe80::230:65ff:fed6:b164%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:30:64:d6:b2:64
media: autoselect (100baseTX <full-duplex>) status: active
From what I can tell MS-Windows is still a little behind, as can be seen from this page. As for other OSs I am not aware of their support status. If you do know, a reply to this post would be handy to most.
Jumpstart the tartan drive.
Jumpstart the tartan drive.
- ... supports QoS features.
So does IPv4 -- it's just that no one actually *uses* them.
The main thing that I *really* don't like about IPv6 is that, while it isn't a mandated part of the protocol, it seems that the overwhelming direction being pushed is to make the last 48 bits of your address your MAC address. Which *really* has nasty privacy implications -- 'slike a universal cookie, visible to everyone, that anyone can see (not just http servers).
May we never see th
I think NetBSD's Introduction to TCP/IP Networking has a pretty good intro about IPv6, even if you do not use NetBSD.
Prescriptive grammar:linguistics
For starters, classful routing on the Internet has gone the way of the Dinosaurs, and good riddance. CIDR saw to that (Classless Inter-Domain Routing), and when BGPv4 became the standard, all was right in the world (Because it implemented CIDR, by carrying Netmask along with the route entries).
In casual conversation today, we still use terms like Class B, or Class C address space, but they don't refer to the actual Classful network boundaries of yore. Today, when someone refers to a Class C address space, they simply mean a 24-bit address space. Likewise, a Class B means a 16-bit (/16) address space.
You say your netmask is 255.255.248.0. This represents a larger address space than a Class C, which has a mask of 255.255.255.0 (or /24).
Your address space is the aggregate of 8 Class C networks. Your network is configured to utilize the first and second octets, and the first 5 bits of the third octet as the network address, leaving the remaining 3 bits of the third octet, and the entire fourth octet as the host address.
That represents a network segment consisting of up to 2048 hosts (Ok... 2046 since you toss the first and last as the network address and the broadcast address.).
In short, your network engineering staff ought to be shot, because damn, that's a really big subnet. There's just no good reason to have that many hosts on a segment.
It's possible that you guys don't have anywhere near that many hosts, but if you do, without even looking, I can tell you that your network is a bit of a show. I hope you have your highly-loaded servers on their own segment, because the number of broadcasts must be tremendous. Even in a switched environment, those broadcasts must be propegated everywhere, and every machine in the network has to stop briefly to examine each and every one.
Your organization should look at some Layer-3 segmentation...
For those that would die defending it, Freedom
has a sweet taste that the protected will never know.
SixXS-IPv6Gate/1.0 (IPv6 Gateway; http://ipv6gate.sixxs.net; info@sixxs.net)
Bad! Many sites go through painstaking effort to be compable with all sorts of user agents, giving plain HTML when one is not recognized. By re-writing the user agent these people prevent this magic. Not good. Instead it should add it's own key/value pair, much like SQUID or other cache/gateway.