everytime i try to get into a server i get an error saying Can not find UDP packet i know its not my firewall and iv manualy opened a port for it and still nothing, but when i opened the port the error changed from can not find UDP packet to can not connect to host

Quote from McGrath :

everytime i try to get into a server i get an error saying Can not find UDP packet i know its not my firewall and iv manualy opened a port for it and still nothing, but when i opened the port the error changed from can not find UDP packet to can not connect to host

Then check that something like a firewall or router isnt blocking UDP traffic. It's required for LFS.

If you have a router with a built in firewall check that too.

Open default port 63392 for lfs if it has one. Another option is to try contacting your ISP and asking them to leave certain ports permanently open on your connection

Test 1
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator.ADMIN-PC>ping master.liveforspeed.net

Pinging master.liveforspeed.net [213.40.20.2] with 32 bytes of data:

Reply from 213.40.20.2: bytes=32 time=68ms TTL=53
Reply from 213.40.20.2: bytes=32 time=68ms TTL=53
Reply from 213.40.20.2: bytes=32 time=68ms TTL=53
Reply from 213.40.20.2: bytes=32 time=69ms TTL=53

Ping statistics for 213.40.20.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 69ms, Average = 68ms

C:\Documents and Settings\Administrator.ADMIN-PC>

Test 2

C:\Documents and Settings\Administrator.ADMIN-PC>tracert master.liveforspeed.net


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

1 20 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 16 ms 10 ms 207 ms core-ath-03-Po1.forthnet.gr [212.251.60.62]
4 30 ms 28 ms 26 ms pal9-forthnet-1-gr.pal.seabone.net [213.144.181.
49]
5 68 ms 68 ms 67 ms par12-par17-racc1.par.seabone.net [195.22.210.11
1]
6 65 ms 64 ms 70 ms te1-2.mpd01.par02.atlas.cogentco.com [130.117.15
.137]
7 65 ms 64 ms 64 ms te1-2.mpd03.par01.atlas.cogentco.com [130.117.2.
110]
8 69 ms 70 ms 69 ms te1-8.mpd02.lon01.atlas.cogentco.com [130.117.50
.13]
9 69 ms 70 ms 70 ms te3-3.mpd01.lon01.atlas.cogentco.com [130.117.2.
25]
10 69 ms 69 ms 69 ms te1-2.ccr01.lon04.atlas.cogentco.com [130.117.3.
190]
11 77 ms 232 ms 204 ms 149.6.3.186
12 70 ms 69 ms 70 ms loncat01-ge-lon01.core.netline.net.uk [213.40.13
1.73]
13 69 ms 70 ms 69 ms beta.lfs.net [213.40.20.2]

Trace complete.

C:\Documents and Settings\Administrator.ADMIN-PC>

Can I ask what version of LFS do you run? You can see that on the main menu screen of LFS, at the bottom.

I have REALLY annoying warps (all other cars warps) when i play online. I did these test and im asking someone to check em if there is something wrong with my connection. Here is results:

Test 1. Pinging

Pinging master.liveforspeed.net [213.40.20.2]with 32 bytes of data:
Reply From 213.40.20.2: bytes=32 time=52 ms TTL=51
Reply From 213.40.20.2: bytes=32 time=52 ms TTL=51
Reply From 213.40.20.2: bytes=32 time=52 ms TTL=51
Reply From 213.40.20.2: bytes=32 time=52 ms TTL=51

Ping statistics for 213.40.20.2:
Packets: Sent = 4, Received = 4, Lost = 0
(0% Loss),
Approximate round trip times in milli-seconds:
Minimum = 52 ms, Maximum = 52 ms, Average = 52 ms

Test 2. Tracing

