Introduction

EyePee-O-Matic is a comprehensive IP subnet calculator and network planning tool designed specifically for live audio engineers who need to calculate and manage IP schemes for live show networks. Whether you're setting up network segments for audio consoles, stage boxes, wireless systems, or other networked equipment, EyePee-O-Matic provides the tools you need to plan, validate, and optimize your network addressing.

What is EyePee-O-Matic?

EyePee-O-Matic is an iOS app that simplifies complex IP subnetting calculations. It helps you:

• Calculate subnet information from IP addresses and CIDR notation
• Convert between different IP address formats
• Plan network schemes for multiple devices
• Validate IP addresses before deployment
• Learn subnetting concepts through interactive tutorials

Target Audience

This app is designed for live audio engineers who work with networked audio equipment and need to:

• Configure IP addresses for mixing consoles, stage boxes, and wireless systems
• Plan network segments for touring shows
• Validate IP configurations before show deployment
• Understand subnetting concepts without deep networking expertise

Quick Start Guide

Getting Started

1. Launch the App: Open EyePee-O-Matic on your iOS device
2. Navigate the Tabs: The app has four main tabs at the bottom:
   • Calculator: Main subnet calculator
   • Converter: IP address format converter
   • Tools: Collection of specialized network tools
   • Learn: Educational content and practice

Your First Calculation

1. Open the Calculator tab
2. Enter an IP address (e.g., 192.168.1.0)
3. Enter a prefix length (e.g., 24 or /24)
4. View the results showing:
   • Network address
   • Broadcast address
   • Usable IP range
   • Total addresses
   • Usable hosts
   • Subnet mask and wildcard mask

Common Use Case: Setting Up a Show Network

Scenario: You need to configure IP addresses for:

• Audio console: 10 devices
• Stage boxes: 50 devices
• Wireless systems: 20 devices
• Control computers: 5 devices

Solution:

1. Use the Network Planner tool (Tools → Planning → Network Planner)
2. Enter a parent network (e.g., 10.0.0.0/16)
3. Add requirements for each device group
4. The planner calculates optimal subnet allocations
5. Export the plan for reference during setup

Calculator Tab

The main subnet calculator provides comprehensive subnet information and detailed explanations.

How to Use

1. Enter IP Address: Type the IP address in dotted-decimal notation (e.g., 192.168.1.0)
2. Enter Prefix Length: Enter the CIDR prefix (e.g., 24 or /24)
3. View Results: The calculator displays:
   • Network address and broadcast address
   • First and last usable IP addresses
   • Subnet mask (dotted-decimal and binary)
   • Wildcard mask
   • Total addresses and usable hosts
   • Block information and classification

Settings

• Treat /31 as Point-to-Point: When enabled, /31 networks allow both addresses to be used (useful for point-to-point links)
• Show Binary Breakdown: Display binary representations of addresses and masks

Features

• Step-by-Step Explanation: Tap "Show Explanation" to see how the calculation works
• Share Results: Export calculation results as text for documentation
• Bit Breakdown: Visual representation of how the IP address is divided into network and host portions

Example

Input: 10.249.77.4/14

Output:

• Network: 10.248.0.0
• Broadcast: 10.251.255.255
• Usable Range: 10.248.0.1 - 10.251.255.254
• Total Addresses: 262,144
• Usable Hosts: 262,142
• Subnet Mask: 255.252.0.0

Converter Tab

Convert IP addresses between different formats: dotted-decimal, binary, hexadecimal, and decimal.

Supported Formats

1. Dotted Decimal (e.g., 192.168.1.1)
   • Standard IP address notation
   • Most commonly used format
2. Binary (e.g., 11000000.10101000.00000001.00000001)
   • 32-bit binary representation
   • Useful for understanding subnet masks
3. Hexadecimal (e.g., C0.A8.01.01)
   • Base-16 representation
   • Sometimes used in network configuration
4. Decimal (e.g., 3232235777)
   • Single decimal number
   • Used in some programming contexts

How to Use

1. Select the input format using the segmented control
2. Enter the IP address in the selected format
3. View all format conversions automatically
4. Copy any format to clipboard by tapping the copy icon

