[geeks] bridging games

[Charles Shannon Hendrix]

Mon, 01 Jan 2007 @ 18:00 -0600, Phil Brutsche said:

> Charles Shannon Hendrix wrote:
> > 	I made sure both LANs can route to each other.
> > 
> > 	I put a redirect on my router box (NetBSD U1) machine's ipnat.conf
> > 	redirecting the game ports to the game server.
> 
> Most LAN games are specifically designed to be played over just that: a
> LAN; same ethernet segment, same IP subnet, etc.

I know.  I need to fool the clients on the other LAN into thinking one
of the IPs on their LAN is really the game server.

I thought that should be pretty simple with routing and NAT rules, but
it appears harder than I thought.

What, besides a NAT mapping, do I need to make a server on one LAN
appear to really be on another?

I figured only the listening port needed to be redirected, because after
that the automatic NAT rewriting would do the rest.

> I think it's silly how hard games make simple things. What happed to the
> days of specifying the IP # of the server ala Quake3?

Definitely.  Nothing wrong with a server browser, but what *IDIOT*
decided it should be the only way to make a connection?

If I could give an IP, network routing would handily take care of the
rest.

Likewise the idiots who write game software which *must* phone home
before playing. They should all be shot, but only after a few days of
torture.


-- 
shannon "AT" widomaker.com -- ["All of us get lost in the darkness,
dreamers turn to look at the stars" -- Rush ]