Tracing route to master.liveforspeed.net [213.40.20.2]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms TeleWell.gateway [192.168.0.254]
2 6 ms 5 ms 5 ms dsl-lprbrasgw1-fe80fa00-1.dhcp.inet.fi [84.250.128.1]
3 5 ms 6 ms 5 ms 141.208.23.81
4 7 ms 7 ms 7 ms kvlcore1-e-3-0-0.datanet.tele.fi [141.208.8.113]
5 12 ms 11 ms 12 ms hkicore1-e-1-0-0.datanet.tele.fi [141.208.204.129]
6 12 ms 12 ms 12 ms hkiasbr1-s0-0-0.datanet.tele.fi [141.208.8.10]
7 12 ms 12 ms 12 ms hls-b4-link.telia.net [213.248.75.17]
8 49 ms 19 ms 19 ms s-bb2-link.telia.net [80.91.249.2]
9 41 ms 41 ms 41 ms ffm-bb2-link.telia.net [80.239.147.178]
10 44 ms 44 ms 44 ms ffm-b3-link.telia.net [80.91.249.141]
11 42 ms 41 ms 42 ms po1-0.core01.fra03.atlas.cogentco.com [130.117.14.57]
12 44 ms 44 ms 44 ms te9-1.ccr01.fra03.atlas.cogentco.com [130.117.1.30]
13 46 ms 46 ms 46 ms te1-2.mpd04.ams03.atlas.cogentco.com [130.117.48.165]
14 54 ms 54 ms 54 ms te3-1.ccr01.lon01.atlas.cogentco.com [130.117.1.38]
15 55 ms 54 ms 55 ms te3-1.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
16 54 ms 55 ms 55 ms te1-1.ccr01.lon07.atlas.cogentco.com [130.117.48.30]
17 54 ms 54 ms 55 ms te1-1.ccr01.lon04.atlas.cogentco.com [130.117.3.186]
18 64 ms 117 ms 52 ms 149.6.3.194
19 54 ms 54 ms 55 ms loncat01-ge-lon01.core.netline.net.uk [213.40.131.73]
20 51 ms 54 ms 52 ms beta.lfs.net [213.40.20.2]

For me it looks like everything is ok but i wanna be sure since my game is unplayable now...

EDIT: Also, is my host file ok?

# Copyright (c) 1993-2006 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

127.0.0.1 localhost
::1 localhost

Hello again. I got new PCI network card and installed it. Now when i do ping test my ping to master.liveforspeed.net is much higher than before. What could be wrong?

Ping test with new card:


Ping-isäntä: master.liveforspeed.net [213.40.20.2] 32 tavua tietoja:
Vastaus isännältä 213.40.20.2: tavuja=32 aika=159 ms TTL=51
Vastaus isännältä 213.40.20.2: tavuja=32 aika=159 ms TTL=51
Vastaus isännältä 213.40.20.2: tavuja=32 aika=159 ms TTL=51
Vastaus isännältä 213.40.20.2: tavuja=32 aika=154 ms TTL=51

Ping-tilastot 213.40.20.2:
Paketit: Lähetetty = 4, Vastaanotettu = 4, Kadonnut = 0
(0% hävikki),
Arvioitu kiertoaika millisekunteina:
Pienin = 154 ms, Suurin = 159 ms, Average = 157 ms

Before average ping was about 50

what's the link speed set to? what duplex?

but it's most likely something outside of your LAN, probably either between your modem and your ISP, or your ISP and the master server.

Help>>>>>>>

Quote from SANEK_ksa :

Help

With?

I have also noticed since the patch, there is no 'Schumie and Feelthere.com (1)' servers in the list and they are on 24/7?

Since 5 days i have major problems to play online.
I can connect to every server but every 3 -5 seconds my car gets warped a little bit.
Feels like sync is lost for a short time.
Finaly after 1 min connection is lost complete.
Everything on my computer is working fine .Onlinegames like BF2 or CS are ok.
Onlineping is mostly 20 -30





Ping master.liveforspeed.net [213.40.20.2] mit 32 Bytes Daten:

Antwort von 213.40.20.2: Bytes=32 Zeit=34ms TTL=53
Antwort von 213.40.20.2: Bytes=32 Zeit=35ms TTL=53
Antwort von 213.40.20.2: Bytes=32 Zeit=35ms TTL=53
Antwort von 213.40.20.2: Bytes=32 Zeit=33ms TTL=53

Ping-Statistik für 213.40.20.2:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 33ms, Maximum = 35ms, Mittelwert = 34ms

--------------------------------------------------------------


Routenverfolgung zu master.liveforspeed.net [213.40.20.2] über maximal 30 Absch
nitte:

1 1 ms <1 ms <1 ms 192.168.0.1
2 20 ms 9 ms 10 ms 62.214.64.233
3 9 ms * * ge-2-4-567.dor002isp006.versatel.de [62.214.108.
213]
4 100 ms 148 ms 234 ms 10g-9-4.hhb002isp005.versatel.de [62.214.110.110
]
5 15 ms 15 ms 16 ms hhb2cogent.versatel.de [62.214.0.30]
6 25 ms 25 ms 25 ms te3-1.mpd04.ams03.atlas.cogentco.com [130.117.50
.41]
7 32 ms 33 ms 33 ms te3-1.ccr01.lon01.atlas.cogentco.com [130.117.1.
38]
8 35 ms 54 ms 33 ms te3-1.mpd01.lon01.atlas.cogentco.com [130.117.3.
225]
9 33 ms 33 ms 33 ms te1-1.ccr01.lon07.atlas.cogentco.com [130.117.48
.30]
10 33 ms 32 ms 34 ms te1-1.ccr01.lon04.atlas.cogentco.com [130.117.3.
186]
11 35 ms 34 ms 34 ms 149.6.3.194
12 33 ms 33 ms 33 ms loncat01-ge-lon01.core.netline.net.uk [213.40.13
1.73]
13 33 ms 33 ms 33 ms beta.lfs.net [213.40.20.2]

