{"id":147,"date":"2017-06-17T23:27:58","date_gmt":"2017-06-18T05:27:58","guid":{"rendered":"https:\/\/datashed.tech\/?p=147"},"modified":"2017-06-17T23:27:58","modified_gmt":"2017-06-18T05:27:58","slug":"vlan-renumbering-plan-and-ip-addressing","status":"publish","type":"post","link":"https:\/\/datashed.tech\/index.php\/2017\/06\/17\/vlan-renumbering-plan-and-ip-addressing\/","title":{"rendered":"VLAN Renumbering Plan and IP Addressing"},"content":{"rendered":"<p>Currently, the datashed&#8217;s VLAN setup is far from ideal:<\/p>\n<ul>\n<li>There are several VLANs that are no longer used or needed.<\/li>\n<li>I&#8217;d like to have out-of-band management stuff on VLAN ID #1 (the native VLAN). This is desirable in order to prevent management functions from being inaccessible in the case of VLAN database corruption.<\/li>\n<li>I&#8217;d like to begin using \/16 blocks for the IPv4 addressing of internal subnets, instead of the current \/24 blocks.<\/li>\n<li>I would like the second octet of each subnet to represent its VLAN ID (i.e., VLAN 5 would be 10.5.0.0\/16). Obviously, I don&#8217;t currently intend to have more than 127 VLANs any time soon, although there are 4096 possible VLAN IDs in the basic standard.<\/li>\n<li>I consider this a prerequisite for my plans of implementing IPv6 internally (the network already implements full IPv6 on the Internet-facing side).<\/li>\n<li>I also consider this a prerequisite for setting up a VPN to allow internal network access from remote locations.<\/li>\n<\/ul>\n<p>I am also trying to get two \/29\u00a0blocks of public IPv4 addresses in addition to the existing \/27 and \/28 blocks (which will ultimately become \/24 blocks, at the smallest). This will fix some routing problems I&#8217;m currently having.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Currently, the datashed&#8217;s VLAN setup is far from ideal: There are several VLANs that are no longer used or needed. I&#8217;d like to have out-of-band management&#46;&#46;&#46;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[6],"tags":[],"_links":{"self":[{"href":"https:\/\/datashed.tech\/index.php\/wp-json\/wp\/v2\/posts\/147"}],"collection":[{"href":"https:\/\/datashed.tech\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/datashed.tech\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/datashed.tech\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/datashed.tech\/index.php\/wp-json\/wp\/v2\/comments?post=147"}],"version-history":[{"count":1,"href":"https:\/\/datashed.tech\/index.php\/wp-json\/wp\/v2\/posts\/147\/revisions"}],"predecessor-version":[{"id":148,"href":"https:\/\/datashed.tech\/index.php\/wp-json\/wp\/v2\/posts\/147\/revisions\/148"}],"wp:attachment":[{"href":"https:\/\/datashed.tech\/index.php\/wp-json\/wp\/v2\/media?parent=147"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/datashed.tech\/index.php\/wp-json\/wp\/v2\/categories?post=147"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/datashed.tech\/index.php\/wp-json\/wp\/v2\/tags?post=147"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}