When F-Secure FREEDOME is turned on, it may not be possible to access a device (for example NAS boxes, network printers, smart network appliances) in your local network with its host name. However, it is possible to access the device with the IP address despite having FREEDOME turned on.
To access devices that are connected to your local network with FREEDOME turned on, the host names must be translated to IP addresses first so that it is understood by the networked computer. This is normally done by a DNS server.
Turning on FREEDOME will result in FREEDOME handling the DNS queries with its own DNS server. This is by design to prevent DNS information leaking outside the VPN tunnel.
If there are devices in the local or private network accessed by their names and not IP addresses, the computer may try to resolve the names to their IP addresses using the FREEDOME DNS server. The DNS servers for FREEDOME do not naturally contain information about your home network devices therefore the host names cannot be translated into their IP addresses.
Due to this, the devices cannot be accessed with their names although they are in the local network.
Both Windows and Mac computers have the possibility to do the name-to-IP translation locally through the hosts file. The operating system checks the hosts file first before doing the DNS query, therefore this can be used to translate the local device names to their IP addresses.
(C:)\Windows\System32\drivers\etc. Change the Text Documents (*.txt) selection to All Files (*.*).
sudo nano /private/etc/hostsand press Enter.
Example to add multiple devices to the hosts file on both Windows and Mac:
Once you have done the steps above, you should now be able to access your devices using their names also when FREEDOME is turned on.
Visit the Community
Check our Forums or How-to & FAQs for advice or answers
View User Guides
Refer to our getting started guides and product manuals
Talk to our Support and get answers to your questions