Ablaufverfolgung beendet.

I hope someone has a good idea .
LFS Offline is working fine.

Bye
Z30 SirErich

Quote :

2 20 ms 9 ms 10 ms 62.214.64.233
3 9 ms * * ge-2-4-567.dor002isp006.versatel.de [62.214.108.213]
4 100 ms 148 ms 234 ms 10g-9-4.hhb002isp005.versatel.de [62.214.110.110]
5 15 ms 15 ms 16 ms hhb2cogent.versatel.de [62.214.0.30]

isp problems?

My machine wont list any hosts since the new version, I am assuming this is because you've switched from TCP to UDP. I can see the traffic being blocked by my firewall on the pc but having trouble identifying a rule that would allow it through. If I disable the firewall the servers are listed but obviously I'd rather not do that..

Tried allowing a port through but then the next time it used a different port :-S

Any idea, do I need to allow a specific range of ports through? I've never needed to do this sort of thing previously on the local firewall..

all I know is that the UDP port to retrieve the list of hots is the same used to receive car position packets, so ou shouldn't have problems.

Quote from adrenalinjunkee :

My machine wont list any hosts since the new version, I am assuming this is because you've switched from TCP to UDP. I can see the traffic being blocked by my firewall on the pc but having trouble identifying a rule that would allow it through. If I disable the firewall the servers are listed but obviously I'd rather not do that..

Tried allowing a port through but then the next time it used a different port :-S

Any idea, do I need to allow a specific range of ports through? I've never needed to do this sort of thing previously on the local firewall..

That is an interesting problem.

It sounds like something that could be solved. I think it would be best to ask on the Z25 patch thread. In fact your problem is not related to connecting with the master server - I think you are able to connect to the master, which sends you the initial list of host IP addresses and ports, which your LFS then tries to communicate with to produce the list you see.

Here is the link to the Z25 thread, maybe you should post over there and say which firewall you are using. Maybe there's a way to allow LFS to send and receive UDP packets.

http://www.lfsforum.net/showthread.php?t=62790

I think most consumer firewalls are more application based rather than port based, in that you set a rule for LFS to use any in- or outbound port using a specific protocol rather than a rule for one port to be used by many programs. I guess there should be an exception list like that somewhere where you can let LFS go about its business as normal. The name of your firewall and what you've already tried could be helpful.

Quote from adrenalinjunkee :

My machine wont list any hosts since the new version, I am assuming this is because you've switched from TCP to UDP. I can see the traffic being blocked by my firewall on the pc but having trouble identifying a rule that would allow it through. If I disable the firewall the servers are listed but obviously I'd rather not do that..

Tried allowing a port through but then the next time it used a different port :-S

Any idea, do I need to allow a specific range of ports through? I've never needed to do this sort of thing previously on the local firewall..

Have you tried clicking the "TCP" button in the bottom right of the list of host screen enable it to yes and refresh

Quote from starfox550 :

Have you tried clicking the "TCP" button in the bottom right of the list of host screen enable it to yes and refresh

NOTE : The TCP button does not switch between UDP and TCP. It's just a filter - it does not tell LFS to use TCP to ping all hosts. All it does is, if you switch on the TCP filter, after the new hosts have been pinged using UDP, it then goes back to the old method and pings the old hosts that have not been updated.

So it is only a temporary button to allow you to see old hosts, because Z25 is still compatible with all hosts from Z onwards.

i cant connect to master server
i did forward ports and firewall is off
here are test results

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Druvis>ping master.liveforspeed.net

Pinging master.liveforspeed.net [213.40.20.2] with 32 bytes of data:

Reply from 213.40.20.2: bytes=32 time=290ms TTL=47
Reply from 213.40.20.2: bytes=32 time=196ms TTL=47
Reply from 213.40.20.2: bytes=32 time=237ms TTL=47
Reply from 213.40.20.2: bytes=32 time=193ms TTL=47

Ping statistics for 213.40.20.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 193ms, Maximum = 290ms, Average = 229ms


C:\Documents and Settings\Druvis>tracert master.liveforspeed.net

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

