Are the IPv6 address space and IPv4 address space completely disjoint?IPv4 shortage is now becoming a reality - what is needed for IPv6 to work?MLD messages during IPv6 duplicate address detectionWhat is the advantage of multicasting in IPv6 (compared to broadcast)?Is it ok if multiple non-router devices send IPv6 RAs with same prefix in the same network?Why do we need IPv6?IPv6 6to4 mechanismHow does address resolution work with multicast, specifically IPv6?Are all the private IPv6 addresses nonoverlapping? If yes, is Route distinguisher required for IPv6?Cisco 3560G not passing IPv6 RA when VLAN without IPv6 addressHow are IPv6 addresses grouped?

A social experiment. What is the worst that can happen?

Has Darkwing Duck ever met Scrooge McDuck?

Global amount of publications over time

Some numbers are more equivalent than others

Indicating multiple different modes of speech (fantasy language or telepathy)

What is the gram­mat­i­cal term for “‑ed” words like these?

Can I rely on this github repository files?

Is there a word to describe the feeling of being transfixed out of horror?

How much character growth crosses the line into breaking the character

Fly on a jet pack vs fly with a jet pack?

Have I saved too much for retirement so far?

Using a siddur to Daven from in a seforim store

Why did the EU agree to delay the Brexit deadline?

What (else) happened July 1st 1858 in London?

Is XSS in canonical link possible?

Proving a function is onto where f(x)=|x|.

Did US corporations pay demonstrators in the German demonstrations against article 13?

Will adding a BY-SA image to a blog post make the entire post BY-SA?

What is this type of notehead called?

Flux received by a negative charge

Folder comparison

What does the Rambam mean when he says that the planets have souls?

How do ground effect vehicles perform turns?

We have a love-hate relationship



Are the IPv6 address space and IPv4 address space completely disjoint?


IPv4 shortage is now becoming a reality - what is needed for IPv6 to work?MLD messages during IPv6 duplicate address detectionWhat is the advantage of multicasting in IPv6 (compared to broadcast)?Is it ok if multiple non-router devices send IPv6 RAs with same prefix in the same network?Why do we need IPv6?IPv6 6to4 mechanismHow does address resolution work with multicast, specifically IPv6?Are all the private IPv6 addresses nonoverlapping? If yes, is Route distinguisher required for IPv6?Cisco 3560G not passing IPv6 RA when VLAN without IPv6 addressHow are IPv6 addresses grouped?













9















Tanenbaum's Computer Networks says




Finally, IPv4 addresses can be written as a pair of colons and an old dotted
decimal number, for example:



::192.31.20.46



  1. Does it mean the IPv4 address space is embedded into the lowest
    subrange of the IPv6 address space?


  2. Is such embedding fixed? Can the IPv4 address space be embedded
    into any continuous subrange of the IPv6 address space?



    Does https://en.wikipedia.org/wiki/IPv6_address#Transition_from_IPv4 list several alternative ways of translation? If it is correct, then the embedding is not fixed.




  3. Does it mean that for any IPv4 address, there is some IPv6 address that refers to the same address as the IPv4 address?



    For example, are ::192.31.20.46 and 192.31.20.46 effectively the same address?



    • if I send a message to ::192.31.20.46, will 192.31.20.46 receive my message?


    • if I send a message to 192.31.20.46, will ::192.31.20.46 receive my message?


    Will ::127.0.0.1 still be a loopback IP address, and if yes, is it effectively the same address as 127.0.0.1?



  4. Or are the IPv6 address space and IPv4 address space completely
    disjoint (i.e. no overlapping), in the sense that when I communicate
    with a IPv6 address, I will not communicate with a IPv4 address?


Thanks.










share|improve this question
























  • If ::192.0.92.1 in IPv6 and 192.0.92.1 in IPv4 were equivalent and always referred to the same host (192.0.92.1 in IPv4-land), then how would a packet destined for ::0.0.0.1 be routed?

    – a CVn
    yesterday











  • @aCVn, IPv4 addresses in the 0.0.0.0/8 network cannot be destination addresses, anyway.

    – Ron Maupin
    yesterday






  • 3





    Beware of outdated textbooks. IPv4-compatible IPv6 addresses have been deprecated for almost 15 years, replaed by IPv4-mapped IPv6 addresses. Modern operating systems may not recognize them. See RFC 4291.

    – Michael Hampton
    yesterday












  • @RonMaupin Fair point, though ::1 was just an obvious example. The same reasoning would apply also to other addresses.

    – a CVn
    16 hours ago















9















Tanenbaum's Computer Networks says




Finally, IPv4 addresses can be written as a pair of colons and an old dotted
decimal number, for example:



::192.31.20.46



  1. Does it mean the IPv4 address space is embedded into the lowest
    subrange of the IPv6 address space?


  2. Is such embedding fixed? Can the IPv4 address space be embedded
    into any continuous subrange of the IPv6 address space?



    Does https://en.wikipedia.org/wiki/IPv6_address#Transition_from_IPv4 list several alternative ways of translation? If it is correct, then the embedding is not fixed.




  3. Does it mean that for any IPv4 address, there is some IPv6 address that refers to the same address as the IPv4 address?



    For example, are ::192.31.20.46 and 192.31.20.46 effectively the same address?



    • if I send a message to ::192.31.20.46, will 192.31.20.46 receive my message?


    • if I send a message to 192.31.20.46, will ::192.31.20.46 receive my message?


    Will ::127.0.0.1 still be a loopback IP address, and if yes, is it effectively the same address as 127.0.0.1?



  4. Or are the IPv6 address space and IPv4 address space completely
    disjoint (i.e. no overlapping), in the sense that when I communicate
    with a IPv6 address, I will not communicate with a IPv4 address?


Thanks.










