### Quick Start Docker Deployment (Host Networking) Source: https://openpacketloss.com/selfhosted-server Use this command for a quick deployment on Linux systems. Host networking offers the best performance and simplifies WebRTC setup. ```bash docker run -d \ --name openpacketloss \ --network host \ --restart unless-stopped \ openpacketloss/openpacketloss-server:latest ``` -------------------------------- ### Docker Compose Deployment (Host Networking - Linux) Source: https://openpacketloss.com/selfhosted-server Recommended for structured deployments on Linux. This configuration uses host networking for optimal performance and simplified WebRTC setup. ```yaml services: openpacketloss: image: openpacketloss/openpacketloss-server:latest container_name: openpacketloss network_mode: host restart: unless-stopped logging: driver: "json-file" options: max-size: "10m" max-file: "3" ``` -------------------------------- ### Managed Switch CLI Interface Command Source: https://openpacketloss.com/how-to-fix-packet-loss Example command to check interface statistics on a managed switch. Look for input errors, CRC, or runts to identify physical layer issues. ```cli # Example for a managed switch CLI show interfaces GigabitEthernet0/1 ``` -------------------------------- ### Diagnose Network Hop Packet Loss (Linux/macOS/Windows) Source: https://openpacketloss.com/voip-packet-loss Use MTR on Linux/macOS or pathping on Windows to identify which network hop is dropping packets. Run this during a bad call for at least two minutes. Replace the example IP with your ISP's gateway or a media server IP. ```bash # Linux / macOS -- run for 2+ minutes during a bad call mtr --report --report-cycles 120 8.8.8.8 ``` ```bash # Windows -- use WinMTR (GUI) or pathping pathping -n -q 100 8.8.8.8 ``` -------------------------------- ### Traceroute to League of Legends Server Source: https://openpacketloss.com/gaming-packet-loss Execute a traceroute command to diagnose network paths to League of Legends regional servers. Replace `prod.euw1.lol.pvp.net` with the target hostname for your region. ```command-line tracert prod.euw1.lol.pvp.net ``` -------------------------------- ### Enable Dota 2 Net Graph Overlay Source: https://openpacketloss.com/gaming-packet-loss Run this command in the Dota 2 console to display real-time network statistics, including packet loss and choke. Use `net_graphpos` to reposition the overlay. ```console net_graph 1 ``` ```console net_graphpos 1 ``` -------------------------------- ### Compare Network Latency (Linux/macOS) Source: https://openpacketloss.com/how-to-fix-packet-loss This command sequence helps diagnose bufferbloat by comparing ping latency under idle and loaded network conditions. It saves results to text files for analysis. ```bash # Run while the network is quiet ping -i 0.2 -c 100 8.8.8.8 > ping_idle.txt # Start a large download (e.g., a Linux ISO or game update) and immediately run: ping -i 0.2 -c 100 8.8.8.8 > ping_loaded.txt ``` -------------------------------- ### Docker Compose Deployment (Bridge Mode - Universal) Source: https://openpacketloss.com/selfhosted-server Use this configuration for universal compatibility across Windows, macOS, and Linux when host networking is not preferred. It explicitly maps ports for HTTP, STUN, and WebRTC media. ```yaml services: openpacketloss: image: openpacketloss/openpacketloss-server:latest container_name: openpacketloss restart: unless-stopped ports: # HTTP and API mapping - "9000:80" - "4000:4000/udp" # WebRTC ICE UDP port range - "40000-40050:40000-40050/udp" environment: # --- Networking (required) --- - STUN_PORT=4000 - NAT_1TO1_IP=192.168.1.12 # --- WebRTC ICE Port Range --- - ICE_PORT_MIN=40000 - ICE_PORT_MAX=40050 logging: driver: "json-file" options: max-size: "10m" max-file: "3" ``` -------------------------------- ### Test UDP Packet Loss with OpenPacketLoss.com Source: https://openpacketloss.com/gaming-packet-loss Run this test to measure real-time UDP packet loss using WebRTC. Zero percent loss indicates a clean local connection and route to the test server. ```bash pathping -n 8.8.8.8 ``` -------------------------------- ### Monitor Docker Logs Source: https://openpacketloss.com/selfhosted-server Command to stream logs from the running OpenPacketLoss container. Useful for debugging and monitoring server activity. ```bash docker logs -f openpacketloss ``` -------------------------------- ### ISP Support Message Template Source: https://openpacketloss.com/how-to-fix-packet-loss Use this template to effectively communicate packet loss issues to your ISP, including troubleshooting steps taken and observed patterns. ```text Subject: Packet Loss Investigation Required for Account [ACCOUNT NUMBER] I am experiencing [X]% packet loss that began approximately [DATE]. Troubleshooting completed: - Baseline Test: [X]% loss measured at openpacketloss.com - MTR Pattern: Loss begins at hop [X] and persists to destination - Isolation: Problem persists when connected directly to the modem via Ethernet - Timing: [Constant loss / Peak hour loss occurring between X and Y] - Signal Check: [Downstream SNR is X dB / Power is Y dBmV] Please open a line fault investigation and check for physical layer errors on the local node or signal instability at my ONT/modem. ``` -------------------------------- ### Flush DNS Cache Source: https://openpacketloss.com/gaming-packet-loss Use this command to clear your local DNS cache. Stale DNS entries can lead to incorrect server routing. ```batch ipconfig /flushdns ``` -------------------------------- ### Run Microsoft Teams Network Assessment Tool Source: https://openpacketloss.com/voip-packet-loss Execute the Teams Network Assessment Tool from affected machines to check connectivity and quality. The quality check specifically measures packet loss, jitter, and round-trip time against Microsoft's thresholds. ```bash NetworkAssessmentTool.exe /connectivitycheck ``` ```bash NetworkAssessmentTool.exe /qualitycheck ``` -------------------------------- ### Generate MTR Report for Packet Loss Analysis Source: https://openpacketloss.com/how-to-fix-packet-loss Use the MTR command to generate a report that helps identify the origin of packet loss. Run this command on Linux/macOS or via WSL on Windows. Ensure you run tests during active issues and quiet times for comparison. ```bash # Linux / macOS mtr --report --report-cycles 60 8.8.8.8 # Windows (winmtr or via WSL) mtr -r -c 60 8.8.8.8 ``` -------------------------------- ### Configure WireGuard MTU Source: https://openpacketloss.com/how-to-fix-packet-loss If your VPN uses WireGuard, set the MTU explicitly in the interface configuration to match the largest packet size found during MTU testing to prevent fragmentation. ```ini [Interface] MTU = 1380 ``` -------------------------------- ### Force Dota 2 Relay Cluster Source: https://openpacketloss.com/gaming-packet-loss Use this command in the Dota 2 console to manually switch to a specific Steam Datagram Relay cluster. Replace `[code]` with the desired location code. To revert, use an empty string. ```console sdr SDRClient_ForceRelayCluster [code] ``` ```console sdr SDRClient_ForceRelayCluster "" ``` -------------------------------- ### Check OS-Level Network Statistics Source: https://openpacketloss.com/what-is-packet-loss Examine operating system-specific network counters to identify packet loss and related errors. These commands provide insights into dropped packets and retransmissions at the network interface level. ```bash ip -s link show eth0 netstat -s | grep -i "packet loss\|retransmit\|failed" ``` ```bash netstat -I en0 ``` ```powershell netstat -e Get-NetAdapterStatistics ``` -------------------------------- ### Check Network Device Errors (Linux) Source: https://openpacketloss.com/how-to-fix-packet-loss Use this command to check for hardware-level packet drops on Linux network interfaces. Useful for diagnosing issues with Ethernet adapters. ```bash dmesg | grep -E "eth|eno|enp|NETDEV|TX timeout|dropped" ``` -------------------------------- ### Analyze Per-Hop Packet Loss with MTR Source: https://openpacketloss.com/what-is-packet-loss MTR combines ping and traceroute to visualize packet loss at each hop along the network path. High loss on a hop that persists to the destination indicates a real issue, while loss on intermediate hops might be due to router prioritization. ```bash mtr --report --report-cycles 100 8.8.8.8 ``` -------------------------------- ### Test Network Connectivity with Ping Source: https://openpacketloss.com/what-is-packet-loss Use ping to send ICMP echo requests and identify timeouts or lost responses, indicating packet loss. Measure the loss percentage by dividing lost packets by sent packets and multiplying by 100. ```bash # Linux / macOS ping -c 100 8.8.8.8 # Windows ping -n 100 8.8.8.8 ``` -------------------------------- ### Increase Linux Kernel Network Buffers Source: https://openpacketloss.com/how-to-fix-packet-loss Tune the operating system's network stack by increasing the maximum receive and send buffer sizes. This allows the kernel to handle higher packet rates, reducing drops under heavy load. ```bash # Increase socket receive buffer sysctl -w net.core.rmem_max=134217728 # Increase socket send buffer sysctl -w net.core.wmem_max=134217728 ``` -------------------------------- ### Set DSCP Value for Teams Audio via PowerShell Source: https://openpacketloss.com/voip-packet-loss Use this PowerShell command to mark Microsoft Teams audio packets with a DSCP value of 46 for Quality of Service (QoS) prioritization. This applies to both TCP and UDP protocols. ```powershell New-NetQosPolicy -Name "Teams-Audio" -AppPathNameMatchCondition "ms-teams.exe" -IPProtocolMatchCondition Both -DSCPAction 46 ``` -------------------------------- ### Test UDP/WebRTC Packet Loss with iPerf3 Source: https://openpacketloss.com/what-is-packet-loss Use iPerf3 with UDP mode to specifically test packet loss for real-time applications like video calls and WebRTC. The output directly reports lost datagrams and the loss percentage. ```bash # Server iperf3 -s # Client iperf3 -c -u -b 10M ``` -------------------------------- ### Diagnose MTU Issues with Ping Source: https://openpacketloss.com/how-to-fix-packet-loss Use ping with specific flags to find the largest packet size that can pass through your network without fragmentation. Decrease the size until the ping succeeds. This helps identify MTU mismatches, especially with VPNs. ```bash # Linux / macOS (decrease size from 1400 until successful) ping -M do -s 1400 8.8.8.8 ``` ```bash # Windows (decrease size from 1400 until successful) ping -f -l 1400 8.8.8.8 ``` -------------------------------- ### Adjust NIC Ring Buffer Size Source: https://openpacketloss.com/how-to-fix-packet-loss Modify the Network Interface Card's (NIC) ring buffer sizes for both receive (RX) and transmit (TX). Increasing these buffers can improve throughput and reduce packet drops on high-load systems. ```bash # View current NIC ring buffer settings ethtool -g eth0 # Set RX and TX ring buffers to the maximum supported value ethtool -G eth0 rx 4096 tx 4096 ``` -------------------------------- ### Analyze Upstream Routing with MTR Source: https://openpacketloss.com/how-to-fix-packet-loss Use MTR to test connectivity and identify packet loss across different network paths. This helps distinguish between transit network faults and destination-specific routing issues. ```cli # Test to Google Public DNS mtr --report --report-cycles 60 8.8.8.8 ``` ```cli # Test to Cloudflare DNS mtr --report --report-cycles 60 1.1.1.1 ``` ```cli # Test to your specific affected destination mtr --report --report-cycles 60 [your game server or affected destination IP] ``` -------------------------------- ### Check Cisco IOS Interface Statistics for Errors Source: https://openpacketloss.com/voip-packet-loss Use this command on Cisco IOS devices to check interface statistics for errors like CRC, runts, and giants, which can indicate duplex mismatches or other physical layer issues. ```text # Cisco IOS show interfaces GigabitEthernet0/1 # Look for: input errors, CRC, runts, giants ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.