Re: Maximum swap size

From: Arthur Hagen (art_at_broomstick.com)
Date: 03/08/05 

Date: Tue, 8 Mar 2005 01:12:28 -0500

James Knott <james.knott@rogers.com> wrote:
> Brian wrote:
>
>> <quote>
>> IPng supports addresses which are four times the number of bits as
>> IPv4 addresses (128 vs. 32). This is 4 Billion times 4 Billion times
>> 4 Billion (2^^96) times the size of the IPv4 address space (2^^32).
>> This works out to be:
>>
>> 340,282,366,920,938,463,463,374,607,431,768,211,456
>>
>> This is an extremely large address space. In a theoretical sense
>> this is approximately 665,570,793,348,866,943,898,599 addresses per
>> square meter of the surface of the planet Earth (assuming the earth
>> surface is 511,263,971,197,990 square meters).
>> </quote>
>
> I guess it'll be a while, before we run out of IPv6 addresses. ;-)

The problem is that the IP space isn't equally distributed, and the 64k
address space that an end-user gets might not be enough for future use,
especially not if requiring extra routing between multiple locations that
divide up the address space.

It'll work for a while, but I find the whole IPv6 concept seriously flawed
and inefficient. A good IP system should really should have a dynamic
length, where each new end-point can add to it. That would allow for true
unlimited address space as well as smarter routing (if my router has a
direct route to ABCD:EFGH:IJKL:MNOP, why should it send a packet to
ABCD:EFGH:IJKL first, and that send it on to :MNOP)?
Alas, too much time was spent trying to maintain compatibility with IPv4,
and it turned out that the compatibility isn't all that great anyhow --
degrading devices are few and far between, and almost all IPv6 traffic is
either local to the system, encapsulated in IPv4 or (slowly starting)
between IPv6-only devices. I still hope for the death of IPv6 and a new
truly dynamic IPvN using a new IP protocol. After all, that could be added
to routers without affecting today's IP, instead of kludged in as an
extension.

Regards, 

-- 
*Art

Relevant Pages

  • RE: Transfer a sending packet to upper TCP/IP protocol layer in IM
    ... He's building a gateway across an IPV4 segment. ... AFAIK, all systems that support IPv6 provide this feature anyway, so that I ... the destination NIC of IPv6 packet is the same as the destination NIC of my ... was assuming that tcpip stack can rebuild the L2 header for the encapped IPv4 ...
    (microsoft.public.development.device.drivers)
  • RE: Transfer a sending packet to upper TCP/IP protocol layer in IM
    ... I suggest you look at the IPv6 gateway standards RFCs if you're interested. ... How is he going to get IPv4 address, ... the destination NIC of IPv6 packet is the same as the destination NIC of my ... was assuming that tcpip stack can rebuild the L2 header for the encapped IPv4 ...
    (microsoft.public.development.device.drivers)
  • Re: AAISP?
    ... Premium packages, and considering Max 1 Premium - depending on the ... nothing about IPv6, except that I'd end up with a /48 block if I ... I'd probably settle for setting up a PPPoE forward on my current router ... would I still be able to use the IPv4 ...
    (uk.telecom.broadband)
  • Re: Fast downloads, slow browsing
    ... That article shows you what a normal IPV4 configuration should look like. ... With Windows XP, Microsoft added IPV6, which is more complex and offers much ... Your computer, and the subnet created by the router, appears to be on ... problem was a defective modem. ...
    (microsoft.public.windowsxp.network_web)
  • AAISP?
    ... IPv6 connections available, which is something I would really like to ... nothing about IPv6, except that I'd end up with a /48 block if I ... Currently my router only supports IPv4. ... would I still be able to use the IPv4 ...
    (uk.telecom.broadband)