share|improve this question
























  • If ::192.0.92.1 in IPv6 and 192.0.92.1 in IPv4 were equivalent and always referred to the same host (192.0.92.1 in IPv4-land), then how would a packet destined for ::0.0.0.1 be routed?

    – a CVn
    yesterday











  • @aCVn, IPv4 addresses in the 0.0.0.0/8 network cannot be destination addresses, anyway.

    – Ron Maupin
    yesterday






  • 3





    Beware of outdated textbooks. IPv4-compatible IPv6 addresses have been deprecated for almost 15 years, replaed by IPv4-mapped IPv6 addresses. Modern operating systems may not recognize them. See RFC 4291.

    – Michael Hampton
    yesterday












  • @RonMaupin Fair point, though ::1 was just an obvious example. The same reasoning would apply also to other addresses.

    – a CVn
    16 hours ago













9












9








9








Tanenbaum's Computer Networks says




Finally, IPv4 addresses can be written as a pair of colons and an old dotted
decimal number, for example:



::192.31.20.46



  1. Does it mean the IPv4 address space is embedded into the lowest
    subrange of the IPv6 address space?


  2. Is such embedding fixed? Can the IPv4 address space be embedded
    into any continuous subrange of the IPv6 address space?



    Does https://en.wikipedia.org/wiki/IPv6_address#Transition_from_IPv4 list several alternative ways of translation? If it is correct, then the embedding is not fixed.




  3. Does it mean that for any IPv4 address, there is some IPv6 address that refers to the same address as the IPv4 address?



    For example, are ::192.31.20.46 and 192.31.20.46 effectively the same address?



    • if I send a message to ::192.31.20.46, will 192.31.20.46 receive my message?


    • if I send a message to 192.31.20.46, will ::192.31.20.46 receive my message?


    Will ::127.0.0.1 still be a loopback IP address, and if yes, is it effectively the same address as 127.0.0.1?



  4. Or are the IPv6 address space and IPv4 address space completely
    disjoint (i.e. no overlapping), in the sense that when I communicate
    with a IPv6 address, I will not communicate with a IPv4 address?


Thanks.










share|improve this question
















Tanenbaum's Computer Networks says




Finally, IPv4 addresses can be written as a pair of colons and an old dotted
decimal number, for example:



::192.31.20.46



  1. Does it mean the IPv4 address space is embedded into the lowest
    subrange of the IPv6 address space?


  2. Is such embedding fixed? Can the IPv4 address space be embedded
    into any continuous subrange of the IPv6 address space?



    Does https://en.wikipedia.org/wiki/IPv6_address#Transition_from_IPv4 list several alternative ways of translation? If it is correct, then the embedding is not fixed.




  3. Does it mean that for any IPv4 address, there is some IPv6 address that refers to the same address as the IPv4 address?



    For example, are ::192.31.20.46 and 192.31.20.46 effectively the same address?



    • if I send a message to ::192.31.20.46, will 192.31.20.46 receive my message?


    • if I send a message to 192.31.20.46, will ::192.31.20.46 receive my message?


    Will ::127.0.0.1 still be a loopback IP address, and if yes, is it effectively the same address as 127.0.0.1?



  4. Or are the IPv6 address space and IPv4 address space completely
    disjoint (i.e. no overlapping), in the sense that when I communicate
    with a IPv6 address, I will not communicate with a IPv4 address?


Thanks.







ip ipv4 ipv6 protocol-theory ip-address






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited yesterday









Ron Maupin

67.7k1369126




67.7k1369126










asked yesterday









TimTim

613516




613516












  • If ::192.0.92.1 in IPv6 and 192.0.92.1 in IPv4 were equivalent and always referred to the same host (192.0.92.1 in IPv4-land), then how would a packet destined for ::0.0.0.1 be routed?

    – a CVn
    yesterday











  • @aCVn, IPv4 addresses in the 0.0.0.0/8 network cannot be destination addresses, anyway.

    – Ron Maupin
    yesterday






  • 3





    Beware of outdated textbooks. IPv4-compatible IPv6 addresses have been deprecated for almost 15 years, replaed by IPv4-mapped IPv6 addresses. Modern operating systems may not recognize them. See RFC 4291.

    – Michael Hampton
    yesterday












  • @RonMaupin Fair point, though ::1 was just an obvious example. The same reasoning would apply also to other addresses.

    – a CVn
    16 hours ago

















  • If ::192.0.92.1 in IPv6 and 192.0.92.1 in IPv4 were equivalent and always referred to the same host (192.0.92.1 in IPv4-land), then how would a packet destined for ::0.0.0.1 be routed?

    – a CVn
    yesterday











  • @aCVn, IPv4 addresses in the 0.0.0.0/8 network cannot be destination addresses, anyway.

    – Ron Maupin
    yesterday






  • 3





    Beware of outdated textbooks. IPv4-compatible IPv6 addresses have been deprecated for almost 15 years, replaed by IPv4-mapped IPv6 addresses. Modern operating systems may not recognize them. See RFC 4291.

    – Michael Hampton
    yesterday












  • @RonMaupin Fair point, though ::1 was just an obvious example. The same reasoning would apply also to other addresses.

    – a CVn
    16 hours ago
















If ::192.0.92.1 in IPv6 and 192.0.92.1 in IPv4 were equivalent and always referred to the same host (192.0.92.1 in IPv4-land), then how would a packet destined for ::0.0.0.1 be routed?

– a CVn
yesterday





If ::192.0.92.1 in IPv6 and 192.0.92.1 in IPv4 were equivalent and always referred to the same host (192.0.92.1 in IPv4-land), then how would a packet destined for ::0.0.0.1 be routed?

– a CVn
yesterday













@aCVn, IPv4 addresses in the 0.0.0.0/8 network cannot be destination addresses, anyway.

– Ron Maupin
yesterday





@aCVn, IPv4 addresses in the 0.0.0.0/8 network cannot be destination addresses, anyway.

– Ron Maupin
yesterday




3




3





Beware of outdated textbooks. IPv4-compatible IPv6 addresses have been deprecated for almost 15 years, replaed by IPv4-mapped IPv6 addresses. Modern operating systems may not recognize them. See RFC 4291.

– Michael Hampton
yesterday






Beware of outdated textbooks. IPv4-compatible IPv6 addresses have been deprecated for almost 15 years, replaed by IPv4-mapped IPv6 addresses. Modern operating systems may not recognize them. See RFC 4291.

