🚒 IBR1900 Fire Engine Setup Guide

Complete configuration for Cradlepoint IBR1900 with GPS, cellular, and Starlink backup

← Back to Kerchunk Networks • Setup Guides • IBR1900 Configuration

📋 Quick Navigation

📦 Equipment Overview
Component Model/Service Purpose
Primary Router Cradlepoint IBR1900 Main fire engine network hub
Cellular Service eSIM (Telnyx recommended) Primary internet connection
Backup Internet Starlink Satellite Automatic failover connection
GPS Service 1 Tablet Command Real-time tactical positioning
GPS Service 2 Versaterm AVL CAD system integration
🔥 Fire Department Specific: This configuration ensures 24/7 connectivity for emergency operations with automatic failover and dual GPS tracking for dispatch and tactical coordination.
🚀 Initial Router Setup
Step 1: Router Access & Security
# Initial connection URL: https://192.168.0.1 Default Login: admin / [last 8 digits of MAC address] # If login fails: Factory reset (hold button 45s, wait 1min)

Secure Admin Password:

  • Local Router: System → Administration → Router Security
  • NetCloud: Settings → Device Settings → [Select Router] → Security
  • Set strong password: FireDept2025! (or similar)
Step 2: NetCloud Manager Registration
⚠️ Security: Only whitelist specific IP addresses for SSH access. Never allow unrestricted SSH access to fire department equipment.

Recommended Whitelist:

  • Fire HQ network: 10.0.0.5
  • IT management subnet: 192.168.1.0/24
  • Emergency management IPs only

Test SSH Access:

ssh admin@[ROUTER_CELLULAR_IP] # Should connect from whitelisted IPs only
Step 3: Firewall Configuration

Path: Security → Zone Firewall

Required Outbound Rules:

  • Allow UDP 12121 to avl.tabletcommand.com (GPS)
  • Allow UDP 12345 to avl.smc911.org (GPS)
  • Allow UDP 53 to DNS servers
  • Allow ICMP for health checks

Security Rules:

  • Block unnecessary inbound traffic
  • Allow SSH only from whitelisted IPs
  • Log all security events
Step 4: SNMP Monitoring

Path: System → SNMP Configuration

  • Enable SNMPv3 (secure version)
  • Community String: [SECURE_COMMUNITY_STRING]
  • Access: Read-only for monitoring tools
  • Allowed Hosts: Fire department monitoring systems only
