Skip to content

NAP Configuration

Marc Sanchis edited this page Jun 5, 2025 · 1 revision

NAP Configuration Guide

Network Access Point (NAP) configuration for wireless communication between Control Station, Vehicle, and Booster systems.

πŸ“‘ Overview

This guide covers the complete setup and configuration of MikroTik NAPs to establish wireless communication across the Hyperloop UPV network infrastructure. NAPs enable wireless connectivity between different network segments while maintaining network isolation and security.

Network Architecture

Control Station (192.168.0.0/24)
        ↕ (wireless)
    NAP Control
        ↕ (wireless)  
    NAP Vehicle ↔ Vehicle Network (192.168.1.0/24)
        ↕ (wireless)
    NAP Booster ↔ Booster Network (192.168.2.0/24)

🎯 Objectives

  • Establish wireless bridges between physically separated network segments
  • Maintain network isolation while enabling controlled communication
  • Provide redundant connectivity for critical operations
  • Enable real-time communication with minimal latency

πŸ› οΈ Hardware Requirements

Equipment Needed

  • MikroTik NAP devices (3 units minimum)
  • PoE injectors for power supply
  • Ethernet cables (Cat6 recommended)
  • Configuration computer with Ethernet adapter
  • WinBox software (Windows) or WebFig (cross-platform)

Network Specifications

  • Frequency: 5.775 GHz (configurable based on regulatory requirements)
  • Bandwidth: 20/40/80MHz channels
  • Security: WPA2 PSK encryption
  • IP Range: 192.168.0.101-103 for management

πŸ”§ Initial Setup

1. Hardware Preparation

PoE Connection Setup

  1. Connect PoE injector to power source
  2. Connect data cable from PoE injector to your configuration PC
  3. Connect PoE cable from injector to NAP device
  4. Verify NAP powers on (LED indicators should illuminate)

Network Adapter Configuration

Configure your PC's network adapter with a static IP:

  • IP Address: 192.168.88.100
  • Subnet Mask: 255.255.255.0
  • Gateway: 192.168.88.1

2. Factory Reset (If Needed)

⚠️ Warning: This will erase all existing configuration.

  1. Disconnect PoE cable to power off NAP
  2. Press and hold the RESET button (located near Ethernet port)
  3. Reconnect PoE cable while holding RESET
  4. Continue holding for ~5 seconds until LED blinks rapidly
  5. Release button and wait for device to complete reset (~60 seconds)

πŸ–₯️ WinBox Configuration

1. Connecting to NAP

  1. Download WinBox from MikroTik official site
  2. Launch WinBox and scan for devices
  3. Locate your NAP in the neighbor list (shows MAC and IP address)
  4. Connect using MAC address (more reliable than IP)
  5. Enter credentials (default: username admin, blank password)

WinBox Connection Screen

2. Initial Security Setup

πŸ”’ Immediately secure your device:

  1. Set device identity: System β†’ Identity

    • Example: NAP-Control, NAP-Vehicle, NAP-Booster
  2. Configure password: System β†’ Password

    • Use strong password (minimum 12 characters)
    • Store securely for team access

Security Configuration

πŸŒ‰ Bridge Configuration

1. Create Network Bridge

Bridges connect the Ethernet and wireless interfaces for seamless data flow.

  1. Navigate: Bridge β†’ Bridge
  2. Click: Add New (+)
  3. Configure:
    • Name: bridge1
    • Protocol: rstp (Rapid Spanning Tree)
    • Leave other settings at default
  4. Click: OK

2. Add Bridge Ports

  1. Navigate: Bridge β†’ Ports

  2. Add Ethernet Port:

    • Interface: ether1
    • Bridge: bridge1
    • Click: OK
  3. Add Wireless Port:

    • Interface: wlan1
    • Bridge: bridge1
    • Click: OK

Bridge Configuration

πŸ“‘ Wireless Configuration

1. Security Profile Setup

πŸ” Critical: All NAPs must use identical security settings.

  1. Navigate: Wireless β†’ Security Profiles
  2. Click: Add New (+)
  3. Configure:
    • Name: HyperNAP-Security
    • Mode: dynamic keys
    • Authentication Types: β˜‘οΈ WPA2 PSK
    • WPA2 Pre-Shared Key: [Your secure network key]
    • WPA2 Encryption: aes ccm
  4. Click: OK

Security Profile