– Michael Hampton
yesterday














@RonMaupin Fair point, though ::1 was just an obvious example. The same reasoning would apply also to other addresses.

– a CVn
16 hours ago





@RonMaupin Fair point, though ::1 was just an obvious example. The same reasoning would apply also to other addresses.

– a CVn
16 hours ago










3 Answers
3






active

oldest

votes


















6















Are the IPv6 address space and IPv4 address space completely disjoint?




Yes, they are two separate, incompatible protocols with completely different addressing.



That book is out-of-date. The addressing to which it refers was deprecated a long time ago. it is referring to the old IPv4-Compatible addressing for IPv6 that was deprecated. See RFC 5156, Special-Use IPv6 Addresses:




2.3. IPv4-Compatible Addresses



::/96 are the IPv4-compatible addresses [RFC4291].
These addresses are deprecated and should not appear on the public
Internet.




There is IPv4-Mapped addressing for IPv6, but it is not really used as addressing for packets:




2.2. IPv4-Mapped Addresses



::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291]. Addresses
within this block should not appear on the public Internet.




Also see the referenced RFC 4291, IP Version 6 Addressing Architecture:




2.5.5. IPv6 Addresses with Embedded IPv4 Addresses



Two types of IPv6 addresses are defined that carry an IPv4 address in
the low-order 32 bits of the address. These are the "IPv4-Compatible
IPv6 address" and the "IPv4-mapped IPv6 address".



2.5.5.1. IPv4-Compatible IPv6 Address



The "IPv4-Compatible IPv6 address" was defined to assist in the IPv6
transition. The format of the "IPv4-Compatible IPv6 address" is as
follows:



| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|0000| IPv4 address |
+--------------------------------------+----+---------------------+


Note: The IPv4 address used in the "IPv4-Compatible IPv6 address" must
be a globally-unique IPv4 unicast address.



The "IPv4-Compatible IPv6 address" is now deprecated because the
current IPv6 transition mechanisms no longer use these addresses. New
or updated implementations are not required to support this address
type.



2.5.5.2. IPv4-Mapped IPv6 Address



A second type of IPv6 address that holds an embedded IPv4 address is
defined. This address type is used to represent the addresses of IPv4
nodes as IPv6 addresses. The format of the "IPv4-mapped IPv6 address"
is as follows:



| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|FFFF| IPv4 address |
+--------------------------------------+----+---------------------+


See [RFC4038] for background on the usage of the "IPv4-mapped
IPv6 address".






Does it mean the IPv4 address space is embedded into the lowest
subrange of the IPv6 address space?




Only under certain circumstances, but this is not normally recommended.




Is such embedding fixed? Can the IPv4 address space be embedded into
any continuous subrange of the IPv6 address space?




Only a couple of IPv6 address ranges are designed for this, and they are not used for sending packets. This is not used in Global IPv6 addressing.




Does it mean that for any IPv4 address, there is some IPv6 address
that refers to the same address as the IPv4 address?




Not really. Conceptually, yes, for IPv4-Mapped addressing for IPv6, but that is not actually used for sending packets.




For example, are ::192.31.20.46 and 192.31.20.46 effectively the
same address?



  • if I send a message to ::192.31.20.46, will 192.31.20.46 receive my message?

  • if I send a message to 192.31.20.46, will ::192.31.20.46 receive my message?

Will ::127.0.0.1 still be a loopback IP address, and if yes, is it
effectively the same address as 127.0.0.1?




No, ::192.31.20.46 is an invalid IPv6 address because the IPv4-Compatible addressing for IPv6 has been deprecated.



IPv4 and IPv6 are two separate, incompatible protocols that can coexist, but cannot directly communicate.



IPv6 has a loopback address of ::1.




Or are the IPv6 address space and IPv4 address space completely
disjoint (i.e. no overlapping), in the sense that when I communicate
with a IPv6 address, I will not communicate with a IPv4 address?




IPv4 and IPv6 have completely separate addressing. IPv4 uses 32-bit addressing that is incompatible with the IPv6 128-bit addressing. The protocol headers are also very different in other ways. IPv6 was created after lessons learned in IPv4. Remember that IPv4 was an academic/government experiment that was never intended to be used the way it is today, and IPv6 is an attempt to correct the deficiencies in IPv4, but it is incompatible with IPv4 because of that.






