Are you experiencing slower speeds than expected after connecting to the Timus Network?
Several factors can contribute to this, but don't worry! This guide will help you troubleshoot the issue and get your connection back up to speed.
Initial Steps:
- Application Updates: Ensure you're using the latest version of the Timus Network client application. Outdated software can sometimes lead to performance issues. You can set automatic updates within the Timus Network client application by accessing your device settings within manage.timusnetworks.com.
- Conflicting Software: Uninstall any other VPN or network software running in the background. Even unused software might consume resources and affect your bandwidth.
If your client is up-to-date and there are no other programs running that could impact your connectivity. Please check the following troubleshooting steps:
- Check Maximum Transmission Unit (MTU)
- Ping Test with Varying Packet Sizes
- Identify Network Issues (Traceroute & MTR)
- Check Endpoint Configuration
- Performance Testing (Optional)
- Quality of Service (QoS) and ISP Throttling
- Firewall and Security Software
1. Identify Current MTU Setting
macOS:
-
Open Terminal.
-
List network services:
networksetup -listallnetworkservice
-
Check current MTU:
networksetup -getMTU <network_service>
Windows:
-
Open Command Prompt.
-
Check current MTU:
netsh interface ipv4 show interfaces
2. Ping with Specific Packet Sizes
macOS:
-
Open Terminal.
-
Ping with a specific packet size:
ping -D -s 1472 <gateway_public_ip>
Windows:
-
Open Command Prompt.
-
Ping with a specific packet size:
ping -f -l 1472 <gateway_public_ip>
-
Adjust Packet Size Incrementally:
- Start with 1472 bytes.
- Reduce the packet size by small increments if you encounter packet loss or errors.
- Find the largest packet size that does not result in fragmentation or packet loss.
3. Use Traceroute and MTR
Traceroute:
macOS:
-
Open Terminal.
-
Install traceroute (if not already installed):
brew install traceroute
-
Run traceroute:
traceroute <gateway_public_ip>
Windows:
-
Open Command Prompt.
-
Run tracert:
tracert <gateway_public_ip>
MTR:
macOS:
-
Open Terminal.
-
Install mtr (if not already installed):
brew install mtr
-
Run mtr:
mtr -rw <gateway_public_ip>
Windows:
- Open Command Prompt.
- Install WinMTR (if not already installed) from https://sourceforge.net/projects/winmtr/.
- Run WinMTR and enter the gateway IP to start the test.
4. Check Endpoint Configuration
ipconfig /all
macOS:
-
Open Activity Monitor.
-
Monitor CPU and memory usage to ensure they are not maxed out during the VPN connection.
-
Check network interface for errors:
ifconfig
Windows:
-
Open Task Manager.
-
Monitor CPU and memory usage to ensure they are not maxed out during the VPN connection.
-
Check network interface for errors:
ipconfig /all
5. Performance Testing
macOS and Windows:
-
Download and install iPerf3 from https://iperf.fr/.
-
Run iPerf tests to measure raw throughput with and without VPN:
iperf3 -c ash.speedtest.clouvider.net -p 5200-5209
6. Quality of Service (QoS) and ISP Throttling
macOS and Windows:
- Check network QoS settings on your router or network management interface to ensure no QoS rules are throttling VPN traffic.
- Confirm with the ISP that there is no throttling of VPN traffic.
7. Firewall and Security Software
macOS:
- Open System Preferences.
- Review firewall settings to ensure they are not limiting VPN throughput.
- Check any installed security software for settings that might affect VPN performance.
Windows:
- Open Control Panel.
- Review Windows Defender Firewall settings to ensure they are not limiting VPN throughput.
- Check any installed security software for settings that might affect VPN performance.
Additional Notes:
- If you're using macOS and don't have Homebrew installed, use the following command in Terminal: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" to install it.
If none of these steps resolve your bandwidth issue, please contact Timus Network support for further assistance at Support@timusnetworks.com
0 comments
Please sign in to leave a comment.