|
|
Post by Jarhead on Mar 15, 2012 10:13:55 GMT -8
Does anyone else here setup their routers to port forward while playing rFactor? I know it's not as critical as with the xbox, but as we saw last night with 17 people on the track at once, even rFactor can have lag and connection issues. I checked and there are 3 ports you should have forwarded for rFactor. TCP 34447, and UDP 34297 and 34397. If you don't know how to do port forwarding, check out www.portforward.comI'm sure some of the members here can also help out if someone needs it. I know how to do my own, but every router is different so I don't know how much help I would be to anyone else. One thing to remember, most home networks have DCHP which can assign a different internal IP Address to your computer every time you turn it on. I'm sure some of you know how to setup a static IP, but I just check my IP whenever I turn on my computer or xbox and if the IP has changed, I just re-forward the ports. Something I think everyone should look into as GBR seems to be really expanding. Would be nice to have fields of 20+ cars with no lag or connection issues. |
|
F1Fan07
Race Director
Ludicrous speed. Gone to plaid.
Posts: 9,366
|
Post by F1Fan07 on Mar 15, 2012 11:34:32 GMT -8
Those are the incoming ports for a PC hosting the server. Forwarding those at your end will do nothing to improve gameplay for the clients. I'll sniff my network traffic to confirm that tonight though. I've been hosting for quite a while without issues. I have bandwidth to spare (100/5 connection) and CPU power to spare on that PC. Lag has been observed really in just the last few weeks and with 3 or 4 cars only on the track (so it's not field size related). That raises the question of why are we seeing lag suddenly? The most likely reason occured to me on my lunch break today. My ISP is performing digital network upgrades in the city (analog cable channels went dark on Mar 12 for faster internet service and more HD channels) and I suspect they're shifting traffic around and overloading nodes as they work on others. The other possible reason is the virtual server configuration I use is choking on the simultaneous connections. I'm going to move rFactor on to a non-virtualized server in the next couple of days to see if that helps. The third reason might be that my network card is about to go tits-up. That's an easy thing to test. I'm running line quality testing software all day today as well. As an aside, 34297 UDP is only required for LAN gaming. ftp.osrw.com/rFactor/Manual/FirewallGuide.pdf |
|
F1Fan07
Race Director
Ludicrous speed. Gone to plaid.
Posts: 9,366
|
Post by F1Fan07 on Mar 15, 2012 12:06:44 GMT -8
OK, that testing didn't take long. I'm getting major packet loss.
To quote Adam Savage "Well, there's your problem!"
Ping test at : 3/15/2012 1:07:27 PM - 3/15/2012 1:08:33 PM
Result:
Sent: 33
Received: 28
Lost: 5
Loss Rate: 15.15 %
Min Time: 68 ms
Max Time: 95 ms
Avg Time: 75 ms
Avg TTL: 51
Detail:
1. 3/15/2012 1:07:27 PM Reply from 74.208.xx.xx bytes=32 time=88ms TTL=51 ok
2. 3/15/2012 1:07:29 PM Reply from 74.208.xx.xx bytes=32 time=74ms TTL=51 ok
3. 3/15/2012 1:07:31 PM Reply from 74.208.xx.xx bytes=32 Request timed out.
4. 3/15/2012 1:07:33 PM Reply from 74.208.xx.xx bytes=32 time=95ms TTL=51 ok
5. 3/15/2012 1:07:35 PM Reply from 74.208.xx.xx bytes=32 time=70ms TTL=51 ok
6. 3/15/2012 1:07:37 PM Reply from 74.208.xx.xx bytes=32 time=68ms TTL=51 ok
7. 3/15/2012 1:07:39 PM Reply from 74.208.xx.xx bytes=32 time=70ms TTL=51 ok
8. 3/15/2012 1:07:41 PM Reply from 74.208.xx.xx bytes=32 time=72ms TTL=51 ok
9. 3/15/2012 1:07:43 PM Reply from 74.208.xx.xx bytes=32 time=70ms TTL=51 ok
10. 3/15/2012 1:07:45 PM Reply from 74.208.xx.xx bytes=32 Request timed out.
11. 3/15/2012 1:07:47 PM Reply from 74.208.xx.xx bytes=32 time=74ms TTL=51 ok
12. 3/15/2012 1:07:50 PM Reply from 74.208.xx.xx bytes=32 time=86ms TTL=51 ok
13. 3/15/2012 1:07:52 PM Reply from 74.208.xx.xx bytes=32 time=80ms TTL=51 ok
14. 3/15/2012 1:07:54 PM Reply from 74.208.xx.xx bytes=32 time=72ms TTL=51 ok
15. 3/15/2012 1:07:56 PM Reply from 74.208.xx.xx bytes=32 time=70ms TTL=51 ok
16. 3/15/2012 1:07:58 PM Reply from 74.208.xx.xx bytes=32 Request timed out.
17. 3/15/2012 1:08:00 PM Reply from 74.208.xx.xx bytes=32 time=71ms TTL=51 ok
18. 3/15/2012 1:08:02 PM Reply from 74.208.xx.xx bytes=32 time=69ms TTL=51 ok
19. 3/15/2012 1:08:04 PM Reply from 74.208.xx.xx bytes=32 time=92ms TTL=51 ok
20. 3/15/2012 1:08:06 PM Reply from 74.208.xx.xx bytes=32 time=81ms TTL=51 ok
|
|
|
|
Post by Jarhead on Mar 15, 2012 13:35:35 GMT -8
So, is there nothing we need to do on the client side to help make a more stable connection? I have FiOS with a 35/35 internet package which I have tested with speedtest.net and got 42/36. I rarely have issues at my end and when I do its normally my kids downloading or streaming videos. I usually tell them before any race to not download or stream anything which normally gives me a great connection.
|
|
F1Fan07
Race Director
Ludicrous speed. Gone to plaid.
Posts: 9,366
|
Post by F1Fan07 on Mar 15, 2012 13:42:10 GMT -8
So, is there nothing we need to do on the client side to help make a more stable connection? There is some bandwidth tuning in the game (I'm not at my PC right now to find the settings) relating to upload and downlaod speed but it shouldn't be needed for 20 guys and I don't know if it's needed at all. I have definite problems right now with packet loss and have reported it to my ISP. So for now, I wouldn't try to change anything on your end. |
|