Example

Input (Dotted Decimal): 192.168.1.1

Output:

• Binary: 11000000.10101000.00000001.00000001
• Hexadecimal: C0.A8.01.01
• Decimal: 3232235777

Tools Tab

The Tools tab contains specialized network calculation and analysis tools organized into categories.

Basic Tools

IP Validator

Validate and analyze IP addresses. Supports multiple IPs (one per line).

Features:

• Validates IP address format
• Classifies addresses (private, public, loopback, multicast, etc.)
• Shows multiple representations (binary, hex, decimal)
• Identifies special addresses (RFC 1918 private, loopback, etc.)

Use Case: Before deploying a show network, validate all IP addresses to ensure they're correctly formatted and appropriate for your use case.

Example Input:

192.168.1.1
10.0.0.1
127.0.0.1
224.0.0.1

Output: Each IP is validated and classified with detailed information.

Wildcard Calculator

Convert between subnet masks, prefix lengths, and wildcard masks.

Input Types:

• Subnet Mask (e.g., 255.255.255.0)
• Prefix Length (e.g., 24 or /24)
• Wildcard Mask (e.g., 0.0.0.255)

Use Cases:

• Access Control Lists (ACLs): Use wildcard masks to match address ranges
• Routing Protocols: OSPF, EIGRP use wildcard masks for network statements
• Firewall Rules: Match IP ranges using wildcard notation

Example:

• Input: Prefix Length /24
• Output:
  • Subnet Mask: 255.255.255.0
  • Wildcard Mask: 0.0.0.255
  • Binary representations included

Advanced Tools

Range to Subnet

Find the smallest subnet that contains a given IP address range.

How to Use:

1. Enter the start IP address (e.g., 192.168.1.10)
2. Enter the end IP address (e.g., 192.168.1.50)
3. View the calculated subnet that contains the range

Use Case: You have a range of IPs already assigned and need to determine what subnet they belong to.

Example:

• Start IP: 192.168.1.10
• End IP: 192.168.1.50
• Result: 192.168.1.0/24 (or smaller if possible)

Subnet Divider

Divide a parent subnet into equal smaller subnets.

Requirements:

• Number of subnets must be a power of 2 (2, 4, 8, 16, 32, etc.)
• Parent subnet must be large enough

How to Use:

1. Enter the parent network IP (e.g., 192.168.0.0)
2. Enter the parent prefix (e.g., 16 or /16)
3. Enter the number of subnets (must be power of 2)
4. View the divided subnets with their network addresses and ranges

Use Case: You have a /16 network and need to divide it into 8 equal /19 subnets for different show components.

Example:

• Parent: 192.168.0.0/16
• Number of Subnets: 8
• Result: 8 subnets of /19 each:
  • 192.168.0.0/19
  • 192.168.32.0/19
  • 192.168.64.0/19
  • ... (and 5 more)

Subnet Comparison

Compare two subnets side-by-side to see their relationship and properties.

Features:

• Side-by-side comparison of subnet properties
• Overlap detection
• Size comparison
• Visual indicators for relationships

Use Case: Verify that two subnets don't overlap before assigning them to different device groups.

Example:

• Subnet 1: 192.168.1.0/24
• Subnet 2: 192.168.2.0/24
• Result: No overlap, both are /24, same size

Network Tools

Overlap Detector

Check if two subnets overlap and identify the overlapping range.

Overlap Types:

• None: Subnets don't overlap
• Partial: Subnets partially overlap
• Subnet 1 Contains Subnet 2: First subnet completely contains the second
• Subnet 2 Contains Subnet 1: Second subnet completely contains the first
• Identical: Both subnets are the same

Use Case: Critical for network planning - ensure no IP address conflicts between device groups.

Example:

• Subnet 1: 192.168.1.0/24
• Subnet 2: 192.168.1.128/25
• Result: Subnet 1 Contains Subnet 2 - Overlapping range: 192.168.1.128 - 192.168.1.255

Host Requirements

Calculate the optimal subnet size for a given number of hosts.