🧪 Testing & Validation
Step 1: Cellular Connection Testing
  • Verify private IP assignment (not CGNAT)
  • Test internet connectivity: ping 8.8.8.8
  • Check signal strength and data speeds
  • Verify data usage monitoring
    • # Verification commands ping 8.8.8.8 nslookup google.com speedtest (via web interface)
    Step 2: Starlink Failover Testing
    📋 Test Procedure: Document failover timing for emergency response planning.
    1. Disable cellular interface temporarily
    2. Confirm automatic switch to Starlink
    3. Verify GPS continues reporting during failover
    4. Test internet connectivity via Starlink
    5. Re-enable cellular and confirm failback
    6. Document total failover time

    Expected Results:

    • Failover time: <30 seconds
    • GPS services continue uninterrupted
    • Automatic failback when cellular restored
    Step 3: WiFi Performance Testing
  • Connect devices to both Public-fc and Public-fc5G
  • Test signal strength at various truck locations
  • Verify band steering works (devices prefer 5GHz)
  • Test maximum client connections (up to 20)
  • Check channel interference with WiFi analyzer
    • Step 4: GPS Service Testing
    ⏰ Testing Time: GPS services may have specific active hours. Tablet Command example: 9:00 AM - 5:00 PM PDT.
  • Verify GPS lock with 4+ satellites
  • Confirm Tablet Command server connection
  • Verify Versaterm server connection
  • Check GPS packet transmission
  • Test position accuracy vs. known location
  • Confirm Unit ID 3311 transmission

    • Verification Commands:

    # Local router verification show location clients show location statistics show gps status
    Step 5: Security Testing
  • Test SSH access from whitelisted IP
  • Verify SSH blocked from non-whitelisted IP
  • Check firewall rules are active
  • Verify security logging is working
  • Test SNMP access restrictions
    • 🚨 Troubleshooting Guide
    GPS Services Not Reporting

    Diagnostic Steps:

    1. Check GPS Status: Status → Location → GPS Status
      • Satellites: Should show 4+ satellites
      • Fix Quality: Should be "3D Fix"
    2. Test Server Connectivity:
      ping avl.tabletcommand.com ping avl.smc911.org
    3. Check Client Status: Location → GPS Clients → [CLIENT] → Status
      • Last Transmission: Should be recent
      • Packets Sent: Should be incrementing
    4. Verify Firewall Rules:
      • Allow UDP 12121 to avl.tabletcommand.com
      • Allow UDP 12345 to avl.smc911.org

    Solutions:

    • Restart GPS client: restart location-client [CLIENT_NAME]
    • Check antenna connections
    • Verify server addresses haven't changed
    • Contact dispatch center to confirm reception
    WAN Failover Not Working

    Diagnostic Steps:

    1. Verify Interface Status: Status → WAN → Interfaces
      • Both cellular and Starlink should show "Connected"
    2. Test Failover Triggers:
      • Manually disconnect primary connection
      • Monitor logs for failover events
      • Time the switchover process
    3. Check Health Monitoring: Network → WAN → Failover → Health Checks
      • Ping targets should respond
      • Adjust thresholds if needed

    Solutions:

    • Reduce failover detection time
    • Add multiple ping targets (8.8.8.8, 1.1.1.1)
    • Check physical connections
    • Update interface priorities
    WiFi Performance Issues

    Common Issues & Solutions:

    • Slow 5GHz Performance:
      • Check for channel interference
      • Adjust power levels
      • Verify band steering configuration
    • Connection Drops:
      • Check client limits (max 20)
      • Verify power supply stability
      • Update device drivers
    • Poor Range:
      • Check antenna connections
      • Adjust antenna positioning
      • Consider external antennas for fire truck mounting
    Emergency Procedures
    🚨 Critical System Failure: If primary communications fail during emergency operations.

    Emergency Recovery Steps:

    1. Immediate Actions:
      • Switch to radio backup communications
      • Document system failure time
      • Contact IT support via alternate method
    2. Quick Diagnostics:
      • Check power connections
      • Verify antenna connections
      • Test with known good cable
    3. Recovery Options:
      • Router reboot: System → Actions → Reboot
      • Factory reset (last resort): Hold reset button 45s
      • Backup router deployment if available

    Emergency Contacts:

    • IT Support: [EMERGENCY_IT_NUMBER]
    • Cradlepoint Support: 1-855-813-3385
    • Carrier Support: [CARRIER_EMERGENCY_NUMBER]
    ✅ Configuration Complete! Your IBR1900 is now configured for fire department operations with redundant connectivity and GPS tracking.

    Next Steps:

    • Add to Kerchunk Networks documentation
    • Schedule regular maintenance and updates
    • Train fire department personnel on basic troubleshooting
    • Set up monitoring alerts via SharePoint ticketing system

    ← Back to Kerchunk Networks | GPS Configuration Guide →

    alert-warning"> ⚠️ Critical: Register with NetCloud Manager BEFORE deployment for remote management capabilities.
    1. Go to NetCloud Manager
    2. Dashboard → Add Device → Manual Registration
    3. Enter Serial Number and MAC Address (found on router label)
    4. Device Name: "Fire Engine [NUMBER] - IBR1900"
    5. Location: Your fire station address
    Step 3: Configuration Backup

    Always backup before making changes:

    📱 Cellular eSIM Configuration
    Step 1: eSIM Activation

    NetCloud Manager Path:

    Settings → Connectivity → Modems → [Select Router] → SIM Management

    Local Router Path:

    Networking → Modems → SIM/APN Settings
    1. Select eSIM option
    2. Download profile via NetCloud Manager
    3. Choose carrier (Telnyx recommended for fire departments)
    4. Set APN: data00.telnyx (or carrier-specific)
    Step 2: Verify Private IP Assignment
    🚨 Critical: Ensure you get a PRIVATE IP address, not CGNAT. Fire departments need direct connectivity for emergency operations.

    Verification Paths:

    • NetCloud: Status → Devices → [Router] → Connection Status
    • Local: Status → Internet → Connection Manager

    Expected Result: IP like 10.0.0.123 (private range)

    If CGNAT: Contact carrier immediately to request static/private IP

    Step 3: LAN Network Configuration

    Path: Networking → Local Networks → Local IP Networks

    Setting Value Purpose
    Router IP 192.168.10.1 Fire engine network gateway
    Subnet Mask 255.255.255.0 /24 network (254 devices)
    DHCP Range 192.168.10.10 - 192.168.10.100 Automatic device assignment
    Reserved IPs 192.168.10.2-9 Static assignments for critical equipment
    🛰️ Starlink Backup Configuration
    Step 1: Physical Connection
    1. Connect Starlink dish to WAN2 Ethernet port on IBR1900
    2. Set Starlink dish to IP Passthrough mode via Starlink app
    3. Verify connection via Starlink app shows "Connected"
    📍 Mounting: Ensure Starlink dish has clear sky view for optimal satellite connectivity during emergency operations.
    Step 2: WAN2 Interface Configuration

    Path: Networking → WAN → Interfaces

    • Set WAN2 as Ethernet interface
    • Configuration: DHCP Client
    • Priority: 2 (backup to cellular)
    • Enable interface: ✅
    Step 3: Failover Configuration

    Path: Networking → WAN → Connection Manager

    Setting Value Purpose
    Primary Interface Cellular (WAN1) Main internet connection
    Secondary Interface Starlink (WAN2) Automatic backup
    Health Check ping 8.8.8.8 Connection monitoring
    Failover Time 30 seconds Emergency response acceptable
    Auto Failback Enabled Return to cellular when restored
    📶 WiFi Configuration
    Step 1: Dual-Band WiFi Setup

    Path: Networking → WiFi → Wireless Settings

    • Enable Dual-Band Concurrent
    • 2.4GHz SSID: Public-fc
    • 5GHz SSID: Public-fc5G
    • Region: United States
    • Channel Selection: SmartSelect (automatic)
    Step 2: Advanced WiFi Settings

    Path: Networking → WiFi → Advanced Settings

    • Band Steering: Enable (automatic 5GHz preference)
    • Alternative: Use separate SSIDs with manual 5GHz preference
    • Max Clients: 20 (fire department equipment limit)
    Step 3: Fire Engine Optimization

    Path: Networking → WiFi → Client Management

    • Priority Devices: Fire tablets, emergency equipment → 5GHz band
    • QoS: Enable for emergency traffic
    • Device Priority: Critical fire department equipment first
    ✅ Optimization: 5GHz provides better performance for data-heavy applications like mapping and video streaming during emergency operations.
    🛰️ GPS Services Configuration
    Step 1: Tablet Command GPS Client

    NetCloud Path:

    Settings → Location Services → [Select Router] → GPS Clients → Add Client

    Local Router Path:

    System → Administration → GPS → Location Services → GPS Clients
    Setting Value
    Client Name tablet_command
    Enabled ✅ Yes
    Server avl.tabletcommand.com
    Port 12121
    Protocol UDP
    Update Interval 3 seconds
    Distance Interval 0 meters
    Stationary Time 300 seconds
    Language NMEA

    NMEA Settings:

    • ✅ Include ID
    • Custom ID: system_id
    • ✅ GGA (position data)
    • ✅ RMC (recommended minimum)
    • ✅ VTG (velocity data)
    Step 2: Versaterm AVL GPS Client

    Same paths as above, different configuration:

    Setting Value
    Client Name versaterm_avl
    Enabled ✅ Yes
    Server avl.smc911.org
    Port 12345
    Update Interval 15 seconds
    Distance Interval 50 meters

    NMEA Settings:

    • ✅ Prepend ID
    • Custom String: 3311 (Unit ID)
    • ✅ RMC (only RMC needed)
    • ❌ GGA
    • ❌ VTG
    📡 Unit ID 3311: This identifies your fire engine in the dispatch system. Verify with your communications center.
    Step 3: GPS Verification

    NetCloud Verification:

    • Status → Location → [Router] → GPS Status
    • Status → Location → [Router] → Last Known Position

    Local Router Verification:

    • Status → Location → GPS Clients
    • Status → Location → Position Data
  • GPS shows 4+ satellites
  • Fix quality shows "3D Fix"
  • Both clients show "Connected"
  • Packets being sent to both servers
  • Position accuracy within 5 meters
    • 🔐 Security & SSH Access
    Step 1: SSH Configuration

    Enable SSH Server:

    • System → Administration → Local Management
    • ✅ Enable SSH Server

    Enable Remote SSH:

    • System → Administration → Remote Admin
    • ✅ Allow Remote SSH Access
    Step 2: SSH Access Restriction

    Path: Security → Zone Firewall → Remote Access Restriction