Sanitized mirror from private repository - 2026-04-19 08:15:48 UTC
This commit is contained in:
488
docs/infrastructure/comprehensive-travel-setup.md
Normal file
488
docs/infrastructure/comprehensive-travel-setup.md
Normal file
@@ -0,0 +1,488 @@
|
||||
# 🌍 Comprehensive Travel Connectivity Setup
|
||||
|
||||
**🟡 Intermediate Guide**
|
||||
|
||||
This guide combines all travel networking components into a complete mobile homelab access solution, featuring the MSI Prestige 13 AI Plus laptop, GL.iNet travel routers, remote KVM, and Tailscale mesh networking.
|
||||
|
||||
---
|
||||
|
||||
## 🎒 Complete Travel Kit
|
||||
|
||||
### **Primary Hardware Stack**
|
||||
```
|
||||
MSI Prestige 13 AI Plus (Travel Laptop)
|
||||
├── GL.iNet Slate 7 (GL-BE3600) - Primary Wi-Fi 7 Router
|
||||
├── GL.iNet Beryl AX (GL-MT3000) - Backup Wi-Fi 6 Router
|
||||
├── GL.iNet Mango (GL-MT300N-V2) - Emergency Router
|
||||
├── GL.iNet S200 - IoT Gateway (optional)
|
||||
└── GL.iNet Comet (GL-RM1) - Remote KVM
|
||||
```
|
||||
|
||||
### **Connectivity Layers**
|
||||
1. **Physical Layer**: GL.iNet routers for internet access
|
||||
2. **Security Layer**: Tailscale mesh VPN for encrypted tunnels
|
||||
3. **Application Layer**: Full homelab service access
|
||||
4. **Management Layer**: Remote KVM for emergency server access
|
||||
|
||||
---
|
||||
|
||||
## 💻 MSI Prestige 13 AI Plus - Travel Workstation
|
||||
|
||||
### **Why This Laptop for Travel?**
|
||||
- **Ultra-Portable**: 990g weight, 13.3" form factor
|
||||
- **AI Acceleration**: Intel NPU for AI workloads (47 TOPS)
|
||||
- **Efficient Performance**: Intel Arc Graphics + Core Ultra 7 258V
|
||||
- **Premium Display**: OLED 2.8K touch-enabled for creative work
|
||||
- **Wi-Fi 7**: Latest wireless standard for maximum speed
|
||||
- **All-Day Battery**: 75Wh with fast charging
|
||||
- **Tailscale IP**: 100.80.0.26 (msi.tail.vish.gg)
|
||||
|
||||
### **Travel-Optimized Configuration**
|
||||
```bash
|
||||
# Windows 11 Pro Setup
|
||||
- WSL2 for Linux development environment
|
||||
- Docker Desktop for container development
|
||||
- Tailscale client for homelab access
|
||||
- GL.iNet mobile app for router management
|
||||
- Remote desktop tools for KVM access
|
||||
|
||||
# Development Environment
|
||||
- Visual Studio Code with remote development
|
||||
- Git with SSH keys for GitLab access
|
||||
- Node.js, Python, Docker for development
|
||||
- VPN clients for secure connectivity
|
||||
```
|
||||
|
||||
### **Power Management for Travel**
|
||||
- **Performance Mode**: Full power for intensive tasks
|
||||
- **Balanced Mode**: Optimal battery life for general use
|
||||
- **Battery Saver**: Extended operation when charging unavailable
|
||||
- **Fast Charging**: Quick top-ups during layovers
|
||||
|
||||
---
|
||||
|
||||
## 🌐 GL.iNet Travel Router Strategy
|
||||
|
||||
### **Multi-Router Redundancy**
|
||||
Each router serves a specific purpose in the travel connectivity stack:
|
||||
|
||||
#### **GL-BE3600 (Primary) - Wi-Fi 7 Performance**
|
||||
```bash
|
||||
# Use Cases:
|
||||
- High-bandwidth work (video calls, large file transfers)
|
||||
- Content creation and media streaming
|
||||
- Development with rapid Docker image pulls
|
||||
- AI/ML workloads requiring fast data access
|
||||
|
||||
# Configuration:
|
||||
- Primary VPN tunnel to homelab
|
||||
- QoS prioritization for work traffic
|
||||
- Guest network for untrusted devices
|
||||
- Captive portal bypass for hotel Wi-Fi
|
||||
```
|
||||
|
||||
#### **GL-MT3000 (Backup) - Wi-Fi 6 Reliability**
|
||||
```bash
|
||||
# Use Cases:
|
||||
- Backup connectivity when primary fails
|
||||
- Secondary location setup (hotel room + lobby)
|
||||
- Load balancing for multiple devices
|
||||
- Dedicated IoT device connectivity
|
||||
|
||||
# Configuration:
|
||||
- Secondary VPN tunnel for redundancy
|
||||
- Different SSID for easy identification
|
||||
- Optimized for battery operation
|
||||
- Simplified configuration for quick setup
|
||||
```
|
||||
|
||||
#### **GL-MT300N-V2 (Emergency) - Basic Connectivity**
|
||||
```bash
|
||||
# Use Cases:
|
||||
- Emergency internet access
|
||||
- Ultra-portable backup (credit card size)
|
||||
- Legacy device connectivity
|
||||
- Power-constrained environments
|
||||
|
||||
# Configuration:
|
||||
- Basic VPN tunnel
|
||||
- Minimal power consumption
|
||||
- Simple WPA2 security
|
||||
- Emergency contact access only
|
||||
```
|
||||
|
||||
#### **GL-S200 (IoT) - Smart Device Management**
|
||||
```bash
|
||||
# Use Cases:
|
||||
- Travel IoT device management
|
||||
- Smart home setup in extended stays
|
||||
- Development and testing of IoT protocols
|
||||
- Portable smart device hub
|
||||
|
||||
# Configuration:
|
||||
- Thread Border Router
|
||||
- Zigbee coordinator
|
||||
- Matter over Thread/Wi-Fi
|
||||
- Isolated IoT network
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🔐 Tailscale Integration Strategy
|
||||
|
||||
### **Split-Brain DNS Configuration**
|
||||
Based on your production setup (`tail.vish.gg`):
|
||||
|
||||
```bash
|
||||
# Nameserver Hierarchy:
|
||||
1. MagicDNS (100.100.100.100) - Tailscale devices
|
||||
2. vish.local (192.168.0.250) - Local network when home
|
||||
3. Homelab DNS (100.103.48.78, 100.72.55.21) - Custom resolution
|
||||
4. Public DNS - Fallback for internet queries
|
||||
|
||||
# Search Domains:
|
||||
- tail.vish.gg (automatic Tailscale resolution)
|
||||
- vish.local (local network resolution)
|
||||
```
|
||||
|
||||
### **Service Access Patterns**
|
||||
Based on current Tailscale network (tail.vish.gg):
|
||||
|
||||
```bash
|
||||
# Active Infrastructure Hosts:
|
||||
atlantis.tail.vish.gg # 100.83.230.112 - Primary NAS & Media
|
||||
calypso.tail.vish.gg # 100.103.48.78 - Development & Caching
|
||||
setillo.tail.vish.gg # 100.125.0.20 - Monitoring & Network
|
||||
homelab.tail.vish.gg # 100.67.40.126 - Experimentation VM
|
||||
pi-5.tail.vish.gg # 100.77.151.40 - Edge Computing
|
||||
pve.tail.vish.gg # 100.87.12.28 - Proxmox Virtualization
|
||||
truenas-scale.tail.vish.gg # 100.75.252.64 - Secondary Storage
|
||||
shinku-ryuu.tail.vish.gg # 100.98.93.15 - Primary Workstation
|
||||
vish-concord-nuc.tail.vish.gg # 100.72.55.21 - Family Network Bridge
|
||||
vmi2076105.tail.vish.gg # 100.99.156.20 - Chicago Remote VM
|
||||
|
||||
# Travel & Mobile Devices:
|
||||
msi.tail.vish.gg # 100.80.0.26 - MSI Prestige 13 AI Plus
|
||||
iphone16.tail.vish.gg # 100.79.252.108 - iPhone 16 Pro Max
|
||||
ipad-pro-12-9-6th-gen-wificellular.tail.vish.gg # 100.68.71.48
|
||||
gl-be3600.tail.vish.gg # 100.105.59.123 - Primary Travel Router
|
||||
gl-mt3000.tail.vish.gg # 100.126.243.15 - Backup Travel Router
|
||||
glkvm.tail.vish.gg # 100.64.137.1 - Remote KVM
|
||||
|
||||
# Service Examples:
|
||||
# Development: Access GitLab via atlantis.tail.vish.gg:3000
|
||||
# Media: Plex via atlantis.tail.vish.gg:32400
|
||||
# Monitoring: Grafana via atlantis.tail.vish.gg:7099
|
||||
# Passwords: Vaultwarden via atlantis.tail.vish.gg:8080
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🛠️ Remote Management with GL-RM1 KVM
|
||||
|
||||
### **Emergency Server Access**
|
||||
The GL-RM1 provides out-of-band management for critical situations:
|
||||
|
||||
```bash
|
||||
# Physical Setup:
|
||||
Server → GL-RM1 KVM → Network → Tailscale → Travel Laptop
|
||||
|
||||
# Access Methods:
|
||||
1. Web Interface: https://gl-rm1.tail.vish.gg
|
||||
2. Direct IP: https://100.xxx.xxx.xxx (Tailscale IP)
|
||||
3. Local Access: https://192.168.8.100 (when on same network)
|
||||
```
|
||||
|
||||
### **Use Case Scenarios**
|
||||
- **BIOS Access**: Configure hardware settings remotely
|
||||
- **OS Installation**: Install/reinstall operating systems
|
||||
- **Network Troubleshooting**: Fix connectivity issues
|
||||
- **Emergency Recovery**: Access systems when SSH fails
|
||||
- **Hardware Diagnostics**: Check system health and status
|
||||
|
||||
---
|
||||
|
||||
## 📱 Mobile Device Integration
|
||||
|
||||
### **Seamless Multi-Device Experience**
|
||||
```bash
|
||||
# Device Ecosystem:
|
||||
MSI Prestige 13 AI Plus (Primary workstation)
|
||||
├── iPhone 16 Pro Max (Communication, monitoring)
|
||||
├── iPad Pro 12.9" 6th Gen (Creative work, presentations)
|
||||
├── GL.iNet Routers (Network infrastructure)
|
||||
└── GL-RM1 KVM (Emergency management)
|
||||
|
||||
# Tailscale Mesh:
|
||||
- All devices connected to same Tailscale network
|
||||
- Consistent service access across all platforms
|
||||
- Automatic failover between network connections
|
||||
- Synchronized settings and configurations
|
||||
```
|
||||
|
||||
### **Cross-Platform Workflows**
|
||||
- **Development**: Code on laptop, test on mobile devices
|
||||
- **Media**: Stream from homelab to any device
|
||||
- **Productivity**: Access documents from any platform
|
||||
- **Monitoring**: Check homelab status from mobile devices
|
||||
- **Security**: Vaultwarden access from all devices
|
||||
|
||||
---
|
||||
|
||||
## 🗺️ Travel Scenarios & Configurations
|
||||
|
||||
### **Business Travel (1-3 days)**
|
||||
```bash
|
||||
# Minimal Kit:
|
||||
- MSI Prestige 13 AI Plus
|
||||
- GL-BE3600 (primary router)
|
||||
- GL-MT300N-V2 (emergency backup)
|
||||
- Essential cables and chargers
|
||||
|
||||
# Configuration:
|
||||
- Single high-performance router
|
||||
- Full homelab access via Tailscale
|
||||
- Emergency backup for critical connectivity
|
||||
- Optimized for hotel/conference environments
|
||||
```
|
||||
|
||||
### **Extended Travel (1-4 weeks)**
|
||||
```bash
|
||||
# Complete Kit:
|
||||
- MSI Prestige 13 AI Plus
|
||||
- GL-BE3600 + GL-MT3000 (redundant routers)
|
||||
- GL-S200 (IoT gateway for smart devices)
|
||||
- GL-RM1 KVM (remote server management)
|
||||
- Full cable kit and backup power
|
||||
|
||||
# Configuration:
|
||||
- Redundant connectivity options
|
||||
- IoT device management capability
|
||||
- Remote server troubleshooting
|
||||
- Extended stay optimizations
|
||||
```
|
||||
|
||||
### **Digital Nomad (Months)**
|
||||
```bash
|
||||
# Full Infrastructure:
|
||||
- Complete GL.iNet router collection
|
||||
- Multiple backup power solutions
|
||||
- Comprehensive cable and adapter kit
|
||||
- Local SIM cards and cellular backup
|
||||
- Portable monitor and peripherals
|
||||
|
||||
# Configuration:
|
||||
- Location-specific optimizations
|
||||
- Local ISP integration
|
||||
- Cultural and regulatory compliance
|
||||
- Long-term reliability focus
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🔧 Setup & Configuration Workflows
|
||||
|
||||
### **Pre-Travel Checklist**
|
||||
```bash
|
||||
# Hardware Preparation:
|
||||
□ All devices charged and firmware updated
|
||||
□ Tailscale clients installed and authenticated
|
||||
□ VPN configurations tested and verified
|
||||
□ Backup power solutions packed
|
||||
□ Essential cables and adapters included
|
||||
|
||||
# Software Preparation:
|
||||
□ Development environments synchronized
|
||||
□ Password manager updated and accessible
|
||||
□ Important documents backed up locally
|
||||
□ Emergency contact information accessible
|
||||
□ Homelab monitoring dashboards bookmarked
|
||||
|
||||
# Network Preparation:
|
||||
□ Router configurations backed up
|
||||
□ Emergency access credentials secured
|
||||
□ Failover procedures documented
|
||||
□ Local emergency contacts identified
|
||||
□ ISP and connectivity research completed
|
||||
```
|
||||
|
||||
### **On-Location Setup Procedure**
|
||||
```bash
|
||||
# Step 1: Establish Basic Connectivity
|
||||
1. Connect GL-BE3600 to local internet
|
||||
2. Verify internet access and speed
|
||||
3. Test Tailscale connection to homelab
|
||||
4. Confirm DNS resolution working
|
||||
|
||||
# Step 2: Secure Network Setup
|
||||
1. Configure guest network for untrusted devices
|
||||
2. Set up QoS rules for work traffic
|
||||
3. Enable firewall and security features
|
||||
4. Test VPN tunnel stability
|
||||
|
||||
# Step 3: Device Integration
|
||||
1. Connect laptop to secure network
|
||||
2. Verify all homelab services accessible
|
||||
3. Test backup router connectivity
|
||||
4. Configure IoT devices if needed
|
||||
|
||||
# Step 4: Monitoring & Maintenance
|
||||
1. Set up network monitoring
|
||||
2. Configure automatic failover
|
||||
3. Test emergency procedures
|
||||
4. Document local network details
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📊 Performance Optimization
|
||||
|
||||
### **Network Performance Tuning**
|
||||
```bash
|
||||
# Router Optimization:
|
||||
- Channel selection for minimal interference
|
||||
- QoS configuration for work traffic priority
|
||||
- Bandwidth allocation for critical services
|
||||
- Latency optimization for real-time applications
|
||||
|
||||
# Tailscale Optimization:
|
||||
- Exit node selection for optimal routing
|
||||
- Subnet routing for efficient access
|
||||
- DNS configuration for fast resolution
|
||||
- Connection monitoring and alerting
|
||||
```
|
||||
|
||||
### **Power Management**
|
||||
```bash
|
||||
# Laptop Power Optimization:
|
||||
- Performance profiles for different scenarios
|
||||
- Battery conservation during travel
|
||||
- Fast charging strategies
|
||||
- Power bank compatibility
|
||||
|
||||
# Router Power Management:
|
||||
- Battery operation for portable routers
|
||||
- Power consumption monitoring
|
||||
- Charging schedules and rotation
|
||||
- Emergency power procedures
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🛡️ Security Best Practices
|
||||
|
||||
### **Multi-Layer Security**
|
||||
```bash
|
||||
# Network Security:
|
||||
- WPA3 encryption on all networks
|
||||
- Guest network isolation
|
||||
- Firewall rules and access control
|
||||
- Regular security updates
|
||||
|
||||
# VPN Security:
|
||||
- Strong encryption (WireGuard/OpenVPN)
|
||||
- Kill switch functionality
|
||||
- DNS leak protection
|
||||
- Connection monitoring
|
||||
|
||||
# Device Security:
|
||||
- Full disk encryption
|
||||
- Strong authentication (2FA)
|
||||
- Regular security updates
|
||||
- Endpoint protection
|
||||
```
|
||||
|
||||
### **Emergency Security Procedures**
|
||||
```bash
|
||||
# Compromise Response:
|
||||
1. Disconnect from network immediately
|
||||
2. Switch to cellular/backup connectivity
|
||||
3. Change critical passwords
|
||||
4. Notify homelab of potential breach
|
||||
5. Implement emergency access procedures
|
||||
|
||||
# Recovery Procedures:
|
||||
1. Factory reset compromised devices
|
||||
2. Restore from secure backups
|
||||
3. Re-establish secure connections
|
||||
4. Verify system integrity
|
||||
5. Document incident for future prevention
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📋 Troubleshooting Guide
|
||||
|
||||
### **Common Issues & Solutions**
|
||||
```bash
|
||||
# Connectivity Problems:
|
||||
- Router not connecting to internet
|
||||
- Tailscale tunnel not establishing
|
||||
- DNS resolution failures
|
||||
- Slow network performance
|
||||
|
||||
# Solutions:
|
||||
- Check physical connections and power
|
||||
- Verify ISP settings and credentials
|
||||
- Test with different routers/configurations
|
||||
- Contact local ISP support if needed
|
||||
```
|
||||
|
||||
### **Emergency Procedures**
|
||||
```bash
|
||||
# Complete Network Failure:
|
||||
1. Switch to cellular hotspot
|
||||
2. Use emergency router (GL-MT300N-V2)
|
||||
3. Access homelab via Tailscale mobile app
|
||||
4. Use GL-RM1 KVM for server management
|
||||
5. Contact local technical support
|
||||
|
||||
# Hardware Failure:
|
||||
1. Identify failed component
|
||||
2. Switch to backup hardware
|
||||
3. Restore configuration from backup
|
||||
4. Test all critical functions
|
||||
5. Arrange replacement if needed
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Advanced Use Cases
|
||||
|
||||
### **Content Creation on the Road**
|
||||
- **4K Video Editing**: High-performance laptop with OLED display
|
||||
- **Large File Transfers**: Wi-Fi 7 for rapid upload/download
|
||||
- **Cloud Storage Sync**: Seamless access to homelab storage
|
||||
- **Collaboration**: Real-time sharing via homelab services
|
||||
|
||||
### **Remote Development**
|
||||
- **Full Dev Environment**: WSL2 + Docker + VS Code
|
||||
- **Git Operations**: Direct GitLab access via Tailscale
|
||||
- **Container Development**: Local Docker with homelab registry
|
||||
- **Testing & Deployment**: Remote access to staging environments
|
||||
|
||||
### **AI/ML Workloads**
|
||||
- **Local Processing**: Intel NPU for edge AI tasks
|
||||
- **Dataset Access**: High-speed download from homelab
|
||||
- **Model Training**: Hybrid local/remote processing
|
||||
- **Result Sharing**: Upload models back to homelab
|
||||
|
||||
---
|
||||
|
||||
## 🔗 Integration Points
|
||||
|
||||
### **Homelab Service Integration**
|
||||
- **[Tailscale Setup](tailscale-setup-guide.md)**: Core VPN configuration
|
||||
- **[GL.iNet Devices](glinet-travel-networking.md)**: Detailed router setup
|
||||
- **[Mobile Devices](mobile-device-setup.md)**: Phone and tablet integration
|
||||
- **[Laptop Setup](laptop-travel-setup.md)**: Detailed laptop configuration
|
||||
|
||||
### **Infrastructure Components**
|
||||
- **[Network Architecture](networking.md)**: Overall network design
|
||||
- **[Host Overview](hosts.md)**: All system specifications
|
||||
- **[Security Model](../admin/security.md)**: Security implementation
|
||||
- **[Monitoring Setup](../admin/monitoring.md)**: System monitoring
|
||||
|
||||
---
|
||||
|
||||
*This comprehensive travel setup provides enterprise-level connectivity, security, and functionality while maintaining the portability and flexibility needed for modern mobile work and digital nomad lifestyles.*
|
||||
Reference in New Issue
Block a user