[ENet-discuss] ENet-discuss Digest, Vol 69, Issue 1

[Aidan McKenna]

I figured it out - I was using a descriptive hostname ie. 
"www.grassgames.com" but the actual host ip / port number was slightly 
different - changing it to the actual ip/port fixed the problem.

A new problem now. I've implemented (it wasn't easy) STUN and UDP hole 
punching and get get traffic send both ways in some router 
configurations and only one way in other more complicated situations. I 
believe if more than one router is in the system, things won't work, 
traffic can be sent from the person behind one router to the person 
behind two, but not received. Enet is doing its job perfectly, so its 
not the place to ask this, but if you have any experience of this 
problem advice would be appreciated. If not, great job with Enet.

BTW, the actual STUN/UDP punch through stuff uses sockets, not Enet. 
Enet takes over once the connection has been established.

Cheers,
Aidan.



Brandon Dawson wrote:
> Are you using a TCP connection for server to client communication?  
> ENET? The problems could be pretty endless in this situation.  Are you 
> positve that there was a successful connection between the server and 
> the client?
>
> -B
> ----- Original Message ----- From: <enet-discuss-request at cubik.org>
> To: <enet-discuss at cubik.org>
> Sent: Wednesday, February 04, 2009 12:00 PM
> Subject: ENet-discuss Digest, Vol 69, Issue 1
>
>
>> Send ENet-discuss mailing list submissions to
>> enet-discuss at cubik.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://lists.cubik.org/mailman/listinfo/enet-discuss
>> or, via email, send a message with subject or body 'help' to
>> enet-discuss-request at cubik.org
>>
>> You can reach the person managing the list at
>> enet-discuss-owner at cubik.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of ENet-discuss digest..."
>>
>>
>> Today's Topics:
>>
>>   1.  NAT Traversal (Aidan McKenna)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 04 Feb 2009 09:09:58 -0300
>> From: Aidan McKenna <aidan at grassgames.com>
>> Subject: [ENet-discuss] NAT Traversal
>> To: enet-discuss at cubik.org
>> Message-ID: <49898596.5060000 at grassgames.com>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> Hello there,
>>
>> I mentioned before having problems getting connections over NATs, and
>> was told to investigate STUN etc. which I did. I ended up getting a
>> successful NAT UDP hole punch through solution going.
>>
>> I finally got a connection working fine the other day with a friend via
>> 2 routers.
>>
>> However its still not working for a lot of people. I have a server setup
>> that is not behind any NATs that both players communicate with in order
>> to get the public network address of the other player.
>>
>> The problem is that while the server can send a message to some players,
>> other players do not get any response at all from the server. The
>> message is sent from the server ok back to the exact address as the
>> incoming request from the player, but the player is not getting this
>> message.
>>
>> Anybody know what the problem is here?
>>
>> Cheers,
>> Aidan.
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> ENet-discuss mailing list
>> ENet-discuss at cubik.org
>> http://lists.cubik.org/mailman/listinfo/enet-discuss
>>
>>
>> End of ENet-discuss Digest, Vol 69, Issue 1
>> *******************************************
>>
>
> _______________________________________________
> ENet-discuss mailing list
> ENet-discuss at cubik.org
> http://lists.cubik.org/mailman/listinfo/enet-discuss
>
>