{"id":37766,"date":"2019-08-14T02:49:16","date_gmt":"2019-08-14T02:49:16","guid":{"rendered":"https:\/\/mec.ph\/?p=37766"},"modified":"2022-02-16T17:33:07","modified_gmt":"2022-02-16T09:33:07","slug":"ip-address-plan","status":"publish","type":"post","link":"https:\/\/mec.ph\/aruba-news\/ip-address-plan\/","title":{"rendered":"Aruba Networks: Developing an IP Address Plan for Wi-Fi"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

Architecture\u00a0overview<\/strong><\/h3>

Your address\u00a0plan\u00a0ought to\u00a0be created in conjunction\u00a0with your\u00a0wireless<\/a>\u00a0design.\u00a0Wireless APs<\/a>\u00a0among\u00a0your four-building\u00a0campus, managed by controllers in your off-campus\u00a0data\u00a0center,\u00a0can\u00a0have address allocation\u00a0significantly different\u00a0from\u00a0a worldwide\u00a0environment\u00a0with controllers in\u00a0every\u00a0workplace<\/a>. Additionally, forcing all wireless traffic through a tagged VLAN on your centrally placed controllers instead of dumping traffic local to the end-user LAN changes the plan and troubleshooting strategies.<\/p>

\u00a0<\/p>

As I\u00a0run through\u00a0an\u00a0address\u00a0plan\u00a0for wireless, I approach it in\u00a0IP\u00a0address-to-User ratios\u00a0based on\u00a0SSID\u00a0function\u00a0and region. Sound odd? Follow me\u00a0on this.<\/p>

\u00a0<\/p>