IPv6 when?

[#1]

That looks like it only supports IPV6 over IPV4, PlusNet should be going IPV6 over IPV6 so that device is more for tunnelling?  You'd also need a proper router which can do things with the Ethernet port, not the standard adsl routers which don't, for instance, let you plug a modem into an Ethernet port and use that instead of the built in modem.

[#2]

But are the zillions of protocols that my PC uses enabled for IPv6?
E.g. can I use a IPV6 address as part of my email address (if I want to)?
How does IPV6 work over wireless?
Over a encrypted powerline connection?
Do I get a firewall+NAT+DHCP on my IPV6 router?
I bet things like IP connected printers would mostly stop working.
Do I have to buy a miniature Linux powered piece of hardware to do all of the above?

[#3]

Quote from: A

But are the zillions of protocols that my PC uses enabled for IPv6?

It's applications that need enabling for IPv6 not protocols.

Quote from: A

E.g. can I use a IPV6 address as part of my email address (if I want to)?

Actually yes, you can (so long as the mail server has been enabled for IPv6), but you wouldn't want to, any more than you would want to use an IPv4 address in your email address.

Quote from: A

How does IPV6 work over wireless? Over a encrypted powerline connection?

Both of those are transmission mediums are basically uninterested in content of what they are transmitting.

Quote from: A

Do I get a firewall+NAT+DHCP on my IPV6 router?

I wouldn't expect NAT for IPv6, since NAT only came about because of the limitations in IPv4, Firewall yes, DHCP for IPv6 yes.

Quote from: A

I bet things like IP connected printers would mostly stop working.

Not really, not unless both your computer suddenly looses the ability to use IPv4 and the printer manufacturers refuse to upgrade their firmware.

Quote from: A

Do I have to buy a miniature Linux powered piece of hardware to do all of the above?

Unless you paid a lot of money to CISCO for one of their proprietory solutions, then you already have "a miniature Linux powered piece of hardware to do all of the above" for IPv4.  Moving to IPv6 may mean a new box, may mean a firmware upgrade...

[#4]

Billion BiPAC 7800NL All-in-One IPv6 ADSL2+ Wireless-N Router (300Mbps)
http://www.broadbandbuyer.co.uk/Shop/ShopDetail.asp?ProductID=10414

[#5]

From what I recall (from memory mind you) IPV6 doesn't do NAT at all, each device is basically connected directly to the internet with it's own IP address which has something to do with the IPV6 address and a Mac address, this makes it even more important to have a firewall because there is no NAT on the router to offer a level of protection that way.

[#6]

Theres no reason that you can't use NAT with IPv6, on the other hand, there's also no reason you would.

[#7]

Nearly all applications work fine with IPv6 now.  Email, DNs, websites etc, mainly only propriety protocols may have problems, skype etc
email is just a case of adding a AAAA record to your MX, ie
bohara@titan> host -t mx benohara.net                                        ~
benohara.net mail is handled by 10 mx0.benohara.net.
bohara@titan> host mx0.benohara.net                                          ~
mx0.benohara.net has address 193.0.0.180
mx0.benohara.net has IPv6 address 2001:67c:2e8:3::c100:b4
There is no NAT in IPV6, its not needed.  It was essentially invented to slow the depletion of IPv4, but it hampers end to end communication so in IPv6 its doesnt exist.
A Stateful firewall on your router will block incoming traffic to hosts if needed.
Ben

[#8]

A good way to learn about IPV6 (for those interested) is to do the HE Certificate, basically you set up an IPV6 environment (email, web server etc.) and each step of the way bumps you up the certificate list and I believe you get a T-Shirt when you complete the certificate!
I got stuck on rDNS for IPV6 on my mail server

[#9]

Quote from: David

A good way to learn about IPV6 (for those interested) is to do the HE Certificate

Agreed, got the T-Shirt 😉

Ben

[#10]

Heh

[#11]

Also,

    Name servers:
        dns0.avatastic.co.uk      84.92.17.212
        dns1.avatastic.co.uk      212.110.185.65
        dns2.avatastic.co.uk      2001:0470:1f09:05f3:0000:0000:0000:0001
        dns3.avatastic.co.uk      2001:41c8:0001:5e2c:0000:0000:0000:0065
    WHOIS lookup made at 14:30:57 06-Feb-2011

[#12]

Quote from: fourfourdevon

Quote from: MJN Or, unfortunately, carrier-grade NAT Yeah, that sucks, NAT behind NAT just gets a real pain and breaks a great deal of applications.

Easy answer: Enable UPNP
Of course I'm joking as it would be rather insecure for everyone to be using the same network and upnp. Something similar could be implemented though surely? - IE clients have a small app on their desktop which allows them to configure ports etc on the ISPs public network interface which can then redirect over the ISPs network to your own network? - Must be possible surely?
I used to use a public wifi connection moons ago and similar was possible there in theory. I had my ICS host connected to their network via wifi and I could use UPNP on my network for other machines. The wifi owner was looking at hacking his wifi APs to allow individual users to open ports to their own computer / host which in turn could then be routed over their own network.
I was pleasantly surprised using a 3G dongle to find it had a public IP as I had always been led to believe that they used NAT.

[#13]

uPnP doesn't work behind double NAT it's one of things I was thinking about what I said NAT behind NAT breaks many applications.

[#14]

Why does NATNAT break things?

[#15]

Well answering that question comprehensively would take both a long time, and be technically involved.
But a fairly simple one to explain is uPnP.
In uPnP, software running on your computer asks your firewall to open a port in the firewall and for any traffic on that port to forwarded directly to a port its listening to on your computer.  The ports are then used by devices on the internet to talk directly to the application running on your computers.
Now if you put another NAT in front of that, it stops working, because no device on the internet can even see your router/firewall, so it doesn't matter than uPnP has opened ports no traffic is ever going to get to it.
For uPnP to work on double NAT, the ISP's firewall would have to support uPnP and somehow manage the massive numbers of open ports needed for uPnP in addition to those needed anyway, then your firewall/router would need some way to both negotiate and pass through the uPnP commands from your application and would also need a way to inform the application about the status of the ports on the ISP's firewall.
I think these problems could be solved, but they couldn't be solved easily or quickly.