How to Use:

1. Enter the number of hosts needed
2. View the recommended prefix length
3. See efficiency metrics (wasted addresses, efficiency percentage)

Use Case: You know you need 100 devices on a subnet - what prefix length should you use?

Example:

• Hosts Needed: 100
• Recommended: /25 (128 total, 126 usable)
• Efficiency: 79.4% (26 wasted addresses)

Tips:

• Higher efficiency means less wasted addresses
• The calculator finds the smallest subnet that fits your requirements
• Consider future growth when selecting subnet sizes

VLSM Calculator

Variable Length Subnet Masking - divide a parent network into subnets of different sizes.

How to Use:

1. Enter the parent network (IP and prefix)
2. Add subnet requirements (name and number of hosts for each)
3. Tap "Calculate VLSM"
4. View optimized subnet allocations

Use Case: Perfect for show networks where different device groups need different numbers of IPs:

• Audio console: 10 hosts → /28
• Stage boxes: 50 hosts → /26
• Wireless: 20 hosts → /27
• Control: 5 hosts → /29

Example:

• Parent: 10.0.0.0/16
• Requirements:
  • Console: 10 hosts
  • Stage: 50 hosts
  • Wireless: 20 hosts
• Result: Optimized subnet allocations with minimal waste

Features:

• Automatically sorts requirements by size (largest first)
• Calculates optimal prefix lengths for each requirement
• Shows efficiency metrics
• Displays usable IP ranges for each subnet

Supernetting

Aggregate multiple contiguous subnets into a single larger subnet (route aggregation).

How to Use:

1. Add subnets to aggregate (e.g., 192.168.1.0/24, 192.168.2.0/24)
2. Tap "Calculate Supernet"
3. View the aggregated supernet

Requirements:

• Subnets must be contiguous
• Subnets must be the same size
• Subnets must align on proper boundaries

Use Case: Simplify routing tables by aggregating multiple subnets into a single route.

Example:

• Subnets: 192.168.1.0/24, 192.168.2.0/24, 192.168.3.0/24
• Supernet: 192.168.0.0/22

Planning

Network Planner

A step-by-step wizard for planning complete network schemes.

Step 1: Parent Network

• Enter the parent network that will contain all your subnets
• Optionally use "Suggest Network" to auto-calculate based on requirements

Step 2: Requirements

• Add subnet requirements (name and number of hosts)
• Add multiple requirements for different device groups
• Reorder or remove requirements as needed

Step 3: Review Plan

• View the calculated network plan
• See subnet allocations, IP ranges, and efficiency metrics
• Verify all requirements are met

Step 4: Export

• Export the plan in multiple formats:
  • Text: Human-readable format
  • CSV: For spreadsheet import
  • JSON: For programmatic use

Use Case: Complete network planning for a touring show:

1. Define parent network (e.g., 10.0.0.0/16)
2. Add requirements:
   • Console Network: 20 hosts
   • Stage A: 50 hosts
   • Stage B: 50 hosts
   • Wireless: 30 hosts
   • Control: 10 hosts
3. Review the optimized plan
4. Export and share with the team

Tips:

• Start with a larger parent network than you think you need
• Add a few extra hosts to each requirement for future growth
• Export the plan before show deployment for reference

Learn Tab

Educational content to help you understand subnetting concepts.

Basics

Interactive tutorial covering fundamental concepts:

• What are bits?
• Reading binary numbers
• IP addresses in binary
• Subnet masks as bits
• Prefix length = network bits
• Putting it all together

How to Use: Swipe through pages to learn subnetting fundamentals with visual examples.

Glossary

Comprehensive glossary of networking terms with:

• Short definitions
• Detailed explanations
• Why it matters
• Examples
• Related terms

Terms Include:

• IPv4 Address, CIDR Notation, Subnet, Subnet Mask
• Wildcard Mask, Prefix Length, Network Address, Broadcast Address
• Bits, Binary, Octets, Bitwise Operations

Audio Industry Terms (New in v1.2):

