ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Switching subnet /24 to /23

    IT Discussion
    7
    40
    6.5k
    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.
    • DustinB3403D
      DustinB3403
      last edited by

      As a business or home user you will likely never need IPv6.

      1 Reply Last reply Reply Quote 1
      • DustinB3403D
        DustinB3403
        last edited by

        IPv6 is for the world, as there are hundreds of billions of available IP addresses.

        1 Reply Last reply Reply Quote 1
        • L
          LAH3385 @JaredBusch
          last edited by

          @JaredBusch said:

          This is easy, you just have to plan it out. Note, you cannot "change" the scope of your DHCP server. You can choose to add another or wipe it and reimport it via PowerShell (what I typically do).

          1. Understand what your new range will be. Since you are on X.X.1.X/24. the new scope will be X.X.0.X/23.
          2. Update your router LAN IP to use the /23. If it was X.X.1.1/24, it is now X.X.1.1/23.
          3. Update your DC (asusming a WIndows network here) to use the new /23.
          4. Put a test device manually on X.X.0.X/23 and make sure you have internet and can ping the DC.
          5. Update all of your static devices to the /23.
          6. Export the DHCP Scope via PowerShell Export-DhcpServer -ComputerName dhcpserver.contoso.com -File C:\exportdir\dhcpexport.xml
          7. Edit the XML file to expand the scope. Here is an example of one I did this on a couple years ago. Basically change the ScopeID, SubnetMask, StartRange, and add an ExclusionRange for the entire X.X.0.1-X.X.0.255 initially. You can delete this exclusion in the GUI later when you are ready to use it.
            0_1458057915602_upload-d032b659-e66f-40cc-90f5-40be59de11d2
          8. Delete your current DHCP scope from the GUI.
          9. Import the updated scope from PowerShell. Import-DhcpServer -ComputerName dhcpserver.contoso.com -File C:\exports\dhcpexport.xml.
          10. Refresh the GUI, enable the scope, restart the service, etc.
          11. Make sure all the settings migrated in correctly.
          12. Force a machine to DHCP renew and you are done.

          Does this looks about right? 1.1-1.30 belong to current static IP addresses
          0_1458133908175_upload-53d7ed7b-6417-4b54-b646-f945e4953e54

          JaredBuschJ 1 Reply Last reply Reply Quote 0
          • JaredBuschJ
            JaredBusch @LAH3385
            last edited by

            @LAH3385 You noted the subnetmask as a /22 but noted the end range as 1.254. The end range of a /22 is 3.254.

            0_1458134281881_upload-97bd05bf-9d79-4265-a3f0-f0eeabb331c9

            1 Reply Last reply Reply Quote 1
            • coliverC
              coliver
              last edited by

              Am I reading that right that you want to to exclude the entire 192.168.0.1/24 subnet?

              L 1 Reply Last reply Reply Quote 0
              • L
                LAH3385 @coliver
                last edited by

                @coliver said:

                Am I reading that right that you want to to exclude the entire 192.168.0.1/24 subnet?

                For the time being. yes. It will be open to public later. I don't have a solid game plan yet so might as well keep everything the way it is (starting at .1.xx)

                coliverC 1 Reply Last reply Reply Quote 0
                • coliverC
                  coliver @LAH3385
                  last edited by

                  @LAH3385 said:

                  @coliver said:

                  Am I reading that right that you want to to exclude the entire 192.168.0.1/24 subnet?

                  For the time being. yes. It will be open to public later. I don't have a solid game plan yet so might as well keep everything the way it is (starting at .1.xx)

                  Ah, ok I was just checking.

                  JaredBuschJ 1 Reply Last reply Reply Quote 0
                  • JaredBuschJ
                    JaredBusch @coliver
                    last edited by

                    @coliver said:

                    @LAH3385 said:

                    @coliver said:

                    Am I reading that right that you want to to exclude the entire 192.168.0.1/24 subnet?

                    For the time being. yes. It will be open to public later. I don't have a solid game plan yet so might as well keep everything the way it is (starting at .1.xx)

                    Ah, ok I was just checking.

                    It is what I told him to do for the immediate change over. I suggested it, because every time I open up a range, I find something that was missed and suddenly people cannot do whatever task they need to.

                    1 Reply Last reply Reply Quote 2
                    • L
                      LAH3385
                      last edited by

                      @JaredBusch
                      To make it simpler for me. Would /22 starting at 192.168.1.1 to 192.168.4.254 better than 192.168.0.1 to 192.168.3.254?

                      coliverC DashrenderD 2 Replies Last reply Reply Quote 0
                      • coliverC
                        coliver @LAH3385
                        last edited by coliver

                        @LAH3385 said:

                        @JaredBusch
                        To make it simpler for me. Would /22 starting at 192.168.1.1 to 192.168.4.254 better than 192.168.0.1 to 192.168.3.254?

                        The /22 network that include 192.168.4.1 is 192.168.4.0-192.168.7.254.

                        1 Reply Last reply Reply Quote 0
                        • DashrenderD
                          Dashrender @LAH3385
                          last edited by

                          @LAH3385 said:

                          @JaredBusch
                          To make it simpler for me. Would /22 starting at 192.168.1.1 to 192.168.4.254 better than 192.168.0.1 to 192.168.3.254?

                          it doesn't work that way. You don't get to pick which addresses are part of your /22, the layout of bits in the subnet mask do.

                          1 Reply Last reply Reply Quote 0
                          • DashrenderD
                            Dashrender
                            last edited by

                            Here is a page that talks about how subnetting works, and why it works how it does.
                            https://www.techopedia.com/6/28587/internet/8-steps-to-understanding-ip-subnetting/3

                            1 Reply Last reply Reply Quote 0
                            • L
                              LAH3385
                              last edited by

                              I see.. Gotta play by their rules.

                              JaredBuschJ DashrenderD scottalanmillerS 3 Replies Last reply Reply Quote 0
                              • JaredBuschJ
                                JaredBusch @LAH3385
                                last edited by

                                @LAH3385 said:

                                I see.. Gotta play by their rules.

                                Look at the screenshot provided above, it shows you the range.

                                1 Reply Last reply Reply Quote 0
                                • DashrenderD
                                  Dashrender @LAH3385
                                  last edited by

                                  @LAH3385 said:

                                  I see.. Gotta play by their rules.

                                  Lol thier rules? You're kidding right?

                                  This is all math and the way binary works... They are not just made up rules someone randomly decided to make.

                                  JaredBuschJ 1 Reply Last reply Reply Quote 2
                                  • JaredBuschJ
                                    JaredBusch @Dashrender
                                    last edited by

                                    @Dashrender said:

                                    They are not just made up rules someone randomly decided to make.

                                    lies! it is magic!

                                    1 Reply Last reply Reply Quote 3
                                    • scottalanmillerS
                                      scottalanmiller @LAH3385
                                      last edited by

                                      @LAH3385 said:

                                      I see.. Gotta play by their rules.

                                      The rules of the universe, yes.

                                      1 Reply Last reply Reply Quote 0
                                      • 1
                                      • 2
                                      • 2 / 2
                                      • First post
                                        Last post