-
Notifications
You must be signed in to change notification settings - Fork 0
NAP Configuration
Network Access Point (NAP) configuration for wireless communication between Control Station, Vehicle, and Booster systems.
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.
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)
- 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
- 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)
- 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
- Connect PoE injector to power source
- Connect data cable from PoE injector to your configuration PC
- Connect PoE cable from injector to NAP device
- Verify NAP powers on (LED indicators should illuminate)
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
- Disconnect PoE cable to power off NAP
- Press and hold the RESET button (located near Ethernet port)
- Reconnect PoE cable while holding RESET
- Continue holding for ~5 seconds until LED blinks rapidly
- Release button and wait for device to complete reset (~60 seconds)
- Download WinBox from MikroTik official site
- Launch WinBox and scan for devices
- Locate your NAP in the neighbor list (shows MAC and IP address)
- Connect using MAC address (more reliable than IP)
-
Enter credentials (default: username
admin
, blank password)
π Immediately secure your device:
-
Set device identity: System β Identity
- Example:
NAP-Control
,NAP-Vehicle
,NAP-Booster
- Example:
-
Configure password: System β Password
- Use strong password (minimum 12 characters)
- Store securely for team access
Bridges connect the Ethernet and wireless interfaces for seamless data flow.
- Navigate: Bridge β Bridge
- Click: Add New (+)
-
Configure:
-
Name:
bridge1
-
Protocol:
rstp
(Rapid Spanning Tree) - Leave other settings at default
-
Name:
- Click: OK
-
Navigate: Bridge β Ports
-
Add Ethernet Port:
-
Interface:
ether1
-
Bridge:
bridge1
- Click: OK
-
Interface:
-
Add Wireless Port:
-
Interface:
wlan1
-
Bridge:
bridge1
- Click: OK
-
Interface:
π Critical: All NAPs must use identical security settings.
- Navigate: Wireless β Security Profiles
- Click: Add New (+)
-
Configure:
-
Name:
HyperNAP-Security
-
Mode:
dynamic keys
- Authentication Types: βοΈ WPA2 PSK
-
WPA2 Pre-Shared Key:
[Your secure network key]
-
WPA2 Encryption:
aes ccm
-
Name:
- Click: OK
- Navigate: Wireless β WiFi Interfaces
-
Enable interface: Select
wlan1
β Enable -
Double-click
wlan1
to configure
-
Mode:
ap bridge
-
SSID:
HyperNAP
-
Security Profile:
HyperNAP-Security
-
Mode:
station bridge
-
SSID:
HyperNAP
-
Security Profile:
HyperNAP-Security
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
Each NAP needs a unique management IP for remote configuration.
- Navigate: IP β Addresses
- Click: Add New (+)
-
Configure:
-
Address:
192.168.0.101/24
(Control) -
Address:
192.168.0.102/24
(Vehicle) -
Address:
192.168.0.103/24
(Booster) -
Interface:
bridge1
-
Address:
- Click: OK
π Note: These management IPs don't interfere with data traffic as NAPs operate at Layer 2 (bridging mode).
Check wireless connectivity:
- Navigate: Wireless β WiFi Interfaces
- Verify: Station mode NAPs show "connected" status
- Check: Signal strength (should be > -70 dBm for optimal performance)
Monitor data flow:
- Navigate: Interfaces
-
Check: RX/TX counters on
bridge1
interface - Verify: Traffic flows between Ethernet and wireless ports
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
Prioritize critical traffic:
- Navigate: Queues β Queue Tree
- Create: Priority queues for control commands
- Configure: Bandwidth allocation rules
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
Setup system monitoring:
- Navigate: System β Logging
- Configure: Log wireless events and security attempts
- Setup: SNMP monitoring for network management
Symptoms: Station mode NAPs show "searching" status
Solutions:
- Verify SSID matches exactly (case-sensitive)
- Check security settings are identical
- Confirm frequency and country settings
- Check signal strength and antenna positioning
Symptoms: High latency, packet loss
Solutions:
- Optimize antenna positioning for line-of-sight
- Adjust TX power and channel width
- Check for interference from other 5GHz devices
- Update NAP firmware to latest version
Symptoms: Cannot connect to NAP via WinBox
Solutions:
- Try MAC address instead of IP connection
- Check PC network configuration
- Verify cables and PoE injector
- Perform factory reset if necessary
- Maintain line-of-sight between NAPs when possible
- Use high-gain antennas for longer distances
- Position away from metal structures and interference sources
- Configure QoS rules for mission-critical traffic
- Monitor usage and adjust limits as needed
- Use dedicated channels to avoid interference
- Weekly: Signal strength and connection status
- Monthly: Firmware updates and security patches
- Quarterly: Performance analysis and optimization
- 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%
- Network Overview - Complete network architecture
- Raspberry Pi Router - Inter-network routing
- Switch Configuration - Network switch setup
- Troubleshooting Network - Network diagnostics
β 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.