Re: Quake 3 with cipe|
Richard Gregory <R.Gregory,AT,liverpool,DOT,ac,DOT,uk>|
Wed, 10 Dec 2003 12:00:53 +0000|
Erm yes, that is why the third paragraph of my original message said this:
Some background... Quake does most of its communications using UDP port
27960. The game server sends packets out representing the current state
of the game at a rate of around 25 per second, ~100 bytes each to port
27960. The clients send back packets representing the users actions, at
around the same rate, size and the same UPD port.
As you can see, this isn't TCP at all, it is basic UDP. So why does
XP/Q3 create those extra packets??
| Computer Science, Room G34 |
| http://www.csc.liv.ac.uk/~greg |
| Electrical Engineering, Room ~104 |
Rob Nelson wrote:
> On Mon, 8 Dec 2003, Richard Gregory wrote:
>>Noticed a problem with Quake 3 network traffic when routed over cipe.
>>Quake 3 sends four times as many UDP packets to the game server as it
>>does when outside the tunnel (or in a ssh/pppd tunnel). This problem
>>only happens when the Quake3 client runs on an XP machine, reboot into
>>Linux and the packet rate becomes one-to-one.
>>This is still the case when the Linux Q3 config file is copied over the
>>Q3 XP config. All in all, suggesting some sort of interaction problem
>>with cipe and XP, but I've no idea what. Does anybody have any
> What protocol is quake running? There are differences in how the tcp/ip
> stack is configured on linux and windows. Knowing whether quake runs udp
> or tcp would help to configure it. Are there any differences in the
> packet trace besides the XP client's extra chatter?
> Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> Other commands available with "help" in body to the same address.
> CIPE info and list archive: