I have a little minetest server running on a raspberry pi. I can connect to the server just fine directly on my LAN and it works great.
I'd like to make it accessible to some friends. I setup port forwarding on my asus router, and setup a DDNS name, which all seems to work fine, however, when attempting to connect my client via the Internet using my DDNS name, I get the following output when running the client with --verbose:
Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.
- Code: Select all
22:07:25: INFO[main]: Connecting to server at <myPublicAddress>:30000
22:07:25: INFO[main]: Client packetcounter (20):
22:07:25: VERBOSE[ConnectionReceive]: con(18/3)con(18/3) Peer 1 sending from different address. Ignoring.
22:07:25: INFO[main]: Client::peerAdded(): peer->id=1
22:07:25: VERBOSE[ConnectionSend]: con(18/3)RE-SENDING timed-out RELIABLE to 83.219.199.81(t/o=0.1): from_peer_id=3, channel=0, seqnum=65501
22:07:25: VERBOSE[ConnectionSend]: con(18/3)RE-SENDING timed-out RELIABLE to 83.219.199.81(t/o=0.1): from_peer_id=3, channel=0, seqnum=65501
22:07:25: VERBOSE[ConnectionSend]: con(18/3)RE-SENDING timed-out RELIABLE to 83.219.199.81(t/o=0.1): from_peer_id=3, channel=0, seqnum=65501
22:07:25: VERBOSE[ConnectionSend]: con(18/3)RE-SENDING timed-out RELIABLE to 83.219.199.81(t/o=0.1): from_peer_id=3, channel=0, seqnum=65501
22:07:25: VERBOSE[ConnectionSend]: con(18/3)RE-SENDING timed-out RELIABLE to 83.219.199.81(t/o=0.1): from_peer_id=3, channel=0, seqnum=65501
22:07:25: VERBOSE[ConnectionReceive]: con(18/3)con(18/3) Peer 1 sending from different address. Ignoring.
these messages repeat forever...
Based on the output above, I'll venture a guess as to what's happening: Since my client is on the same LAN/subnet as the server, the message 'Peer 1 sending from different address. Ignoring.' seems to be indicating that the server is responding, but the client is ignoring it since the server is most certainly responding with it's LAN/subnet IP address (e.g. 192.168.0.11), instead of the address the client is expecting (e.g. <myPublicAddress>), which is the router's public IP address.
If I'm correct on this, then it probably means that the server will work just fine for a client not on my LAN, but it makes it difficult for me to verify that the port forwarding is working correctly.
Can anyone let me know if I'm correct on this and/or offer any suggestions on how to work around it, if possible?