• DANTE - Including self-assigned IP best practices
• MILAN - Media networking protocol
• AVB - Audio Video Bridging
• TSN - Time-Sensitive Networking
• PTP - Precision Time Protocol
• gPTP - Generalized Precision Time Protocol
• Media Clock - Synchronization for audio streams
• CRF - Clock Reference
• Link-Local (169.254.x.x) - Self-assigned addressing (Dante's recommended default mode)
• QoS - Quality of Service
• VLAN - Virtual LAN for network segmentation

How to Use: Browse or search for terms. Tap any term to see detailed information.

Guide

Quick reference guide covering:

• What is subnetting?
• Understanding CIDR notation
• Subnet masks
• Usable host addresses
• Special cases (/31, /32)

How to Use: Swipe through guide pages for quick reference on key concepts.

Reference

Common subnet reference table showing:

• Prefix length
• Total addresses
• Usable hosts
• Common use cases
• Example networks

Features:

• Searchable by prefix, hosts, or use case
• Copy example networks to clipboard
• Quick reference for common subnet sizes

Common Subnets:

• /24: 254 hosts - Small office/home office
• /16: 65,534 hosts - Large organization
• /8: 16,777,214 hosts - Class A network
• And many more...

Practice

Interactive practice questions to test your subnetting knowledge.

Features:

• Multiple difficulty levels
• Score tracking
• Immediate feedback
• Explanations for correct answers

Question Types:

• Calculate network address
• Find broadcast address
• Determine usable range
• Calculate subnet mask
• And more...

How to Use:

1. Select difficulty level
2. Answer the question
3. Check your answer
4. Review the explanation
5. Move to the next question

Tips:

• Start with easier difficulty levels
• Review explanations even for correct answers
• Practice regularly to improve speed and accuracy

Common Use Cases for Live Audio Engineers

Use Case 1: Setting Up Network Segments for Show Components

Scenario: You're setting up a live show with multiple networked components:

• Audio console: 15 devices
• Stage boxes (Stage A): 40 devices
• Stage boxes (Stage B): 40 devices
• Wireless systems: 25 devices
• Control computers: 8 devices

Solution:

1. Open Network Planner (Tools → Planning → Network Planner)
2. Step 1 - Parent Network:
   • Enter: 10.0.0.0/16
   • This gives you 65,534 usable addresses (plenty of room)
3. Step 2 - Add Requirements:
   • Console Network: 15 hosts
   • Stage A: 40 hosts
   • Stage B: 40 hosts
   • Wireless: 25 hosts
   • Control: 8 hosts
4. Step 3 - Review Plan:
   • Console: 10.0.0.0/28 (16 addresses, 14 usable)
   • Stage A: 10.0.1.0/26 (64 addresses, 62 usable)
   • Stage B: 10.0.1.64/26 (64 addresses, 62 usable)
   • Wireless: 10.0.2.0/27 (32 addresses, 30 usable)
   • Control: 10.0.2.32/29 (8 addresses, 6 usable)
5. Step 4 - Export:
   • Export as text or CSV
   • Share with your team
   • Use during show setup

Use Case 2: Validating IP Addresses Before Deployment

Scenario: You have a list of IP addresses from a previous show and want to verify they're valid before reusing them.

Solution:

1. Open IP Validator (Tools → Basic Tools → IP Validator)
2. Enter IPs (one per line):

   192.168.1.10
   192.168.1.20
   192.168.1.30
   10.0.0.5
   172.16.0.1

3. Review Results:
   • Each IP is validated
   • Classification shown (private, public, etc.)
   • Multiple representations available
   • Special address types identified
4. Verify:
   • All IPs are valid
   • Appropriate for your use case (private vs. public)
   • No conflicts or special addresses that shouldn't be used

Use Case 3: Calculating Subnets for Multiple Devices

Scenario: You need to quickly calculate subnet information for a /24 network you're using.

Solution:

1. Open Calculator tab
2. Enter:
   • IP: 192.168.1.0
   • Prefix: 24
3. View Results:
   • Network: 192.168.1.0
   • Broadcast: 192.168.1.255
   • Usable Range: 192.168.1.1 - 192.168.1.254
   • Total: 256 addresses
   • Usable: 254 hosts
4. Share (optional):
   • Tap the share button
   • Export results for documentation

Use Case 4: Planning Network Schemes for Touring Shows

Scenario: You're planning IP schemes for a touring show that will use the same network setup at multiple venues.

Solution:

1. Use Network Planner to create a standardized plan
2. Create a Template:
   • Use consistent parent network (e.g., 10.0.0.0/16)
   • Define standard requirements for each show component
   • Export the plan as a template
3. For Each Venue:
   • Load the template
   • Adjust if needed for venue-specific requirements
   • Export and share with local crew
4. Benefits:
   • Consistent IP schemes across venues
   • Easier troubleshooting
   • Faster setup time

Use Case 5: Converting Between IP Formats

Scenario: You need to convert an IP address to binary for documentation or to understand subnet masking.

Solution:

1. Open Converter tab
2. Enter IP in dotted-decimal: 192.168.1.1
3. View All Formats:
   • Binary: 11000000.10101000.00000001.00000001
   • Hexadecimal: C0.A8.01.01
   • Decimal: 3232235777
4. Copy any format to clipboard for use elsewhere

Use Case 6: Finding the Subnet for a Range of IPs

Scenario: You have devices with IPs from 192.168.1.10 to 192.168.1.50 and need to know what subnet they're on.

Solution:

1. Open Range to Subnet (Tools → Advanced Tools → Range to Subnet)
2. Enter:
   • Start IP: 192.168.1.10
   • End IP: 192.168.1.50
3. Result: 192.168.1.0/24
   • This is the smallest subnet containing your range
   • Shows network, broadcast, and usable range

Troubleshooting & FAQ

Common Input Errors

"Invalid IP address format"

Problem: The IP address you entered is not in the correct format.

Solution:

• Use dotted-decimal notation: 192.168.1.1
• Each octet must be between 0-255
• Use exactly 4 octets separated by dots

Examples:

• ✅ Correct: 192.168.1.1
• ❌ Wrong: 192.168.1 (missing octet)
• ❌ Wrong: 192.168.1.256 (octet > 255)
• ❌ Wrong: 192.168.01.1 (leading zeros are OK but not standard)

"Invalid prefix length"

Problem: The prefix length is out of range or incorrectly formatted.

Solution:

• Prefix must be between 0-32
• You can enter with or without the slash: 24 or /24
• Both formats are accepted

Examples:

• ✅ Correct: 24 or /24
• ❌ Wrong: 33 (out of range)
• ❌ Wrong: 24.5 (must be integer)

"Requirements cannot fit in parent network"

Problem: In VLSM Calculator or Network Planner, your requirements are too large for the parent network.

Solution:

• Use a larger parent network (smaller prefix number)
• Reduce the number of hosts in your requirements
• Check that requirements don't exceed available addresses

Example:

• Parent: 192.168.1.0/24 (254 usable hosts)
• Requirement: 300 hosts → Error
• Solution: Use 192.168.0.0/16 (65,534 usable hosts)

"Number of subnets must be a power of 2"

Problem: In Subnet Divider, you entered a number that's not a power of 2.

Solution:

• Use: 2, 4, 8, 16, 32, 64, 128, 256, etc.
• These are the only values that allow equal division

Examples:

• ✅ Correct: 2, 4, 8, 16, 32
• ❌ Wrong: 3, 5, 6, 7, 10, 12

Understanding Calculation Results

Why are there 2 fewer usable hosts than total addresses?

Answer: The network address (first) and broadcast address (last) are reserved and cannot be assigned to hosts.

Example: A /24 network has:

• 256 total addresses
• 254 usable hosts
• 1 network address (192.168.1.0)
• 1 broadcast address (192.168.1.255)

What does "efficiency" mean?

Answer: Efficiency shows how well a subnet size matches your requirements. Higher efficiency means fewer wasted addresses.

Example:

• You need 100 hosts
• /25 gives you 126 usable (79.4% efficiency)
• /24 gives you 254 usable (39.4% efficiency)
• /25 is more efficient for 100 hosts

What is a /31 network?

Answer: A /31 network has only 2 addresses. With "Treat /31 as Point-to-Point" enabled, both addresses can be used for point-to-point links (no network or broadcast address).

Use Case: Perfect for router-to-router connections where you only need 2 IPs.

What is a /32 network?

Answer: A /32 network represents a single host with no subnetting. There's no usable range - just the single IP address.

Use Case: Sometimes used in routing tables to represent a single host route.

Export and Sharing Features

How do I share calculation results?

Answer:

1. In the Calculator tab, after calculating, tap the "Share" button in the results section
2. Choose how to share (Messages, Mail, Notes, etc.)
3. Results are formatted as text for easy reading

What formats can I export network plans in?

Answer: Network Planner supports three export formats:

• Text: Human-readable format for documentation
• CSV: For importing into spreadsheets
• JSON: For programmatic use or integration with other tools

Can I copy IP addresses to clipboard?

Answer: Yes! In the Converter tab, each format has a copy button. In Common Subnets reference, you can copy example networks. Many result views also support text selection for copying.

Tips for Efficient Workflow

Tip 1: Use Network Planner for Complex Setups

For shows with multiple device groups, use Network Planner instead of calculating each subnet individually. It's faster and ensures no overlaps.

Tip 2: Validate Before Deployment

Always use IP Validator to check your IP addresses before show deployment. Catch errors early!

Tip 3: Export Your Plans

Export network plans and keep them for reference. You can reuse them for similar shows or venues.

Tip 4: Learn the Common Subnets

Familiarize yourself with common subnet sizes (/24, /26, /28, etc.) from the Reference section. This speeds up planning.

Tip 5: Use Practice Mode

Regular practice improves your subnetting skills and speed. Use the Practice section in Learn tab.

Tip 6: Check for Overlaps

Before finalizing a network plan, use Overlap Detector to verify no subnets overlap. This prevents IP conflicts.

Tip 7: Plan for Growth

When calculating subnet requirements, add 10-20% extra hosts for future growth. It's easier than reconfiguring later.

Reference Information

Common Subnet Sizes

Quick reference for common subnet configurations:

• /32: 1 address, 0 usable - Single host route
• /31: 2 addresses, 2 usable* - Point-to-point links
• /30: 4 addresses, 2 usable - Smallest usable subnet
• /29: 8 addresses, 6 usable - Very small networks
• /28: 16 addresses, 14 usable - Small device groups
• /27: 32 addresses, 30 usable - Medium device groups
• /26: 64 addresses, 62 usable - Large device groups
• /25: 128 addresses, 126 usable - Small office networks
• /24: 256 addresses, 254 usable - Standard LAN
• /23: 512 addresses, 510 usable - Small organization
• /22: 1,024 addresses, 1,022 usable - Medium organization
• /21: 2,048 addresses, 2,046 usable - Large organization
• /20: 4,096 addresses, 4,094 usable - Very large organization
• /16: 65,536 addresses, 65,534 usable - Class B network
• /8: 16,777,216 addresses, 16,777,214 usable - Class A network

*With "Treat /31 as Point-to-Point" enabled

IP Address Classifications

Private Addresses (RFC 1918)

• 10.0.0.0/8 (10.0.0.0 - 10.255.255.255)
• 172.16.0.0/12 (172.16.0.0 - 172.31.255.255)
• 192.168.0.0/16 (192.168.0.0 - 192.168.255.255)

Use: Internal networks, not routable on the internet

Special Addresses

• Loopback: 127.0.0.0/8 - Used for localhost testing
• Link-Local (APIPA): 169.254.0.0/16 (169.254.0.0 - 169.254.255.255)
  • Self-assigned addresses; DANTE's recommended default mode
  • Not a failure state for audio networks - this is intentional!
  • Devices automatically assign themselves addresses in this range when no DHCP server is available
• Multicast: 224.0.0.0/4 - Used for group communication
• Documentation (TEST-NET): 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24 - Reserved for documentation and examples

Networked Audio Protocols (New in v1.2)

DANTE

DANTE (Digital Audio Network Through Ethernet) is a popular audio-over-IP protocol used in professional audio systems.

Key Points:

• Self-Assigned IP Mode: DANTE devices can use link-local addressing (169.254.x.x) when no DHCP server is present
• This is not an error condition - it's the recommended default mode for many setups
• DANTE Controller software manages device discovery and configuration
• Supports unicast and multicast audio streams
• Requires proper network configuration for latency and bandwidth management

IP Configuration Best Practices:

• Use static IP addresses for critical devices in production environments
• Plan subnet sizes to accommodate all DANTE devices plus control traffic
• Consider VLAN separation for audio networks vs. control networks
• Validate IP addresses before deployment using EyePee-O-Matic's IP Validator

MILAN

MILAN (Media Integration for Local Area Networks) is an open standard for professional audio networking based on AVB/TSN.

Key Points:

• Built on IEEE 802.1 Audio Video Bridging (AVB) and Time-Sensitive Networking (TSN) standards
• Requires network switches that support AVB/TSN protocols
• Provides deterministic latency and synchronization
• Uses PTP (Precision Time Protocol) for clock synchronization
• Requires proper VLAN configuration for stream isolation

Network Planning Considerations:

• MILAN networks require AVB-capable switches
• Plan VLANs to separate audio streams from control traffic
• Ensure proper QoS configuration on switches
• Calculate bandwidth requirements for all audio channels

VLAN (Virtual LAN)

VLANs allow you to logically segment a physical network into multiple virtual networks.

Key Points:

• Separate broadcast domains on the same physical infrastructure
• Improve security by isolating network segments
• Reduce broadcast traffic and improve performance
• Essential for MILAN/AVB networks to isolate audio streams
• Useful for separating audio networks from control networks

VLAN Planning for Audio Networks:

• Audio VLAN: Dedicated VLAN for audio streams (DANTE, MILAN, etc.)
• Control VLAN: Separate VLAN for device control and management
• Guest/Public VLAN: Isolated network for non-critical devices
• Plan IP subnets for each VLAN using Network Planner
• Ensure no IP address overlap between VLANs
• Use EyePee-O-Matic's Overlap Detector to verify VLAN subnets don't conflict

Example VLAN Configuration:

• VLAN 10 (Audio): 10.0.10.0/24 - DANTE/MILAN devices
• VLAN 20 (Control): 10.0.20.0/24 - Console control, wireless management
• VLAN 30 (Guest): 10.0.30.0/24 - Public WiFi, non-critical devices

Best Practices:

• Document VLAN assignments and IP schemes
• Use consistent VLAN numbering across shows
• Plan for VLAN trunking if using multiple switches
• Validate all VLAN IP ranges before deployment

Terminology Quick Reference

• CIDR: Classless Inter-Domain Routing - modern subnetting method
• Prefix Length: Number of bits used for network portion (e.g., /24)
• Subnet Mask: 32-bit number identifying network vs. host bits
• Wildcard Mask: Inverse of subnet mask, used in ACLs
• Network Address: First address in a subnet (identifies the network)
• Broadcast Address: Last address in a subnet (used for broadcast messages)
• Usable Range: IP addresses that can be assigned to hosts
• VLSM: Variable Length Subnet Masking - using different subnet sizes
• Supernetting: Aggregating multiple subnets into one larger subnet

Best Practices

• Always validate IP addresses before deployment
• Check for overlaps when planning multiple subnets
• Export and save your network plans
• Plan for future growth when sizing subnets
• Use private IP ranges (RFC 1918) for internal networks
• Standardize IP schemes across shows for easier troubleshooting
• Document your network plans and keep them for reference
• Calculate subnets during prep, not during setup
• For DANTE networks: Understand that link-local (169.254.x.x) addresses are normal, not errors
• For MILAN/AVB networks: Plan VLANs and ensure switch compatibility
• For VLAN configurations: Use Network Planner to ensure no IP overlap between VLANs

Back to Support | Return to Home

This documentation is for EyePee-O-Matic version 1.2 and later.