[ENet-discuss] NAT punch-through

[Chris Meub]

I am by no means an expert on the subject, but I am using a really basic
form of NAT punch-through with Enet at the moment with a hobby project. I
have 2 clients, one at home behind a consumer router, and 1 at the office
behind a firewall. Both connect to a central server, and begin transmitting
packets to the server. The server collates the packets into simulation step
packets, and sends those back to each client. This system works fine and
I've had no issues with our firewall or any routers.

Now I imagine if you wanted to get rid of the central server, that would be
another story. You would probably have to still use a central server for
matchmaking and then do some trickery to figure out which IP+port each peer
needed to start sending packets to in order to bypass the firewall(s). But I
imagine one could still do that with Enet.

The only other thing I can think of would be some kind of brute force
library that randomly tries ports until it finds one that can get through
the firewall. Is that what RakNet provides?

On Mon, May 2, 2011 at 1:32 PM, Josh Klint <jklint at leadwerks.com> wrote:

> Hi,
>
>
>
> A search for enet and NAT punch-through yields a lot of questions about
> whether this is possible and discussion of how it might be done, but I have
> never found an actual instance of working code, or anyone who claims to have
> successfully implemented NAT punch-through with enet.
>
> I love the simplicity of enet, but without NAT punch-through support, I
> don't see how it is useful for networked software.  I’ll have to
> (unfortunately) go with RakNet, which is huge, bloated, and comes with
> licensing hang-ups I have to pass on to my customers.
>
>
>
>
>
> Best Regards,
>
>
>
> Josh Klint
>
> CEO
>
> Leadwerks Software
>
>
>
> _______________________________________________
> ENet-discuss mailing list
> ENet-discuss at cubik.org
> http://lists.cubik.org/mailman/listinfo/enet-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cubik.org/pipermail/enet-discuss/attachments/20110502/1a0e0821/attachment.html>