The online racing simulator
Cant connect to master server, only with vpn,
1st test

C:\Users\dionb>ping master.liveforspeed.net

Pinging master.liveforspeed.net [188.122.74.158] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 188.122.74.158:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

2nd test


Tracing route to master.liveforspeed.net [188.122.74.158]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.


host file

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

soo, i can only connect to master using a vpn and now im getting host did not recieve UDP packet
Please help me

-ImDion
Hi there,

Neither ping nor traceroute are reliable ways of troubleshooting TCP/UDP (I'm sure the LFS client is uses both) connections since those tools use ICMP.

The DNS/hosts config appears to be correct. I am seeing the same name resolutions as you do:

dig +short lfs.net master.lfs.net liveforspeed.net master.liveforspeed.net A
188.122.74.150
188.122.74.158
188.122.74.150
188.122.74.158

Though I don't have access to LFS at the moment so I cant check which domains the client actually tries to resolve (I think *.liveforspeed.net is deprecated).

Sounds like a firewall issue to me.

The VPN connection most likely brings up a new interface that is, contrary to you default interface, allowed to talk to the LFS services.
What kind of VPN service are you using?


Edit: Oh I misread, the VPN didn't make it work -- It just threw a different error.

Can you give us some more information about what happens in LFS when you are NOT using the VPN?
#3 - troy
I can't ping master.liveforspeed.net any more either, maybe something changed there. I still get the server list though. No help I know, just wanted to let you know it's probably not a problem caused by not being able to ping it.
Quote from troy :I can't ping master.liveforspeed.net any more either, maybe something changed there. I still get the server list though. No help I know, just wanted to let you know it's probably not a problem caused by not being able to ping it.

Exactly. That the server drops/rejects ping (ICMP) requests says nothing about the server's availability (nor the state of it's listening services).
Quote from felplacerad :Exactly. That the server drops/rejects ping (ICMP) requests says nothing about the server's availability (nor the state of it's listening services).

im using Hotspotshield vpn
I do get "host did not recieve UDP packet at the moment"
Quote from DriftingDion :im using Hotspotshield vpn
I do get "host did not recieve UDP packet at the moment"

Thanks, I thought you got it working with the VPN but then I realised it just threw another error. I suggest trying to troubleshoot this without using the VPN.

What does LFS output when you are not using the VPN?

If you're still stuck later I will be able to assist you better tonight when I'm at home and have access to LFS.
Quote from felplacerad :Thanks, I thought you got it working with the VPN but then I realised it just threw another error. I suggest trying to troubleshoot this without using the VPN.

What does LFS output when you are not using the VPN?

If you're still stuck later I will be able to assist you better tonight when I'm at home and have access to LFS.

Thanks, i'm not sure if im home tonight since ive got a birthday Tongue

So i start up lfs, try to login and im unable to connect to master lfs server, with other games (steam,lol,minecraft) i cant connect to servers aswell when i turn on a vpn i can login and play online, ive recently done a clean windows install, so i dont know the problem
Hope this helps

----IPCONFIG----

Microsoft Windows [Version 10.0.10586]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\dionb>ipconfig

Windows IP Configuration


Ethernet adapter Hamachi:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2620:9b::197e:391
Link-local IPv6 Address . . . . . : fe80::25e6:3230:b3b1:a96e%14
IPv4 Address. . . . . . . . . . . : 25.126.3.145
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 2620:9b::1900:1
25.0.0.1

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::855e:2fc:44bf:2fda%2
IPv4 Address. . . . . . . . . . . : 192.168.178.13
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.178.1

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::2c10:e770:98c9:5550%6
IPv4 Address. . . . . . . . . . . : 10.254.248.12
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{9C35EE73-8453-44D5-B837-89051D50F1F8}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter isatap.{0C1A963F-3240-4DB3-BB05-76C9103E881F}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter isatap.{EBB79AB0-00D2-450F-B1A6-A04CC9D4EA9E}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Users\dionb>
"Ethernet adapter Ethernet" should be your primary interface and it's ipv4 and gateway config looks fine as far as I can tell. Otherwise you shouldn't be able to surf the net.

Hamachi AND Hotspotshield though? Tongue Looks like Hamachi is currently up.
Try disabling it.

Also, have you installed any antivirus/firewall software (other than the built-in Windows firewall)?
They are both off now, no difference
I only have the essentials from microsoft and malwarebytes


Microsoft Windows [Version 10.0.10586]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\dionb>ipconfig

Windows IP Configuration


Ethernet adapter Hamachi:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2620:9b::197e:391
Link-local IPv6 Address . . . . . : fe80::25e6:3230:b3b1:a96e%14
IPv4 Address. . . . . . . . . . . : 25.126.3.145
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 2620:9b::1900:1
25.0.0.1

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::855e:2fc:44bf:2fda%2
IPv4 Address. . . . . . . . . . . : 192.168.178.13
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.178.1

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::2c10:e770:98c9:5550%6
IPv4 Address. . . . . . . . . . . : 10.254.248.12
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{9C35EE73-8453-44D5-B837-89051D50F1F8}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter isatap.{0C1A963F-3240-4DB3-BB05-76C9103E881F}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter isatap.{EBB79AB0-00D2-450F-B1A6-A04CC9D4EA9E}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Users\dionb>ipconfig

Windows IP Configuration


Ethernet adapter Hamachi:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2620:9b::197e:391
Link-local IPv6 Address . . . . . : fe80::25e6:3230:b3b1:a96e%14
IPv4 Address. . . . . . . . . . . : 25.126.3.145
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 2620:9b::1900:1
25.0.0.1

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::855e:2fc:44bf:2fda%2
IPv4 Address. . . . . . . . . . . : 192.168.178.13
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.178.1

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter isatap.{0C1A963F-3240-4DB3-BB05-76C9103E881F}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter isatap.{EBB79AB0-00D2-450F-B1A6-A04CC9D4EA9E}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Users\dionb>
Quote from felplacerad :"Ethernet adapter Ethernet" should be your primary interface and it's ipv4 and gateway config looks fine as far as I can tell. Otherwise you shouldn't be able to surf the net.

Hamachi AND Hotspotshield though? Tongue Looks like Hamachi is currently up.
Try disabling it.

Also, have you installed any antivirus/firewall software (other than the built-in Windows firewall)?

forgot to quote u Tongue
So I had a quick look with LFS and it appears as if when you click "Display list of hosts" a sequence of TCP packets are transferred between your client (src port ~9k) and master.liveforspeed.net (188.122.74.158, dst port 29339).

That port is actually documented as a required port (at least for hosting) here: https://www.lfs.net/faq/host/13

Then your client retrieves each individual server's information using UDP.

If I block master.liveforspeed.net locally LFS throws an error message: "Could not connect to to master server [...].

Is that what you are seeing in LFS?
Quote from felplacerad :So I had a quick look with LFS and it appears as if when you click "Display list of hosts" a sequence of TCP packets are transferred between your client (src port ~9k) and master.liveforspeed.net (188.122.74.158, dst port 29339).

That port is actually documented as a required port (at least for hosting) here: https://www.lfs.net/faq/host/13

Then your client retrieves each individual server's information using UDP.

If I block master.liveforspeed.net locally LFS throws an error message: "Could not connect to to master server [...].

Is that what you are seeing in LFS?

Fixed, running my pc of another router
Ty for help Smile

FGED GREDG RDFGDR GSFDG