Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Split up IPv6 /36 using VLAN

    Scheduled Pinned Locked Moved IPv6
    17 Posts 7 Posters 1.8k Views
    Loading More Posts
    • 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.
    • JKnottJ
      JKnott
      last edited by

      ^^^^
      That article can be translated.  However, if an organization is world wide, then they might want to have blocks from the various regions.  One of the reasons for having such a large address space is to have address blocks tied to a region, to reduce the size of routing tables.  There was a problem a few years back, where the memory of some routers was overloaded, causing routing failures.

      PfSense running on Qotom mini PC
      i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
      UniFi AC-Lite access point

      I haven't lost my mind. It's around here...somewhere...

      1 Reply Last reply Reply Quote 0
      • B
        bimmerdriver
        last edited by

        @johnpoz:

        I don't see anyone giving out a /36 to one site.. I take it typo or misunderstanding from a /56.. Why would you give such a large network to a site?  /48 is the typical site space…  ARIN or any RIR would give you as an ISP in your initial space a /32... Why would said isp give out 16th of their /32 space to 1 site?  Doesn't allow for that many sites..  Sure you can more space, but doesn't make a lot of sense to give out such big chunks.

        So I could give out 65K /48 or 16 /36 ;)  Which would do you think you should give out?

        Didn't comcast get a /9 which was a HUGE freaking allocation... Doesn't allow for a lot of customers if you give away such large chunks of your space..  Even if you had a /9

        While I agree sure lets give everyone on the planet a /36... There for sure is plenty to go around, but that is how we ran into trouble with ipv4 - lack of management of the space..  A /48 allows for a HUGE network!!  65k /64's there would be zero reason for a /36 to one site.. You might give that to a region of your global network if you had say a /32 to work with..

        IMO, it's just stupid giving out a /36 to any single organization. Even a /56 is overkill for end-users. Sure, there are 64 bits of networks, but pissing it away in such massive chunks at this early stage in its adoption is short-sighted.

        1 Reply Last reply Reply Quote 0
        • ?
          Guest
          last edited by

          IoT - Everything will be connected to the Internet. For example, your underpants will be connected one day. Rather then changing them every day, they will email you when they require changing, this will save on laundry and thus this is eco friendly and saving the planet. This applies to all garments, under and over, in fact all forms of apparel.

          Thus you can start to see how a basic /56 allocation for each person on the planet will be the bare minimum, those with larger wardrobes, like my wife, mainly down to her handbags and shoes, will of course need to apply possibly for a /48.

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            IPv6 really shouldn't be thought of in terms of host address counts.

            There are 18-billion-billion host addresses in the standard interface subnet (/64). That amount of hosts on one subnet is, for all intents and purposes, infinite and not worthy of any consideration or thought. The 64 host bits in a /64 interface subnet simply do not exist from a network design perspective. And no, it is NOT wasteful. Just get over it, set your /64 interface subnets, and move on.

            IPv6 should be thought of in terms of available networks to delegate to different to sites (The /36 mentioned here could delegate to 4096 /48,  65536 /52, or  1.048M /56 sites) or in terms of the number of available interfaces (/64 of course) at that site (/48 = 65536, /52 = 4096, /56 = 256).

            That is why assigning a /48 to any reasonably-sized campus is not obscene. If they decide to set up some VPNs or whatever out of that they only have 256 /56s (or 16 /52s, or 4096 /60s) to play with. When you start splitting the space up like it is intended, you start to get down to numbers the typical dude can understand - like 256 and 16.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator
              last edited by

              Well put Derelict.. Which was the point I was trying to make myself ;)

              Its not about the number addresses in that space, its the number of prefixes that can be used under it.. I just do not see handing a specific site/user a /36 – makes zero sense.. Then take into account they do not even know how to subnet it ;)  And points to typo even more..

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

              1 Reply Last reply Reply Quote 0
              • JKnottJ
                JKnott
                last edited by

                IMO, it's just stupid giving out a /36 to any single organization. Even a /56 is overkill for end-users. Sure, there are 64 bits of networks, but pissing it away in such massive chunks at this early stage in its adoption is short-sighted.

                One reason for the huge address space is so that it won't be necessary to worry about saving addresses.  Bear in mind, only 1/8th of the entire IPv6 address space is used for unique global addresses and a much smaller amount for everything else.  This means well over 3/4s of the address space has not been assigned any purpose and is available if needed.

                PfSense running on Qotom mini PC
                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                UniFi AC-Lite access point

                I haven't lost my mind. It's around here...somewhere...

                1 Reply Last reply Reply Quote 0
                • B
                  bimmerdriver
                  last edited by

                  @johnpoz:

                  Well put Derelict.. Which was the point I was trying to make myself ;)

                  Its not about the number addresses in that space, its the number of prefixes that can be used under it.. I just do not see handing a specific site/user a /36 – makes zero sense.. Then take into account they do not even know how to subnet it ;)  And points to typo even more..

                  My point was not about 64 bits on an individual network, it was about squandering networks. This is the money quote.

                  1 Reply Last reply Reply Quote 0
                  • JKnottJ
                    JKnott
                    last edited by

                    @bimmerdriver:

                    Its not about the number addresses in that space, its the number of prefixes that can be used under it.. I just do not see handing a specific site/user a /36 – makes zero sense.. Then take into account they do not even know how to subnet it ;)  And points to typo even more..

                    My point was not about 64 bits on an individual network, it was about squandering networks. This is the money quote.

                    Given the huge address space, there's plenty to squander.  That was intentional.  As I mentioned above, there are enough addresses to give every person on earth a /36.  That's 4096 /48s each.  Seems to me there's plenty to squander.  Unlike IPv4, we don't have to squeeze out every last address.  The immense size of the IPv6 address space is pretty much inconceivable, until you start making comparisons.  For example, a single /64 has as many addresses as the entire IPv4 address space squared!  And there are the same number of /64 prefixes.  That is, for every single IPv4 address, there are over 4 billion /64 prefixes.  It would really take some effort to run out of IPv6 address, even with only 1/8th the address space being used.  The address space was made huge, to avoid worrying about such things.

                    Here's another interesting comparison.  I recently watched a show about multiple universes.  One point made is there are about 10^80 elementary particles in the entire known universe.  Well, 2^128 is about 3.4 x 10^38 addresses, so if you take that number, multiply by 30 and then square the result, you're in the same ball park as the number of particles in the universe.  128 bits provides a LOT of addresses.

                    PfSense running on Qotom mini PC
                    i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                    UniFi AC-Lite access point

                    I haven't lost my mind. It's around here...somewhere...

                    1 Reply Last reply Reply Quote 0
                    • B
                      bimmerdriver
                      last edited by

                      Everyone here understands powers of two. Just because you think you can squander addresses does not mean you should, particularly when it would take no additional effort to not squander them. As was said, there are no reasons to allocate a /36 when a /56 is far in excess of what most people could ever use.

                      1 Reply Last reply Reply Quote 0
                      • DerelictD
                        Derelict LAYER 8 Netgate
                        last edited by

                        (I don't think OP (who vanished) got a /36)

                        Chattanooga, Tennessee, USA
                        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                        Do Not Chat For Help! NO_WAN_EGRESS(TM)

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.