GitHub - foodini/game_echo_service: Five or six years ago, I was stuck writing a network emulation layer for a PS2 game. I was told that all the classic behaviors of an internet connection had to be displayed; realistic loss characteristics, packet reordering, latency, rush-induced packet loss. Essentially, I was told to implement the internet in a couple weeks. I suggested just bouncing all our game traffic off a remote echo server. When I was told that it was absolutely forbidden to send development traffic out over public wires, I simply created a server that everyone pointed their PS2 devkits at that would store every packet it received and send a doppleganger (full of an id for the original packet plus a bunch of random garbage to make it the same size) out to the echo servers I ran. When the doppleganger was received, I would pass the original packet on to its original destination. Boom. Internet simulation with all the thorns.

foodini / game_echo_service Public

Notifications You must be signed in to change notification settings
Fork 1
Star 2

Five or six years ago, I was stuck writing a network emulation layer for a PS2 game. I was told that all the classic behaviors of an internet connection had to be displayed; realistic loss characteristics, packet reordering, latency, rush-induced packet loss. Essentially, I was told to implement the internet in a couple weeks. I suggested just b…

2 stars 1 fork Branches Tags Activity

Star

Notifications

Branches Tags

Name		Name	Last commit message	Last commit date
Latest commit History 2 Commits
.gitattributes		.gitattributes
Makefile		Makefile
README.txt		README.txt
proxy.cpp		proxy.cpp
proxy_sockets.cpp		proxy_sockets.cpp
proxy_sockets.h		proxy_sockets.h
proxy_threads.cpp		proxy_threads.cpp
proxy_threads.h		proxy_threads.h
terminator.cpp		terminator.cpp

Repository files navigation

This project provides you with a way to push local UDP traffic out to a remote
echo server, then accept the echoed data back and forward it to its final
destination. This is most useful to developers who are testing internet-
enabled games that they wish to run between nodes on their local network, but
want to be able to see how the game will behave under real network load and
loss.

I wrote this a while back in order to provide a tangible answer to my question
on stackoverflow:

http://stackoverflow.com/questions/2329059/network-simulator/2362274#2362274

(There, I'm "sniggerfardimungus".)

Because the code I describe there was owned by the company that employed me at
the time, I wrote it all from scratch a year or so ago. This repository is the
result of that effort.

This version does not encrypt your echoed traffic, as described on 
stackoverflow. That will be added later, if there is sufficient interest. It
does set up a Unity policy server, since I have a current interest in using
Unity for something else I'm doing.

It should build on Windows, using Visual Studio, cygwin, mac, and linux. I
will formalize that support better as I find time to mature the project.


proxy.cpp is the proxy server itself. It accepts TCP connections and routes
each through the echo server before forwarding the data along to their
destination. See the help text in game.cpp for a description of how to provide
the game server (the destination) and the echo server info.

terminator.cpp is the echo server. It takes a single argument, the port number
to listen on.