🚀 go-pugleaf

"Gregor" <gregor...@yahoo.com> wrote in message 
news:1162669421.059436.111900@m73g2000cwd.googlegroups.com...
> Hi all,
> I have been suffering from the following problem:
> Some time ago BT has gave me a hub. Since then I have not been able to
> join to any game and play comfortable. When I do this the net latency
> is so high that I am not able to do anything and usually the game drops
> me out. As a remedy I configured ip port forwarding (6112 in and out)
> to host a games. In most cases is fine and I can play even 3v3 quite
> all right. Why I still can not join and play without lags? Is anybody
> here who had similar problems and has managed to sort this out? Any
> tips in router configuration? Why the joining to the games is different
> than hosting the games? After all this is not a client-server
> connection!
> Cheers:
> Gregor
>

If this fixes most of your problems then you probably did it correctly.

The lagging is probably coming from someone else, very likely if you are 
playing in 3vs3 games - other people who perhaps did not have their ports 
forwarded ;)

Once you get going it is not client/server - but there is originally a host 
computer.  If you are the host then you need to be able to accept incoming 
connections to setup the game initially.    If your router receives incoming 
TCP or UDP packets unsolicited, then it won't know what to do with them, 
unless you have setup port forwarding - and then the problem that you are 
seeing will happen, you will appear to be hosting normally, but no one will 
be able to join your game.

--
LTP

:) 

> If this fixes most of your problems then you probably did it correctly.
> 
> The lagging is probably coming from someone else, very likely if you are 
> playing in 3vs3 games - other people who perhaps did not have their ports 
> forwarded ;)
> 
> Once you get going it is not client/server - but there is originally a host 
> computer.  If you are the host then you need to be able to accept incoming 
> connections to setup the game initially.    If your router receives incoming 
> TCP or UDP packets unsolicited, then it won't know what to do with them, 
> unless you have setup port forwarding - and then the problem that you are 
> seeing will happen, you will appear to be hosting normally, but no one will 
> be able to join your game.
> 
> --
> LTP
> 
> :) 
> 
> 

Can port forwarding be used to solve the problem of two machines behind 
one router/ADSL modem wanting to play on Battle.net in the same game 
with someone else farther afield?

Cheers,
Chris

"Chris Cole" <tele...@tpg.com.au> wrote in message 
news:457d1631@dnews.tpgi.com.au...
> Can port forwarding be used to solve the problem of two machines behind 
> one router/ADSL modem wanting to play on Battle.net in the same game with 
> someone else farther afield?

Oh THAT problem

Oh god . . .

Let me search the old google groups for the nasty ugly fix.   Ah nevermind

Something like this.   yadda yadda yadda starcraft appears to have 
originally been designed to work on up to 7 ports, but an option to choose 
which one mysteriously disappeared, but SC will still reply on the the port 
which initiated the contact.

Problem is, you will need to dynamically remap the outcoming and incoming 
UDP port.  This can be accomplished on many (but not all) modern routers

You can find instructions for doing it through a Linux box.

No I have never done it myself  ;)

What we need - is a client to act as a inline rerouter - so outgoing packets 
on port 6112 are remapped to 6113 before they leave the machine, and coming 
in, 6113 back to 6112 - AFAIK, no such client exists.

I actually paid for a seperate ISP to dial up to fix this problem

Sorry d00d - SC was not designed for two people to play from same IP address

I've also heard there is some fix, involving DDNS - but I have never heard 
of a successful implementation (doesn't mean it doesn't exist)

I suggest setting up a dish to look for an unsecured wireless network (or 
hackable WEP network) somewhere from a friendly neighbour.

--
LTP

:)