Received unhandled library message Ping from XXX.XXX.XX.XX
313 views
Skip to first unread message
kfrench16
Jul 15, 2011, 11:30:28 PM7/15/11
to lidgren-network-gen3
I'm new to the Lidgren library. I have been going through the samples
and working on client server code alongside the samples.
Everything was working fine on my machine and through my LAN. My issue
is when I try to use my WAN IP for host connections.
I receive the following message on both client and server
Received unhandled library message Ping from <IP address of client or
server goes here>
I can't seem to find anything regarding this message. As a result of
the message, I cannot process any client requests on the server and
the server eventually crashes.
I have turned off my firewall on the server. I have allowed pings on
the router, server, and client machines. I have opened all necessary
ports on the router. Now, I am out of ideas.
Any ideas at what else I should look at?
and working on client server code alongside the samples.
Everything was working fine on my machine and through my LAN. My issue
is when I try to use my WAN IP for host connections.
I receive the following message on both client and server
Received unhandled library message Ping from <IP address of client or
server goes here>
I can't seem to find anything regarding this message. As a result of
the message, I cannot process any client requests on the server and
the server eventually crashes.
I have turned off my firewall on the server. I have allowed pings on
the router, server, and client machines. I have opened all necessary
ports on the router. Now, I am out of ideas.
Any ideas at what else I should look at?
lidgren
Jul 18, 2011, 5:00:50 PM7/18/11
to lidgren-network-gen3
Yes, there seems to be an issue of ping messages being transmitted
before the connection handshake is complete. I'm going to have a look
at that.
However; that shouldn't disrupt anything else... why can't you process
any client requests, and what code crashes?
--michael
before the connection handshake is complete. I'm going to have a look
at that.
However; that shouldn't disrupt anything else... why can't you process
any client requests, and what code crashes?
--michael
kfrench16
Jul 18, 2011, 7:47:53 PM7/18/11
to lidgren-network-gen3
I'm sending a simple "heartbeat" message type from the client to the
server via a client peer Reliable and ordered. This is all testing and
learning; so, nothing to fancy going on here. The message never gets
to the server that I can tell. I have a message written to the console
when the message type has been received on the server. The message
type is from my own "OP Code" enumeration. As stated, everything works
within the LAN. It is the WAN I am having issues with. I tried testing
from work today to verify that all of my ports are properly forwarded.
No success there. I think work has UDP blocked :) I'm having a co-
worker trying from their home for verification.
Thanks for looking into this. So far, I really like Lidgren.
server via a client peer Reliable and ordered. This is all testing and
learning; so, nothing to fancy going on here. The message never gets
to the server that I can tell. I have a message written to the console
when the message type has been received on the server. The message
type is from my own "OP Code" enumeration. As stated, everything works
within the LAN. It is the WAN I am having issues with. I tried testing
from work today to verify that all of my ports are properly forwarded.
No success there. I think work has UDP blocked :) I'm having a co-
worker trying from their home for verification.
Thanks for looking into this. So far, I really like Lidgren.
kfrench16
Jul 19, 2011, 1:48:18 PM7/19/11
to lidgren-network-gen3
EDIT: Co-worker was able to connect without any issues. It appears
that everything is working fine. I just can't use my external IP while
on my LAN which is fine.
that everything is working fine. I just can't use my external IP while
on my LAN which is fine.
Reply all
Reply to author
Forward
0 new messages