by karma » Fri Sep 09, 2005 9:24 am
strange. have you had any luck starting over? here's another tip.
Check out GIT logging information. If you have been logging with GIT, check out the logs for the times between establishing connection, starting game, and lag out. check the timestamps; you can see how saturated your tunnel gets by looking at the difference between timestamps of forwarded packets. I have a 288kbps upstream. I've seen 40 udp starcraft packets per second being forwarded from me, in a lagless game. Check out your upstream speed and how many packets per second have status 'ok'.
here is an entry in forwarded.log which was one of the 40 per second.
[Thu Jun 30 19:22:59 2005] network: hw:00:30:1b:b1:f4:b0 EthernetII IPv4 UDP to:192.168.0.100:6112 from:192.168.0.12:6112 'ok'
Basically, that breaks down to.. timestamp, nic card, protocol, to host:port, from host:port, status.
If you have not been logging already, rightclick git tray icon, select logging, turn on all. Note the time, make your git connection, observe network crash.. again note the time. Then go back through your logs and see how traffic behaved. There might be a clue there.
--rob