1 2 ms 1 ms 1 ms buffalo.setup [192.168.11.1]
2 5 ms 3 ms 3 ms 85.15.241.65
3 7 ms 4 ms 5 ms 192.168.32.1
4 7 ms 8 ms 16 ms 83.136.143.157
5 9 ms 9 ms 9 ms 10.100.10.206
6 11 ms 9 ms 18 ms 10.100.10.228
7 10 ms 8 ms 10 ms 85.15.194.142
8 15 ms 14 ms 23 ms 85.15.194.141
9 12 ms 8 ms 8 ms 83.136.143.15
10 11 ms 13 ms 10 ms 83.136.143.15
11 26 ms 17 ms * 85.15.192.192
12 21 ms 18 ms 18 ms xe720-202.RT.TC1.STO.SE.retn.net [87.245.249.41]

13 20 ms 21 ms 20 ms port-channel2.440.ar1.ARN3.gblx.net [64.212.109.
133]
14 114 ms 115 ms 114 ms te2-8.ccr01.jfk07.atlas.cogentco.com [154.54.14.
69]
15 115 ms 114 ms * te4-1.mpd03.jfk02.atlas.cogentco.com [154.54.27.
209]
16 188 ms 193 ms 186 ms te9-1.ccr02.jfk02.atlas.cogentco.com [154.54.25.
142]
17 187 ms 185 ms 186 ms te7-3.ccr01.lon01.atlas.cogentco.com [130.117.0.
45]
18 190 ms 191 ms 195 ms te4-4.mpd01.lon01.atlas.cogentco.com [130.117.1.
74]
19 195 ms 319 ms 194 ms te1-1.ccr01.lon07.atlas.cogentco.com [130.117.48
.30]
20 194 ms 192 ms 207 ms te1-1.ccr01.lon04.atlas.cogentco.com [130.117.3.
186]
21 192 ms 200 ms 190 ms 149.6.3.194
22 194 ms 197 ms 194 ms loncat01-ge-lon01.core.netline.net.uk [213.40.13
1.73]
23 192 ms 192 ms 192 ms beta.lfs.net [213.40.20.2]

Trace complete.

i was on the master server yesterday and today it wont let me connect


C:\Users\Nick>tracert master.liveforspeed.net
Tracing route to master.liveforspeed.net [213.40.20.2]
over a maximum of 30 hops:
1 3 ms 1 ms <1 ms 172.16.0.1
2 86 ms 99 ms 98 ms BigPond.BigPond [10.0.0.138]
3 15 ms 29 ms 14 ms 172.18.212.1
4 13 ms 16 ms 13 ms 172.18.69.98
5 14 ms 15 ms 14 ms 172.18.241.9
6 15 ms 13 ms 14 ms Bundle-Ether10.cha45.Brisbane.telstra.net [203.4
5.53.237]
7 16 ms 15 ms 15 ms Bundle-Ether2.cha-core4.Brisbane.telstra.net [20
3.50.44.13]
8 44 ms 31 ms 30 ms Pos0-4-1-0.ken-core4.Sydney.telstra.net [203.50.
6.205]
9 31 ms 30 ms 29 ms Bundle-Ether1.pad-gw2.Sydney.telstra.net [203.50
.6.29]
10 31 ms 31 ms 30 ms TenGigabitEthernet2-0.sydp-core02.Sydney.reach.c
om [203.50.13.50]
11 184 ms 185 ms 185 ms i-2-0-1.wil-core02.bx.reach.com [202.84.144.101]
12 181 ms 178 ms 180 ms i-1-2.tlot03.bi.reach.com [202.84.251.238]
13 185 ms 184 ms 186 ms cogent-peer.tlot03.pr.reach.com [134.159.63.66]
14 183 ms 190 ms 183 ms te8-3.mpd01.lax01.atlas.cogentco.com [154.54.0.2
17]
15 224 ms 220 ms 223 ms te2-8.mpd01.iah01.atlas.cogentco.com [154.54.5.1
01]
16 229 ms 229 ms 231 ms te8-7.mpd01.atl01.atlas.cogentco.com [154.54.28.
253]
17 248 ms 246 ms 247 ms te8-4.mpd01.dca01.atlas.cogentco.com [154.54.28.
197]
18 250 ms 249 ms 247 ms te8-4.mpd03.jfk02.atlas.cogentco.com [154.54.1.1
06]
19 330 ms 329 ms 330 ms te9-1.ccr02.jfk02.atlas.cogentco.com [154.54.25.
142]
20 332 ms 330 ms 329 ms te7-3.ccr01.lon01.atlas.cogentco.com [130.117.0.
45]
21 329 ms 325 ms 324 ms te4-4.mpd01.lon01.atlas.cogentco.com [130.117.1.
74]
22 321 ms 322 ms 321 ms te1-1.ccr01.lon07.atlas.cogentco.com [130.117.48
.30]
23 349 ms 325 ms 350 ms te1-1.ccr01.lon04.atlas.cogentco.com [130.117.3.
186]
24 452 ms 330 ms 341 ms 149.6.3.194
25 378 ms 324 ms 341 ms loncat01-ge-lon01.core.netline.net.uk [213.40.13
1.73]
26 331 ms 330 ms 328 ms beta.lfs.net [213.40.20.2]

