Can I access computers on my local network? – Speedify Knowledge Base
Mục Lục
Can I access computers on my local network?
Many devices such as Chromecasts, Apple TV, the Roku remote app, streaming audio devices, Network Attached Storage (NAS), and home servers need to talk directly to your phone on the local Wi-Fi network or LAN.
Luckily, Speedify is smart about this and automatically detects when you are accessing devices on the same local network. It lets apps on your device connect directly without going through Speedify. Any traffic on the same local subnet will go around Speedify and out the appropriate network connection.
Note that means that data sent and received from local devices will not show up on the Speedify graphs and will not affect your daily usage limits or the amount of Speedify data you have for the month.
Complex Networks with Multiple Subnets
For most users, this means that you will have no problem accessing other devices on your local network. However, users with complex local networks consisting of multiple subnets will not be able to access devices on other subnets.
For example, let’s say you have a local network that with two subnets: 192.168.1.X and 192.168.55.X. Your computer running Speedify is connected to the 192.168.1.X subnet.
When Speedify is not connected, any traffic that destined for an IP address outside the 192.168.1.X subnet, including Internet traffic or traffic to the 192.168.55.X subnet, will go to the default gateway at 192.168.1.1. The gateway will know whether to route the traffic to the other subnet or out to the Internet.
When Speedify is connected, Speedify becomes the default route to the Internet. Traffic destined for the local subnet 192.168.1.X will still get sent directly to that network, outside the VPN. Any other traffic, including Internet traffic or traffic for the other subnet 192.168.55.X, will go to the default route, which is now Speedify. The Speedify server has no way of routing traffic to your local 192.168.55.X network, so the traffic gets lost.
To get around this issue, you can add customs routes on desktop / laptop machines (Windows, Mac, Linux) to tell your computer to send traffic for the 192.168.55.X to the 192.168.1.1 gateway, instead of going over Speedify. The example commands below are based on these example subnets. You will need to adjust the arguments for your particular scenario.
The 192.168.55.0 address is the subnet you are trying to reach.
The 192.168.1.1 address is the gateway for the subnet you are connected to.
Windows:
Open an Administrator command prompt by right clicking on the command prompt from the start menu and choosing “Run as Administrator”
Run the following command:
route add 192.168.55.0 mask 255.255.255.0 192.168.1.1
If this command works, you can run again with adding the -p argument to make it persistent across reboots:
route add 192.168.55.0 mask 255.255.255.0 192.168.1.1 -p
Mac:
Open a terminal and run the following command:
sudo route add -net 192.168.55.0/24 192.168.1.1
Linux:
Open a terminal and run the following command:
sudo route add -net 192.168.55.0 netmask 255.255.255.0 gw 192.168.1.1