share|improve this answer
































    10














    Number 4 is correct. V4 and v6 protocols are completely different with different formats and addressing schemes. The two addresses have the same relationship as telephone numbers and lottery numbers— that is, none.



    There have been many proposed methods of mapping v4 to v6 to allow for protocol translation, but most are deprecated today.






    share|improve this answer























    • I like to use appletalk vs. ipx. (very clearly different systems)

      – Ricky Beam
      yesterday






    • 5





      @RickyBeam Ain’t many of us left who remember AppleTalk or ipx.

      – Ron Trunk
      yesterday











    • @RonTrunk, I used to install IPX on S-Net (Novell ShareNet), the Novell proprietary box. We installed a site for a company that moved to Austin, and the bulding drilled a floor hole for the printer cable, shorting a 208V line to the 120V line that served the S-Net Box. The board in the box looked like an atomic bomb went off. At the time, there were only two authorized Novell dealers in Texas (Houston and Dallas), and I had to travel to Dallas to get the replacement board (15,000 1986 dollars).

      – Ron Maupin
      yesterday



















    0














    I'm somewhat surprised that no existing answer mentioned 6to4.



    It allows to send an IPv6 packet to an IPv4 host, encapsulated within IPv4 packet of protocol type 41.



    6to4 addresses are of the type 2002:AABB:CCDD:suffix corresponding to IPv4 address A.B.C.D where A,B,C,D are decimal and AA,BB,CC,DD are hexadecimal. So, each IPv4 address actually has a whole /48 block of IPv6 addresses.



    6to4 is not just some notation mechanism allowing IPv4 addresses to be notated using IPv6 addresses, it's a real and working IPv6 transition mechanism.



    The performance and latency of 6to4 connectivity will be poor, however, so native IPv6 is preferred where such connectivity is available.



    So, my answer to IPv4 and IPv6 spaces being disjoint: not really, each IPv4 address has a /48 block of IPv6 addresses.






    share|improve this answer























    • The problem with your answer is that it leads people to believe that you can have an IPv6-only host directly communicate with an IPv4-only host or vice versa, and that simply isn't true. There is a lot more to it than that, including relay routers to translate the protocols, so, yes, the address space is still separate, but you have something that can talk in both protocols to do translation.

      – Ron Maupin
      14 hours ago










    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "496"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    noCode: true, onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f57903%2fare-the-ipv6-address-space-and-ipv4-address-space-completely-disjoint%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    6















    Are the IPv6 address space and IPv4 address space completely disjoint?




    Yes, they are two separate, incompatible protocols with completely different addressing.



    That book is out-of-date. The addressing to which it refers was deprecated a long time ago. it is referring to the old IPv4-Compatible addressing for IPv6 that was deprecated. See RFC 5156, Special-Use IPv6 Addresses:




    2.3. IPv4-Compatible Addresses



    ::/96 are the IPv4-compatible addresses [RFC4291].
    These addresses are deprecated and should not appear on the public
    Internet.




    There is IPv4-Mapped addressing for IPv6, but it is not really used as addressing for packets:




    2.2. IPv4-Mapped Addresses



    ::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291]. Addresses
    within this block should not appear on the public Internet.




    Also see the referenced RFC 4291, IP Version 6 Addressing Architecture:




    2.5.5. IPv6 Addresses with Embedded IPv4 Addresses



    Two types of IPv6 addresses are defined that carry an IPv4 address in
    the low-order 32 bits of the address. These are the "IPv4-Compatible
    IPv6 address" and the "IPv4-mapped IPv6 address".



    2.5.5.1. IPv4-Compatible IPv6 Address



    The "IPv4-Compatible IPv6 address" was defined to assist in the IPv6
    transition. The format of the "IPv4-Compatible IPv6 address" is as
    follows:



    | 80 bits | 16 | 32 bits |
    +--------------------------------------+--------------------------+
    |0000..............................0000|0000| IPv4 address |
    +--------------------------------------+----+---------------------+


    Note: The IPv4 address used in the "IPv4-Compatible IPv6 address" must
    be a globally-unique IPv4 unicast address.



    The "IPv4-Compatible IPv6 address" is now deprecated because the
    current IPv6 transition mechanisms no longer use these addresses. New
    or updated implementations are not required to support this address
    type.



    2.5.5.2. IPv4-Mapped IPv6 Address



    A second type of IPv6 address that holds an embedded IPv4 address is
    defined. This address type is used to represent the addresses of IPv4
    nodes as IPv6 addresses. The format of the "IPv4-mapped IPv6 address"
    is as follows:



    | 80 bits | 16 | 32 bits |
    +--------------------------------------+--------------------------+
    |0000..............................0000|FFFF| IPv4 address |
    +--------------------------------------+----+---------------------+


    See [RFC4038] for background on the usage of the "IPv4-mapped
    IPv6 address".






    Does it mean the IPv4 address space is embedded into the lowest
    subrange of the IPv6 address space?




    Only under certain circumstances, but this is not normally recommended.




    Is such embedding fixed? Can the IPv4 address space be embedded into
    any continuous subrange of the IPv6 address space?




    Only a couple of IPv6 address ranges are designed for this, and they are not used for sending packets. This is not used in Global IPv6 addressing.




    Does it mean that for any IPv4 address, there is some IPv6 address
    that refers to the same address as the IPv4 address?




    Not really. Conceptually, yes, for IPv4-Mapped addressing for IPv6, but that is not actually used for sending packets.




    For example, are ::192.31.20.46 and 192.31.20.46 effectively the
    same address?



    • if I send a message to ::192.31.20.46, will 192.31.20.46 receive my message?

    • if I send a message to 192.31.20.46, will ::192.31.20.46 receive my message?

    Will ::127.0.0.1 still be a loopback IP address, and if yes, is it
    effectively the same address as 127.0.0.1?




    No, ::192.31.20.46 is an invalid IPv6 address because the IPv4-Compatible addressing for IPv6 has been deprecated.



    IPv4 and IPv6 are two separate, incompatible protocols that can coexist, but cannot directly communicate.



    IPv6 has a loopback address of ::1.




    Or are the IPv6 address space and IPv4 address space completely
    disjoint (i.e. no overlapping), in the sense that when I communicate
    with a IPv6 address, I will not communicate with a IPv4 address?




    IPv4 and IPv6 have completely separate addressing. IPv4 uses 32-bit addressing that is incompatible with the IPv6 128-bit addressing. The protocol headers are also very different in other ways. IPv6 was created after lessons learned in IPv4. Remember that IPv4 was an academic/government experiment that was never intended to be used the way it is today, and IPv6 is an attempt to correct the deficiencies in IPv4, but it is incompatible with IPv4 because of that.






    share|improve this answer





























      6















      Are the IPv6 address space and IPv4 address space completely disjoint?




      Yes, they are two separate, incompatible protocols with completely different addressing.



      That book is out-of-date. The addressing to which it refers was deprecated a long time ago. it is referring to the old IPv4-Compatible addressing for IPv6 that was deprecated. See RFC 5156, Special-Use IPv6 Addresses:




      2.3. IPv4-Compatible Addresses



      ::/96 are the IPv4-compatible addresses [RFC4291].
      These addresses are deprecated and should not appear on the public
      Internet.




      There is IPv4-Mapped addressing for IPv6, but it is not really used as addressing for packets:




      2.2. IPv4-Mapped Addresses



      ::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291]. Addresses
      within this block should not appear on the public Internet.




      Also see the referenced RFC 4291, IP Version 6 Addressing Architecture:




      2.5.5. IPv6 Addresses with Embedded IPv4 Addresses



      Two types of IPv6 addresses are defined that carry an IPv4 address in
      the low-order 32 bits of the address. These are the "IPv4-Compatible
      IPv6 address" and the "IPv4-mapped IPv6 address".



      2.5.5.1. IPv4-Compatible IPv6 Address



      The "IPv4-Compatible IPv6 address" was defined to assist in the IPv6
      transition. The format of the "IPv4-Compatible IPv6 address" is as
      follows:



      | 80 bits | 16 | 32 bits |
      +--------------------------------------+--------------------------+
      |0000..............................0000|0000| IPv4 address |
      +--------------------------------------+----+---------------------+


      Note: The IPv4 address used in the "IPv4-Compatible IPv6 address" must
      be a globally-unique IPv4 unicast address.



      The "IPv4-Compatible IPv6 address" is now deprecated because the
      current IPv6 transition mechanisms no longer use these addresses. New
      or updated implementations are not required to support this address
      type.



      2.5.5.2. IPv4-Mapped IPv6 Address



      A second type of IPv6 address that holds an embedded IPv4 address is
      defined. This address type is used to represent the addresses of IPv4
      nodes as IPv6 addresses. The format of the "IPv4-mapped IPv6 address"
      is as follows:



      | 80 bits | 16 | 32 bits |
      +--------------------------------------+--------------------------+
      |0000..............................0000|FFFF| IPv4 address |
      +--------------------------------------+----+---------------------+


      See [RFC4038] for background on the usage of the "IPv4-mapped
      IPv6 address".






      Does it mean the IPv4 address space is embedded into the lowest
      subrange of the IPv6 address space?




      Only under certain circumstances, but this is not normally recommended.




      Is such embedding fixed? Can the IPv4 address space be embedded into
      any continuous subrange of the IPv6 address space?




      Only a couple of IPv6 address ranges are designed for this, and they are not used for sending packets. This is not used in Global IPv6 addressing.




      Does it mean that for any IPv4 address, there is some IPv6 address
      that refers to the same address as the IPv4 address?




      Not really. Conceptually, yes, for IPv4-Mapped addressing for IPv6, but that is not actually used for sending packets.




      For example, are ::192.31.20.46 and 192.31.20.46 effectively the
      same address?



      • if I send a message to ::192.31.20.46, will 192.31.20.46 receive my message?

      • if I send a message to 192.31.20.46, will ::192.31.20.46 receive my message?

      Will ::127.0.0.1 still be a loopback IP address, and if yes, is it
      effectively the same address as 127.0.0.1?




      No, ::192.31.20.46 is an invalid IPv6 address because the IPv4-Compatible addressing for IPv6 has been deprecated.



      IPv4 and IPv6 are two separate, incompatible protocols that can coexist, but cannot directly communicate.



      IPv6 has a loopback address of ::1.




      Or are the IPv6 address space and IPv4 address space completely
      disjoint (i.e. no overlapping), in the sense that when I communicate
      with a IPv6 address, I will not communicate with a IPv4 address?




      IPv4 and IPv6 have completely separate addressing. IPv4 uses 32-bit addressing that is incompatible with the IPv6 128-bit addressing. The protocol headers are also very different in other ways. IPv6 was created after lessons learned in IPv4. Remember that IPv4 was an academic/government experiment that was never intended to be used the way it is today, and IPv6 is an attempt to correct the deficiencies in IPv4, but it is incompatible with IPv4 because of that.






      share|improve this answer



























        6












        6








        6








        Are the IPv6 address space and IPv4 address space completely disjoint?




        Yes, they are two separate, incompatible protocols with completely different addressing.



        That book is out-of-date. The addressing to which it refers was deprecated a long time ago. it is referring to the old IPv4-Compatible addressing for IPv6 that was deprecated. See RFC 5156, Special-Use IPv6 Addresses:




        2.3. IPv4-Compatible Addresses



        ::/96 are the IPv4-compatible addresses [RFC4291].
        These addresses are deprecated and should not appear on the public
        Internet.




        There is IPv4-Mapped addressing for IPv6, but it is not really used as addressing for packets:




        2.2. IPv4-Mapped Addresses



        ::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291]. Addresses
        within this block should not appear on the public Internet.




        Also see the referenced RFC 4291, IP Version 6 Addressing Architecture:




        2.5.5. IPv6 Addresses with Embedded IPv4 Addresses



        Two types of IPv6 addresses are defined that carry an IPv4 address in
        the low-order 32 bits of the address. These are the "IPv4-Compatible
        IPv6 address" and the "IPv4-mapped IPv6 address".



        2.5.5.1. IPv4-Compatible IPv6 Address



        The "IPv4-Compatible IPv6 address" was defined to assist in the IPv6
        transition. The format of the "IPv4-Compatible IPv6 address" is as
        follows:



        | 80 bits | 16 | 32 bits |
        +--------------------------------------+--------------------------+
        |0000..............................0000|0000| IPv4 address |
        +--------------------------------------+----+---------------------+


        Note: The IPv4 address used in the "IPv4-Compatible IPv6 address" must
        be a globally-unique IPv4 unicast address.



        The "IPv4-Compatible IPv6 address" is now deprecated because the
        current IPv6 transition mechanisms no longer use these addresses. New
        or updated implementations are not required to support this address
        type.



        2.5.5.2. IPv4-Mapped IPv6 Address



        A second type of IPv6 address that holds an embedded IPv4 address is
        defined. This address type is used to represent the addresses of IPv4
        nodes as IPv6 addresses. The format of the "IPv4-mapped IPv6 address"
        is as follows:



        | 80 bits | 16 | 32 bits |
        +--------------------------------------+--------------------------+
        |0000..............................0000|FFFF| IPv4 address |
        +--------------------------------------+----+---------------------+


        See [RFC4038] for background on the usage of the "IPv4-mapped
        IPv6 address".






        Does it mean the IPv4 address space is embedded into the lowest
        subrange of the IPv6 address space?




        Only under certain circumstances, but this is not normally recommended.




        Is such embedding fixed? Can the IPv4 address space be embedded into
        any continuous subrange of the IPv6 address space?




        Only a couple of IPv6 address ranges are designed for this, and they are not used for sending packets. This is not used in Global IPv6 addressing.




        Does it mean that for any IPv4 address, there is some IPv6 address
        that refers to the same address as the IPv4 address?




        Not really. Conceptually, yes, for IPv4-Mapped addressing for IPv6, but that is not actually used for sending packets.




        For example, are ::192.31.20.46 and 192.31.20.46 effectively the
        same address?



        • if I send a message to ::192.31.20.46, will 192.31.20.46 receive my message?

        • if I send a message to 192.31.20.46, will ::192.31.20.46 receive my message?

        Will ::127.0.0.1 still be a loopback IP address, and if yes, is it
        effectively the same address as 127.0.0.1?




        No, ::192.31.20.46 is an invalid IPv6 address because the IPv4-Compatible addressing for IPv6 has been deprecated.



        IPv4 and IPv6 are two separate, incompatible protocols that can coexist, but cannot directly communicate.



        IPv6 has a loopback address of ::1.




        Or are the IPv6 address space and IPv4 address space completely
        disjoint (i.e. no overlapping), in the sense that when I communicate
        with a IPv6 address, I will not communicate with a IPv4 address?




        IPv4 and IPv6 have completely separate addressing. IPv4 uses 32-bit addressing that is incompatible with the IPv6 128-bit addressing. The protocol headers are also very different in other ways. IPv6 was created after lessons learned in IPv4. Remember that IPv4 was an academic/government experiment that was never intended to be used the way it is today, and IPv6 is an attempt to correct the deficiencies in IPv4, but it is incompatible with IPv4 because of that.






        share|improve this answer
















        Are the IPv6 address space and IPv4 address space completely disjoint?




        Yes, they are two separate, incompatible protocols with completely different addressing.



        That book is out-of-date. The addressing to which it refers was deprecated a long time ago. it is referring to the old IPv4-Compatible addressing for IPv6 that was deprecated. See RFC 5156, Special-Use IPv6 Addresses:




        2.3. IPv4-Compatible Addresses



        ::/96 are the IPv4-compatible addresses [RFC4291].
        These addresses are deprecated and should not appear on the public
        Internet.




        There is IPv4-Mapped addressing for IPv6, but it is not really used as addressing for packets:




        2.2. IPv4-Mapped Addresses



        ::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291]. Addresses
        within this block should not appear on the public Internet.




        Also see the referenced RFC 4291, IP Version 6 Addressing Architecture:




        2.5.5. IPv6 Addresses with Embedded IPv4 Addresses



        Two types of IPv6 addresses are defined that carry an IPv4 address in
        the low-order 32 bits of the address. These are the "IPv4-Compatible
        IPv6 address" and the "IPv4-mapped IPv6 address".



        2.5.5.1. IPv4-Compatible IPv6 Address



        The "IPv4-Compatible IPv6 address" was defined to assist in the IPv6
        transition. The format of the "IPv4-Compatible IPv6 address" is as
        follows:



        | 80 bits | 16 | 32 bits |
        +--------------------------------------+--------------------------+
        |0000..............................0000|0000| IPv4 address |
        +--------------------------------------+----+---------------------+


        Note: The IPv4 address used in the "IPv4-Compatible IPv6 address" must
        be a globally-unique IPv4 unicast address.



        The "IPv4-Compatible IPv6 address" is now deprecated because the
        current IPv6 transition mechanisms no longer use these addresses. New
        or updated implementations are not required to support this address
        type.



        2.5.5.2. IPv4-Mapped IPv6 Address



        A second type of IPv6 address that holds an embedded IPv4 address is
        defined. This address type is used to represent the addresses of IPv4
        nodes as IPv6 addresses. The format of the "IPv4-mapped IPv6 address"
        is as follows:



        | 80 bits | 16 | 32 bits |
        +--------------------------------------+--------------------------+
        |0000..............................0000|FFFF| IPv4 address |
        +--------------------------------------+----+---------------------+


        See [RFC4038] for background on the usage of the "IPv4-mapped
        IPv6 address".






        Does it mean the IPv4 address space is embedded into the lowest
        subrange of the IPv6 address space?




        Only under certain circumstances, but this is not normally recommended.




        Is such embedding fixed? Can the IPv4 address space be embedded into
        any continuous subrange of the IPv6 address space?




        Only a couple of IPv6 address ranges are designed for this, and they are not used for sending packets. This is not used in Global IPv6 addressing.




        Does it mean that for any IPv4 address, there is some IPv6 address
        that refers to the same address as the IPv4 address?




        Not really. Conceptually, yes, for IPv4-Mapped addressing for IPv6, but that is not actually used for sending packets.




        For example, are ::192.31.20.46 and 192.31.20.46 effectively the
        same address?



        • if I send a message to ::192.31.20.46, will 192.31.20.46 receive my message?

        • if I send a message to 192.31.20.46, will ::192.31.20.46 receive my message?

        Will ::127.0.0.1 still be a loopback IP address, and if yes, is it
        effectively the same address as 127.0.0.1?




        No, ::192.31.20.46 is an invalid IPv6 address because the IPv4-Compatible addressing for IPv6 has been deprecated.



        IPv4 and IPv6 are two separate, incompatible protocols that can coexist, but cannot directly communicate.



        IPv6 has a loopback address of ::1.




        Or are the IPv6 address space and IPv4 address space completely
        disjoint (i.e. no overlapping), in the sense that when I communicate
        with a IPv6 address, I will not communicate with a IPv4 address?




        IPv4 and IPv6 have completely separate addressing. IPv4 uses 32-bit addressing that is incompatible with the IPv6 128-bit addressing. The protocol headers are also very different in other ways. IPv6 was created after lessons learned in IPv4. Remember that IPv4 was an academic/government experiment that was never intended to be used the way it is today, and IPv6 is an attempt to correct the deficiencies in IPv4, but it is incompatible with IPv4 because of that.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited yesterday

























        answered yesterday









        Ron MaupinRon Maupin

        67.7k1369126




        67.7k1369126





















            10














            Number 4 is correct. V4 and v6 protocols are completely different with different formats and addressing schemes. The two addresses have the same relationship as telephone numbers and lottery numbers— that is, none.



            There have been many proposed methods of mapping v4 to v6 to allow for protocol translation, but most are deprecated today.






            share|improve this answer























            • I like to use appletalk vs. ipx. (very clearly different systems)

              – Ricky Beam
              yesterday






            • 5





              @RickyBeam Ain’t many of us left who remember AppleTalk or ipx.

              – Ron Trunk
              yesterday











            • @RonTrunk, I used to install IPX on S-Net (Novell ShareNet), the Novell proprietary box. We installed a site for a company that moved to Austin, and the bulding drilled a floor hole for the printer cable, shorting a 208V line to the 120V line that served the S-Net Box. The board in the box looked like an atomic bomb went off. At the time, there were only two authorized Novell dealers in Texas (Houston and Dallas), and I had to travel to Dallas to get the replacement board (15,000 1986 dollars).

              – Ron Maupin
              yesterday
















            10














            Number 4 is correct. V4 and v6 protocols are completely different with different formats and addressing schemes. The two addresses have the same relationship as telephone numbers and lottery numbers— that is, none.



            There have been many proposed methods of mapping v4 to v6 to allow for protocol translation, but most are deprecated today.






            share|improve this answer























            • I like to use appletalk vs. ipx. (very clearly different systems)

              – Ricky Beam
              yesterday






            • 5





              @RickyBeam Ain’t many of us left who remember AppleTalk or ipx.

              – Ron Trunk
              yesterday











            • @RonTrunk, I used to install IPX on S-Net (Novell ShareNet), the Novell proprietary box. We installed a site for a company that moved to Austin, and the bulding drilled a floor hole for the printer cable, shorting a 208V line to the 120V line that served the S-Net Box. The board in the box looked like an atomic bomb went off. At the time, there were only two authorized Novell dealers in Texas (Houston and Dallas), and I had to travel to Dallas to get the replacement board (15,000 1986 dollars).

              – Ron Maupin
              yesterday














            10












            10








            10







            Number 4 is correct. V4 and v6 protocols are completely different with different formats and addressing schemes. The two addresses have the same relationship as telephone numbers and lottery numbers— that is, none.



            There have been many proposed methods of mapping v4 to v6 to allow for protocol translation, but most are deprecated today.






            share|improve this answer













            Number 4 is correct. V4 and v6 protocols are completely different with different formats and addressing schemes. The two addresses have the same relationship as telephone numbers and lottery numbers— that is, none.



            There have been many proposed methods of mapping v4 to v6 to allow for protocol translation, but most are deprecated today.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered yesterday









            Ron TrunkRon Trunk

            38.7k33780




            38.7k33780












            • I like to use appletalk vs. ipx. (very clearly different systems)

              – Ricky Beam
              yesterday






            • 5





              @RickyBeam Ain’t many of us left who remember AppleTalk or ipx.

              – Ron Trunk
              yesterday











            • @RonTrunk, I used to install IPX on S-Net (Novell ShareNet), the Novell proprietary box. We installed a site for a company that moved to Austin, and the bulding drilled a floor hole for the printer cable, shorting a 208V line to the 120V line that served the S-Net Box. The board in the box looked like an atomic bomb went off. At the time, there were only two authorized Novell dealers in Texas (Houston and Dallas), and I had to travel to Dallas to get the replacement board (15,000 1986 dollars).

              – Ron Maupin
              yesterday


















            • I like to use appletalk vs. ipx. (very clearly different systems)

              – Ricky Beam
              yesterday






            • 5





              @RickyBeam Ain’t many of us left who remember AppleTalk or ipx.

              – Ron Trunk
              yesterday











            • @RonTrunk, I used to install IPX on S-Net (Novell ShareNet), the Novell proprietary box. We installed a site for a company that moved to Austin, and the bulding drilled a floor hole for the printer cable, shorting a 208V line to the 120V line that served the S-Net Box. The board in the box looked like an atomic bomb went off. At the time, there were only two authorized Novell dealers in Texas (Houston and Dallas), and I had to travel to Dallas to get the replacement board (15,000 1986 dollars).

              – Ron Maupin
              yesterday

















            I like to use appletalk vs. ipx. (very clearly different systems)

            – Ricky Beam
            yesterday





            I like to use appletalk vs. ipx. (very clearly different systems)

            – Ricky Beam
            yesterday




            5




            5





            @RickyBeam Ain’t many of us left who remember AppleTalk or ipx.

            – Ron Trunk
            yesterday





            @RickyBeam Ain’t many of us left who remember AppleTalk or ipx.

            – Ron Trunk
            yesterday













            @RonTrunk, I used to install IPX on S-Net (Novell ShareNet), the Novell proprietary box. We installed a site for a company that moved to Austin, and the bulding drilled a floor hole for the printer cable, shorting a 208V line to the 120V line that served the S-Net Box. The board in the box looked like an atomic bomb went off. At the time, there were only two authorized Novell dealers in Texas (Houston and Dallas), and I had to travel to Dallas to get the replacement board (15,000 1986 dollars).

            – Ron Maupin
            yesterday






            @RonTrunk, I used to install IPX on S-Net (Novell ShareNet), the Novell proprietary box. We installed a site for a company that moved to Austin, and the bulding drilled a floor hole for the printer cable, shorting a 208V line to the 120V line that served the S-Net Box. The board in the box looked like an atomic bomb went off. At the time, there were only two authorized Novell dealers in Texas (Houston and Dallas), and I had to travel to Dallas to get the replacement board (15,000 1986 dollars).

            – Ron Maupin
            yesterday












            0














            I'm somewhat surprised that no existing answer mentioned 6to4.



            It allows to send an IPv6 packet to an IPv4 host, encapsulated within IPv4 packet of protocol type 41.



            6to4 addresses are of the type 2002:AABB:CCDD:suffix corresponding to IPv4 address A.B.C.D where A,B,C,D are decimal and AA,BB,CC,DD are hexadecimal. So, each IPv4 address actually has a whole /48 block of IPv6 addresses.



            6to4 is not just some notation mechanism allowing IPv4 addresses to be notated using IPv6 addresses, it's a real and working IPv6 transition mechanism.



            The performance and latency of 6to4 connectivity will be poor, however, so native IPv6 is preferred where such connectivity is available.



            So, my answer to IPv4 and IPv6 spaces being disjoint: not really, each IPv4 address has a /48 block of IPv6 addresses.






            share|improve this answer























            • The problem with your answer is that it leads people to believe that you can have an IPv6-only host directly communicate with an IPv4-only host or vice versa, and that simply isn't true. There is a lot more to it than that, including relay routers to translate the protocols, so, yes, the address space is still separate, but you have something that can talk in both protocols to do translation.

              – Ron Maupin
              14 hours ago















            0














            I'm somewhat surprised that no existing answer mentioned 6to4.



            It allows to send an IPv6 packet to an IPv4 host, encapsulated within IPv4 packet of protocol type 41.



            6to4 addresses are of the type 2002:AABB:CCDD:suffix corresponding to IPv4 address A.B.C.D where A,B,C,D are decimal and AA,BB,CC,DD are hexadecimal. So, each IPv4 address actually has a whole /48 block of IPv6 addresses.



            6to4 is not just some notation mechanism allowing IPv4 addresses to be notated using IPv6 addresses, it's a real and working IPv6 transition mechanism.



            The performance and latency of 6to4 connectivity will be poor, however, so native IPv6 is preferred where such connectivity is available.



            So, my answer to IPv4 and IPv6 spaces being disjoint: not really, each IPv4 address has a /48 block of IPv6 addresses.






            share|improve this answer























            • The problem with your answer is that it leads people to believe that you can have an IPv6-only host directly communicate with an IPv4-only host or vice versa, and that simply isn't true. There is a lot more to it than that, including relay routers to translate the protocols, so, yes, the address space is still separate, but you have something that can talk in both protocols to do translation.

              – Ron Maupin
              14 hours ago













            0












            0








            0







            I'm somewhat surprised that no existing answer mentioned 6to4.



            It allows to send an IPv6 packet to an IPv4 host, encapsulated within IPv4 packet of protocol type 41.



            6to4 addresses are of the type 2002:AABB:CCDD:suffix corresponding to IPv4 address A.B.C.D where A,B,C,D are decimal and AA,BB,CC,DD are hexadecimal. So, each IPv4 address actually has a whole /48 block of IPv6 addresses.



            6to4 is not just some notation mechanism allowing IPv4 addresses to be notated using IPv6 addresses, it's a real and working IPv6 transition mechanism.



            The performance and latency of 6to4 connectivity will be poor, however, so native IPv6 is preferred where such connectivity is available.



            So, my answer to IPv4 and IPv6 spaces being disjoint: not really, each IPv4 address has a /48 block of IPv6 addresses.






            share|improve this answer













            I'm somewhat surprised that no existing answer mentioned 6to4.



            It allows to send an IPv6 packet to an IPv4 host, encapsulated within IPv4 packet of protocol type 41.



            6to4 addresses are of the type 2002:AABB:CCDD:suffix corresponding to IPv4 address A.B.C.D where A,B,C,D are decimal and AA,BB,CC,DD are hexadecimal. So, each IPv4 address actually has a whole /48 block of IPv6 addresses.



            6to4 is not just some notation mechanism allowing IPv4 addresses to be notated using IPv6 addresses, it's a real and working IPv6 transition mechanism.



            The performance and latency of 6to4 connectivity will be poor, however, so native IPv6 is preferred where such connectivity is available.



            So, my answer to IPv4 and IPv6 spaces being disjoint: not really, each IPv4 address has a /48 block of IPv6 addresses.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 17 hours ago









            juhistjuhist

            37217




            37217












            • The problem with your answer is that it leads people to believe that you can have an IPv6-only host directly communicate with an IPv4-only host or vice versa, and that simply isn't true. There is a lot more to it than that, including relay routers to translate the protocols, so, yes, the address space is still separate, but you have something that can talk in both protocols to do translation.

              – Ron Maupin
              14 hours ago

















            • The problem with your answer is that it leads people to believe that you can have an IPv6-only host directly communicate with an IPv4-only host or vice versa, and that simply isn't true. There is a lot more to it than that, including relay routers to translate the protocols, so, yes, the address space is still separate, but you have something that can talk in both protocols to do translation.

              – Ron Maupin
              14 hours ago
















            The problem with your answer is that it leads people to believe that you can have an IPv6-only host directly communicate with an IPv4-only host or vice versa, and that simply isn't true. There is a lot more to it than that, including relay routers to translate the protocols, so, yes, the address space is still separate, but you have something that can talk in both protocols to do translation.

            – Ron Maupin
            14 hours ago





            The problem with your answer is that it leads people to believe that you can have an IPv6-only host directly communicate with an IPv4-only host or vice versa, and that simply isn't true. There is a lot more to it than that, including relay routers to translate the protocols, so, yes, the address space is still separate, but you have something that can talk in both protocols to do translation.

            – Ron Maupin
            14 hours ago

















            draft saved

            draft discarded
















































            Thanks for contributing an answer to Network Engineering Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f57903%2fare-the-ipv6-address-space-and-ipv4-address-space-completely-disjoint%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            getting Checkpoint VPN SSL Network Extender working in the command lineHow to connect to CheckPoint VPN on Ubuntu 18.04LTS?Will the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayVPN SSL Network Extender in FirefoxLinux Checkpoint SNX tool configuration issuesCheck Point - Connect under Linux - snx + OTPSNX VPN Ububuntu 18.XXUsing Checkpoint VPN SSL Network Extender CLI with certificateVPN with network manager (nm-applet) is not workingWill the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayImport VPN config files to NetworkManager from command lineTrouble connecting to VPN using network-manager, while command line worksStart a VPN connection with PPTP protocol on command linestarting a docker service daemon breaks the vpn networkCan't connect to vpn with Network-managerVPN SSL Network Extender in FirefoxUsing Checkpoint VPN SSL Network Extender CLI with certificate

            Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition

            Marilyn Monroe Ny fiainany manokana | Jereo koa | Meny fitetezanafanitarana azy.