Im having this problem and thought i knew why but now i read something and wanted to make sure:
Anyone else have weird problems with wireless LAN? Im in germany and i use T-Online. Works without problems via solid LAN so it must be something with the wireless card or the config or interference. So if youre in germany running WLAN please tell your configuration.
The problem in detail:
Only WLAN: My ping varies from 30 to 5000 with peaks up to infinity. So i have huge delays but i dont get any "clocks". It just freezes sometimes.
WLAN
Moderators: Nexuiz Moderators, Moderators
5 posts
• Page 1 of 1
by divVerent » Mon Oct 23, 2006 6:13 am
Unfortunately, that is normal with WLAN. WLAN has quite some packet loss...
The closer you are to the WLAN access point and the better you align the antennae, the better is your reception. Try some packet generator tools (or on Linux, ping ) to test your packet loss.
root@macmini:~# ping -f -s 1400 192.168.178.1
In my case (the IP is an access point) I then got after a while:
11474 packets transmitted, 11473 received, +204 duplicates, 0% packet loss, time 38730ms
rtt min/avg/max/mdev = 3.001/3.314/9.200/0.474 ms, pipe 2, ipg/ewma 3.375/3.207 ms
Hm... DUPLICATES? Even that happens in WLANs? I will talk to LordHavoc if DP has issues with duplicates...
The closer you are to the WLAN access point and the better you align the antennae, the better is your reception. Try some packet generator tools (or on Linux, ping ) to test your packet loss.
root@macmini:~# ping -f -s 1400 192.168.178.1
In my case (the IP is an access point) I then got after a while:
11474 packets transmitted, 11473 received, +204 duplicates, 0% packet loss, time 38730ms
rtt min/avg/max/mdev = 3.001/3.314/9.200/0.474 ms, pipe 2, ipg/ewma 3.375/3.207 ms
Hm... DUPLICATES? Even that happens in WLANs? I will talk to LordHavoc if DP has issues with duplicates...
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again
You can vary the number of "MS", so you can clearly see it's MS which is causing it.
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again
You can vary the number of "MS", so you can clearly see it's MS which is causing it.
- divVerent
- Site admin and keyboard killer
- Posts: 3809
- Joined: Thu Mar 02, 2006 4:46 pm
- Location: BRLOGENSHFEGLE
by divVerent » Sun Dec 24, 2006 7:26 pm
Try one thing:
open a command prompt/shell/DOS window (whatever you call it) and run a ping test, like: "ping -t 141.2.16.3" (Windows) or "ping 141.2.16.3" (Linux).
Then start the game and play online for at least ten minutes, preferably on my CTF server (141.2.16.3). If you use another server, ping the server's IP, not mine (ping and playing should be the same server for the results to make sense).
After that, quit the game and press Ctrl-C in the window in which you started the ping. Look at the report at the end:
on Windows; on Linux it would look like
It should show at least 500 packets.
Loss should never be above one percent. If you are on Linux, the mdev should be small compared to the avg value. On Windows, the maximum should not be large. In any case, minimum and average should be close together.
If not, something is wrong with your connection. If mdev is small, maximum is not THAT large, no loss occurred, and minimum and average are close together, and the ping is below 100ms, let us know. But I haven't ever seen a WLAN connection that passes this test.
If however it shows 100% packet loss, either your computer or the server you are playing on is firewalled and does not respond to ping. In that case, use another server (like 141.2.16.3); if that does not help, check your firewall settings and change them to allow you to ping.
open a command prompt/shell/DOS window (whatever you call it) and run a ping test, like: "ping -t 141.2.16.3" (Windows) or "ping 141.2.16.3" (Linux).
Then start the game and play online for at least ten minutes, preferably on my CTF server (141.2.16.3). If you use another server, ping the server's IP, not mine (ping and playing should be the same server for the results to make sense).
After that, quit the game and press Ctrl-C in the window in which you started the ping. Look at the report at the end:
- Code: Select all
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 130ms, Average = 112ms
on Windows; on Linux it would look like
- Code: Select all
7 packets transmitted, 7 received, 0% packet loss, time 6001ms
rtt min/avg/max/mdev = 73.152/74.913/76.703/1.154 ms
It should show at least 500 packets.
Loss should never be above one percent. If you are on Linux, the mdev should be small compared to the avg value. On Windows, the maximum should not be large. In any case, minimum and average should be close together.
If not, something is wrong with your connection. If mdev is small, maximum is not THAT large, no loss occurred, and minimum and average are close together, and the ping is below 100ms, let us know. But I haven't ever seen a WLAN connection that passes this test.
If however it shows 100% packet loss, either your computer or the server you are playing on is firewalled and does not respond to ping. In that case, use another server (like 141.2.16.3); if that does not help, check your firewall settings and change them to allow you to ping.
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again
You can vary the number of "MS", so you can clearly see it's MS which is causing it.
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again
You can vary the number of "MS", so you can clearly see it's MS which is causing it.
- divVerent
- Site admin and keyboard killer
- Posts: 3809
- Joined: Thu Mar 02, 2006 4:46 pm
- Location: BRLOGENSHFEGLE
5 posts
• Page 1 of 1
Return to Nexuiz - Performance Tips
Who is online
Users browsing this forum: No registered users and 1 guest