Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

isurg

  1. Home
  2. Technology
  3. IPv6 adoption statistics – Google

IPv6 adoption statistics – Google

Scheduled Pinned Locked Moved Technology
technology
9 Posts 5 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L This user is from outside of this forum
    L This user is from outside of this forum
    lemmydividebyzero@reddthat.com
    wrote last edited by
    #1
    This post did not contain any content.
    Link Preview Image
    IPv6 – Google

    favicon

    (www.google.com)

    treadful@lemmy.zipT 1 Reply Last reply
    0
    • L lemmydividebyzero@reddthat.com
      This post did not contain any content.
      Link Preview Image
      IPv6 – Google

      favicon

      (www.google.com)

      treadful@lemmy.zipT This user is from outside of this forum
      treadful@lemmy.zipT This user is from outside of this forum
      treadful@lemmy.zip
      wrote last edited by
      #2

      I gotta suck it up and learn IPv6. My ISP now provides me with a /64. But I feel like I have a lot of knowledge gaps on their features so I'm worried about security. Especially with all the new features like SLAAC.

      What's the best crash course these days? Go through Cisco materials or something?

      C 1 Reply Last reply
      0
      • treadful@lemmy.zipT treadful@lemmy.zip

        I gotta suck it up and learn IPv6. My ISP now provides me with a /64. But I feel like I have a lot of knowledge gaps on their features so I'm worried about security. Especially with all the new features like SLAAC.

        What's the best crash course these days? Go through Cisco materials or something?

        C This user is from outside of this forum
        C This user is from outside of this forum
        cmnybo@discuss.tchncs.de
        wrote last edited by
        #3

        You need to find out if your ISP supports prefix delegation. A /64 will only give you one subnet. An ISP should supply a /56 if your router requests it. There are some bad ISPs out there that won't though.

        treadful@lemmy.zipT 1 Reply Last reply
        0
        • C cmnybo@discuss.tchncs.de

          You need to find out if your ISP supports prefix delegation. A /64 will only give you one subnet. An ISP should supply a /56 if your router requests it. There are some bad ISPs out there that won't though.

          treadful@lemmy.zipT This user is from outside of this forum
          treadful@lemmy.zipT This user is from outside of this forum
          treadful@lemmy.zip
          wrote last edited by
          #4

          Doesn't a /64 already give me more than I'll ever use?

          C 1 Reply Last reply
          0
          • treadful@lemmy.zipT treadful@lemmy.zip

            Doesn't a /64 already give me more than I'll ever use?

            C This user is from outside of this forum
            C This user is from outside of this forum
            cmnybo@discuss.tchncs.de
            wrote last edited by
            #5

            An IPv6 subnet must be /64. Anything else breaks stuff. If you want a separate network for guests or IoT devices, a single /64 won't be enough because it can't be divided up any smaller.

            treadful@lemmy.zipT 1 Reply Last reply
            0
            • C cmnybo@discuss.tchncs.de

              An IPv6 subnet must be /64. Anything else breaks stuff. If you want a separate network for guests or IoT devices, a single /64 won't be enough because it can't be divided up any smaller.

              treadful@lemmy.zipT This user is from outside of this forum
              treadful@lemmy.zipT This user is from outside of this forum
              treadful@lemmy.zip
              wrote last edited by
              #6

              You can't subnet below a /64 at all? Or it just makes things like SLAAC/auto-addressing using the MAC address unusable?

              N 1 Reply Last reply
              0
              • treadful@lemmy.zipT treadful@lemmy.zip

                You can't subnet below a /64 at all? Or it just makes things like SLAAC/auto-addressing using the MAC address unusable?

                N This user is from outside of this forum
                N This user is from outside of this forum
                nonentity@sh.itjust.works
                wrote last edited by
                #7

                The only legitimate v6 prefix smaller than /64 is /127, to be used for point to point links, similar to /31’s in v4, but these aren’t processed for routing outside of the boxes the link is configured on.

                The concepts of addressing for v4 and v6 don’t map 1:1.

                From the perspective of the internet, and any properly configured routing infrastructure, they should only ever be interested in the first 64 bits when routing, the second 64 should be exclusively the domain of the last segment. It’s like inserting an additional type of addressing between the routing portion and the protocol port.

                You kind of have this with v4, but it’s variable, particularly since CIDR shot the v4 address classes in the head, so the equipment had to be able to process the entire address with every routing lookup and other functions.

                treadful@lemmy.zipT 1 Reply Last reply
                0
                • N nonentity@sh.itjust.works

                  The only legitimate v6 prefix smaller than /64 is /127, to be used for point to point links, similar to /31’s in v4, but these aren’t processed for routing outside of the boxes the link is configured on.

                  The concepts of addressing for v4 and v6 don’t map 1:1.

                  From the perspective of the internet, and any properly configured routing infrastructure, they should only ever be interested in the first 64 bits when routing, the second 64 should be exclusively the domain of the last segment. It’s like inserting an additional type of addressing between the routing portion and the protocol port.

                  You kind of have this with v4, but it’s variable, particularly since CIDR shot the v4 address classes in the head, so the equipment had to be able to process the entire address with every routing lookup and other functions.

                  treadful@lemmy.zipT This user is from outside of this forum
                  treadful@lemmy.zipT This user is from outside of this forum
                  treadful@lemmy.zip
                  wrote last edited by
                  #8

                  From the perspective of the internet, and any properly configured routing infrastructure, they should only ever be interested in the first 64 bits when routing, the second 64 should be exclusively the domain of the last segment.

                  Interesting. But routers don't actually strip that, do they? So the endpoint I'm communicating with will still get the full /128 address? I'm concerned about the privacy implications of MAC addresses being sent to everybody and their mother.

                  P 1 Reply Last reply
                  0
                  • treadful@lemmy.zipT treadful@lemmy.zip

                    From the perspective of the internet, and any properly configured routing infrastructure, they should only ever be interested in the first 64 bits when routing, the second 64 should be exclusively the domain of the last segment.

                    Interesting. But routers don't actually strip that, do they? So the endpoint I'm communicating with will still get the full /128 address? I'm concerned about the privacy implications of MAC addresses being sent to everybody and their mother.

                    P This user is from outside of this forum
                    P This user is from outside of this forum
                    partial_accumen@lemmy.world
                    wrote last edited by
                    #9

                    I’m concerned about the privacy implications of MAC addresses being sent to everybody and their mother.

                    Unless something has drastically changed from my understanding MAC addresses only operate on Layer 2 (Data Link). Anything IP related is handled at Layer 3 (Network). MAC addresses aren't routable, so the chatter where MAC addresses would happen don't make it to the other side of a router on another network interface.

                    1 Reply Last reply
                    0

                    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                    With your input, this post could be even better 💗

                    Register Login
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • World
                    • Users
                    • Groups