I have no idea y it cannot connect

dont worry about my last post cause it is working again

Master Server connection problems after a fresh Z28 install on Vista.

TEST 1 - ping

Microsoft Windows [version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. Tous droits réservés.

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

Envoi d'une requête 'ping' sur master.liveforspeed.net [213.40.20.2] avec 32 oct
ets de données :
Réponse de 213.40.20.2 : octets=32 temps=106 ms TTL=45
Réponse de 213.40.20.2 : octets=32 temps=105 ms TTL=45
Réponse de 213.40.20.2 : octets=32 temps=105 ms TTL=45
Réponse de 213.40.20.2 : octets=32 temps=111 ms TTL=45

Statistiques Ping pour 213.40.20.2:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 105ms, Maximum = 111ms, Moyenne = 106ms

C:\Users\Jonathan>

TEST 2 - tracert (traceroute)

Microsoft Windows [version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. Tous droits réservés.

C:\Users\Jonathan>tracert master.liveforspeed.net

Détermination de l'itinéraire vers master.liveforspeed.net [213.40.20.2]
avec un maximum de 30 sauts :

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms m0n0wall.local [192.168.4.1]
3 8 ms 8 ms 11 ms 74.221.24.3
4 17 ms 13 ms 13 ms cp161.113.187.66.ivic.qc.ca [66.187.113.161]
5 11 ms 25 ms 20 ms pluton3.116-187-66.ivic.qc.ca [66.187.116.3]
6 18 ms 19 ms 20 ms 69.156.255.225
7 19 ms 17 ms 18 ms core4-quebec14_POS2-0-0.net.bell.ca [64.230.170.
73]
8 23 ms 22 ms 20 ms Ncore4-montrealak_POS0-0-0-0.net.bell.ca [64.230
.147.145]
9 29 ms 31 ms 29 ms newcore2-newyork83_so2-0-0.net.bell.ca [64.230.1
87.141]
10 37 ms 34 ms 38 ms BX5-NEWYORK83_POS12-0-0_core.net.bell.ca [64.230
.187.93]
11 30 ms 46 ms 31 ms te2-2.ccr02.jfk05.atlas.cogentco.com [154.54.10.
205]
12 46 ms 32 ms 32 ms te2-4.ccr02.jfk02.atlas.cogentco.com [130.117.0.
53]
13 263 ms 218 ms 226 ms te9-1.mpd03.jfk02.atlas.cogentco.com [154.54.25.
141]
14 108 ms 107 ms 116 ms te9-1.ccr02.jfk02.atlas.cogentco.com [154.54.25.
142]
15 108 ms 109 ms 108 ms te7-1.ccr01.lon01.atlas.cogentco.com [154.54.5.1
21]
16 108 ms 106 ms 105 ms te3-1.mpd01.lon01.atlas.cogentco.com [130.117.3.
225]
17 108 ms 106 ms 104 ms te1-2.ccr01.lon04.atlas.cogentco.com [130.117.3.
190]
18 108 ms 111 ms 109 ms 149.6.3.186
19 120 ms 126 ms 133 ms loncat01-ge-lon01.core.netline.net.uk [213.40.13
1.73]
20 139 ms 133 ms 107 ms beta.lfs.net [213.40.20.2]

Itinéraire déterminé.

C:\Users\Jonathan>

Host files are correct, firewall is also correctly set. Even when I disable it there's no change.

Apart from node 13 possibly causing lag spikes or DCs there's nothing wrong with it. If your ISP is Cogent you can try to call them up, otherwise not much you can do.

You can test how bad the node 13 problem is by running ping -t 154.54.25.141 for a minute or two and see if it drops packets.

I tried running the ping -t 154.54.25.141 command and I dont seem to havew any packet loss. I remember I called my ISP one or three times because he was blocking something, but I cant remember what it was. So, what do I ask him?

Thanks for your quick reply btw