• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How to register IPV6 IP address

blazer78

Senior member
Hi, I was just wondering whether there was a process to register ipv6 addresses? Is this allocated through the ISP or is there a unique procedure to do so (for a private network not connected to the net)?

 
If it's a private network, it all has to do with your DHCP server. Although if it's a private network, I don't see one reason why you'd need IPV6 addresses anyway. I don't ever see a private network running out of IPv4 addresses.
 
I require wireless internet access and improved security amidst other features present in IPv6 that arent in IPv4.

So for a network with internet access I would have to register an ipv6 address via my ISP?
and for a network without internet access I'd have to process it through the DHCP server?
 
No. You would use a private IP address for your local network (either assigned by DHCP from your router or manually configured on the computer, then your router will transmit your web requests to the ISP using the IP address that the ISP gave it. The ISP doesn't care what IP address(es) you use on your own private network, and using an IPv6 address on your private network will not have any effect on your Internet traffic unless your ISP assigns you a public IPv6 address.

As far as your "need" to use IPv6, what features do you need on your private network that can't be provided by an IPv4 address (I'm just curious).
 
I fail to see the need at all for IPV6 addresses on any private network. There will eventually be IPV6 addresses assigned by ISP's to consumer's but that won't have any effect on a private network with how NAT is. Honestly, if most companies used NAT properly the way it was designed, I predict we wouldn't be running out of IPV4 addresses but that's a separate issue entirely. In a private network, 99% of the time, IP addresses whether they be V4 or V6 are handled through DHCP and I honestly don't see the need for v6 IP addresses in a private network. You don't change things like that unless you have to, atleast in a corporate environment you don't.
 
Using IPv6 in a private network is like riding a bicycle and thought that you needed a highyway system to get it going.
 
Not sure if this changes anything or even matters, but aren't all IPv6 addresses right now encapsulated within an IPv4 packet once it hits the internet anyways? I think as long as a router supports it it will pass it through as IPv6, but for compatibility it passes it as an IPv4 so it gets where it needs to go. And at the destination encapsulates it back to IPv6? Yes/No?
 
Originally posted by: Tarrant64
Not sure if this changes anything or even matters, but aren't all IPv6 addresses right now encapsulated within an IPv4 packet once it hits the internet anyways? I think as long as a router supports it it will pass it through as IPv6, but for compatibility it passes it as an IPv4 so it gets where it needs to go. And at the destination encapsulates it back to IPv6? Yes/No?

Yes and No. It depends. You're talking about tunneling IPv6 packets around, and that does require both ends to be configured. If only one end supports it, the tunneled IPv6 packet will just be dropped upon arrival. I believe there is even a NAT configuration for doing IPv6 to IPv4 and vice versa. They've been trying all kinds of methods to get them to work together so they can start a transition. Supposedly some IPv6 addresses have been allocated, but you're probably not going to see them any time soon.
 
Originally posted by: mcmilljb
Originally posted by: Tarrant64
Not sure if this changes anything or even matters, but aren't all IPv6 addresses right now encapsulated within an IPv4 packet once it hits the internet anyways? I think as long as a router supports it it will pass it through as IPv6, but for compatibility it passes it as an IPv4 so it gets where it needs to go. And at the destination encapsulates it back to IPv6? Yes/No?

Yes and No. It depends. You're talking about tunneling IPv6 packets around, and that does require both ends to be configured. If only one end supports it, the tunneled IPv6 packet will just be dropped upon arrival. I believe there is even a NAT configuration for doing IPv6 to IPv4 and vice versa. They've been trying all kinds of methods to get them to work together so they can start a transition. Supposedly some IPv6 addresses have been allocated, but you're probably not going to see them any time soon.

There was a map chart not too long ago (maybe linked on Slashdot) with who is using the most IPv6 addresses. The U.S. was not at the top of the list, I think Russia is.

Edit: Here we go. This article actually has some good info about IPv6 vs IPv4 and their usage right now. Go Mac apparently:

http://arstechnica.com/news.ar...-ipv6-usage-in-us.html
 
Back
Top