Vai al contenuto principale

Progettista di sottoreti iPSK e scope DHCP multi-tenant

Pianifica le allocazioni IP e i parametri DHCP per le reti di appartamenti e studentati utilizzando Identity Pre-Shared Keys.

Pianifica l'allocazione delle subnet

1. Base IP address range

Enter the starting private IP address block for the property.

2. Number of units

Total isolated resident apartments or student flats in the building.

3. Devices per unit

10 Devices
Expected limit of smart home, gaming console, and mobile devices per apartment.
Calculated parent network block
10.0.0.0/21

To support 100 units with up to 10 devices each, you need 16 IP addresses per unit. This requires allocating a parent network of 2,048 total IPs.

Subnet Mask per Unit255.255.255.240 (/28)
Usable IPs per Unit14 usable
Allocated IPs Total1,600 / 2,048
DHCP Lease Time24 Hours

Subnet allocation table (First 5 units)

Unit #Subnet CIDRGateway IPUsable DHCP Scope RangeVLAN Tag
Apartment 110.0.0.0/2810.0.0.110.0.0.2 - 10.0.0.14VLAN 101
Apartment 210.0.0.16/2810.0.0.1710.0.0.18 - 10.0.0.30VLAN 102
Apartment 310.0.0.32/2810.0.0.3310.0.0.34 - 10.0.0.46VLAN 103
Apartment 410.0.0.48/2810.0.0.4910.0.0.50 - 10.0.0.62VLAN 104
Apartment 510.0.0.64/2810.0.0.6510.0.0.66 - 10.0.0.78VLAN 105

Wireless controller config generator

Select your vendor stack to generate template scripts.

# Meraki MX Security Appliance DHCP Scope Configuration (VLANs 101 to 200)
# Copy-paste this setup template to deploy tenant isolation

# Global iPSK SSID settings:
# SSID Name: BTR Private Resident WiFi
# Association: WPA2 / WPA3 Enterprise with iPSK
# VLAN Allocation: Dynamic (via RADIUS User-Vlan-Id attribute)

# Sample scope configuration block:

# Apartment Unit 1 Configuration
vlan_101:
  name: "Apartment_1"
  id: 101
  ip: "10.0.0.1"
  subnet: "255.255.255.240"
  dhcp_start: "10.0.0.2"
  dhcp_end: "10.0.0.14"
  dns: "8.8.8.8, 1.1.1.1"
  lease_time: "24 Hours (86400s)"

# Apartment Unit 2 Configuration
vlan_102:
  name: "Apartment_2"
  id: 102
  ip: "10.0.0.17"
  subnet: "255.255.255.240"
  dhcp_start: "10.0.0.18"
  dhcp_end: "10.0.0.30"
  dns: "8.8.8.8, 1.1.1.1"
  lease_time: "24 Hours (86400s)"

# Apartment Unit 3 Configuration
vlan_103:
  name: "Apartment_3"
  id: 103
  ip: "10.0.0.33"
  subnet: "255.255.255.240"
  dhcp_start: "10.0.0.34"
  dhcp_end: "10.0.0.46"
  dns: "8.8.8.8, 1.1.1.1"
  lease_time: "24 Hours (86400s)"

# Apartment Unit 4 Configuration
vlan_104:
  name: "Apartment_4"
  id: 104
  ip: "10.0.0.49"
  subnet: "255.255.255.240"
  dhcp_start: "10.0.0.50"
  dhcp_end: "10.0.0.62"
  dns: "8.8.8.8, 1.1.1.1"
  lease_time: "24 Hours (86400s)"

# Apartment Unit 5 Configuration
vlan_105:
  name: "Apartment_5"
  id: 105
  ip: "10.0.0.65"
  subnet: "255.255.255.240"
  dhcp_start: "10.0.0.66"
  dhcp_end: "10.0.0.78"
  dns: "8.8.8.8, 1.1.1.1"
  lease_time: "24 Hours (86400s)"

Progettazione tecnica della rete per gestori immobiliari

Le Identity Pre-Shared Keys consentono alle proprietà multi-tenant di ospitare un singolo SSID, isolando al contempo i dispositivi di ciascun appartamento nella propria VLAN privata. Questo strumento di progettazione aiuta gli ingegneri a dimensionare lo spazio IP principale, definire gli scope DHCP e allocare sottoreti pulite.

Variabili di progettazione della rete

  • Isolamento VLAN per unità abitativa per dispositivi smart home e di gioco.
  • Dimensionamento della durata del lease dello scope DHCP per prevenire l'esaurimento degli indirizzi.
  • Generazione diretta di modelli di configurazione per i principali controller wireless enterprise.

Planning multi-tenant WiFi?

Deploying isolated subnets using iPSK or PPSK secures tenant devices under a unified SSID. Purple simplifies property onboarding, billing, and resident portals.

Talk to a WiFi expert