2. Wireless Interface Configuration

  1. Navigate: Wireless β†’ WiFi Interfaces
  2. Enable interface: Select wlan1 β†’ Enable
  3. Double-click wlan1 to configure

For Control Station NAP (Master)

  • Mode: ap bridge
  • SSID: HyperNAP
  • Security Profile: HyperNAP-Security

For Vehicle/Booster NAPs (Clients)

  • Mode: station bridge
  • SSID: HyperNAP
  • Security Profile: HyperNAP-Security

3. Advanced Wireless Settings

Configure based on your antenna specifications:

Country: etsi 5.7-5.8 srd
Band: 5GHz-only-AC
Channel Width: 20/40/80MHz XXXX
Frequency: 5775 MHz
TX Power: Maximum allowed for region

Wireless Configuration

🌐 IP Address Configuration

1. Management IP Setup

Each NAP needs a unique management IP for remote configuration.

  1. Navigate: IP β†’ Addresses
  2. Click: Add New (+)
  3. Configure:
    • Address: 192.168.0.101/24 (Control)
    • Address: 192.168.0.102/24 (Vehicle)
    • Address: 192.168.0.103/24 (Booster)
    • Interface: bridge1
  4. Click: OK

IP Configuration

πŸ“ Note: These management IPs don't interfere with data traffic as NAPs operate at Layer 2 (bridging mode).

βœ… Verification and Testing

1. Connection Status

Check wireless connectivity:

  1. Navigate: Wireless β†’ WiFi Interfaces
  2. Verify: Station mode NAPs show "connected" status
  3. Check: Signal strength (should be > -70 dBm for optimal performance)

2. Bridge Traffic

Monitor data flow:

  1. Navigate: Interfaces
  2. Check: RX/TX counters on bridge1 interface
  3. Verify: Traffic flows between Ethernet and wireless ports

3. Network Connectivity

Test end-to-end connectivity:

# From Control Station PC (192.168.0.9)
ping 192.168.1.100  # Vehicle network device
ping 192.168.2.100  # Booster network device

πŸ”§ Advanced Configuration

1. Quality of Service (QoS)

Prioritize critical traffic:

  1. Navigate: Queues β†’ Queue Tree
  2. Create: Priority queues for control commands
  3. Configure: Bandwidth allocation rules

2. Wireless Security Enhancements

Additional security measures:

  • MAC Address Filtering: Restrict access to known devices
  • Hidden SSID: Don't broadcast network name
  • Access List: Control which devices can connect

3. Monitoring and Logging

Setup system monitoring:

  1. Navigate: System β†’ Logging
  2. Configure: Log wireless events and security attempts
  3. Setup: SNMP monitoring for network management

🚨 Troubleshooting

Common Issues

NAPs Won't Connect

Symptoms: Station mode NAPs show "searching" status

Solutions:

  1. Verify SSID matches exactly (case-sensitive)
  2. Check security settings are identical
  3. Confirm frequency and country settings
  4. Check signal strength and antenna positioning

Poor Performance

Symptoms: High latency, packet loss

Solutions:

  1. Optimize antenna positioning for line-of-sight
  2. Adjust TX power and channel width
  3. Check for interference from other 5GHz devices
  4. Update NAP firmware to latest version

Management Access Issues

Symptoms: Cannot connect to NAP via WinBox

Solutions:

  1. Try MAC address instead of IP connection
  2. Check PC network configuration
  3. Verify cables and PoE injector
  4. Perform factory reset if necessary

Performance Optimization

Signal Quality

  • Maintain line-of-sight between NAPs when possible
  • Use high-gain antennas for longer distances
  • Position away from metal structures and interference sources

Bandwidth Management

  • Configure QoS rules for mission-critical traffic
  • Monitor usage and adjust limits as needed
  • Use dedicated channels to avoid interference

πŸ“Š Monitoring and Maintenance

Regular Checks

  • Weekly: Signal strength and connection status
  • Monthly: Firmware updates and security patches
  • Quarterly: Performance analysis and optimization

Performance Metrics

  • Signal Strength: Should be > -70 dBm
  • Throughput: Monitor actual vs. theoretical speeds
  • Latency: Keep < 10ms for real-time operations
  • Packet Loss: Should be < 0.1%

πŸ”— Related Documentation


βœ… NAP Configuration Complete!

Your wireless network backbone is now ready to support Hyperloop operations. For ongoing support, refer to the Troubleshooting Network guide or contact the network team.

Clone this wiki locally