Spring RTS Engine

Hello all,

I just joined the forums to ask if anyone knew how to host without hole punching from behind a firewall/router.

I have access to the router and I know how to allow/deny traffic on a port. I don't know if that's the same as port forwarding. If it is then great, if not - I'll do some searching to find out how to do that.

The main problem with hole punching is that not everyone can connect, and every time someone gets dropped I feel like an a$$. I already opened traffic on the port I am trying to host on. Even so, I can only host with hole punching on.

M

Did you open the port for UDP traffic ?

yes, but still I can only host with hole punching, everything else fails

Does your routers has a 'real' IP address ? (maybe you ISP connects you through NAT). In case it doesn't you can't do much....

i have a static ip if that is what you mean.

I mean routable ip... (you can have for example a static class C ip for the router like 192.168.0.1 - that wouldn't help).

I just reread your first post. I do not think opening a port is equivalent to port forwarding. There should be a special configuration of your router (and I guess every router would name it differently). Maybe you can tell us the router model and someone else has the same type....

http://www.portforward.com should tell you everything you need to know (including router specific information [unless you have a very obscure router])

i use a gateway pc computer as my firewall and server, so port portforward.com doesn't really help.

looks like hole punching is the only option. ime, there are not that many people that cannot connect to a hole-punched server. you cannot account for every possible user setup on your host, they just gotta deal (and surely they must know if they have trouble connecting to a nat enabled host)

you could also run the autohost off the gateway computer...

So you should setup port forwarding on your router and on your gateway computer... It would be possible, but is it worth the trouble ?

it would be easy

aegis wrote:it would be easy

sure... if I knew how.

if you know how to port forward on a FreeBSD-based apache server running ipfirewall, I'd be very grateful if you shared the knowledge

why are you running your internet through a webserver running freebsd and ipfirewall if you don't know how to use it?


does it still call NAT/forwarding "divert" rules?

My dad set it up that way. I just punch holes in it when I need to, and then cover them back up after I'm done with them.