WillKnott
Posts: 48
Joined: 9/13/2010 Status: offline
|
that scenario might make sense if both client and host had different public ips and routers. However, most home users wont have this, they will come from the same public ip, but behind the firewall the host and client will usually exist on the same subnet. Routers and firewalls don't like to route inside addresses, to outside addresses and back inside again. I have spent many years in a datacenter troubleshooting these inside/outside/inside connections and it was always a complicated soulution to work around it never involved one device only by the end of it. The host should send its own local ip to the lobby and the lobby passes this on to the client, who in turn then should try to contact the host's local ip "directly"...Sorry for the poor man's visio, it was best i could do at the time :) I will make attempts to setup a scenario that works. I already use port forwarding to access devices remotely, I will monkey with this some to see if I can get that scenario to even happen. again..capture on client and on host at both ends...no connections attempted to any ip on port 1944 or my public ip. I would see that leaving the clients network port during the 'attempt' whether it was setup on the router or not. If I saw this connection being attempted, I could figure out a way to possibly work this out, however, if the client doesnt even send the connection out to 'try' to connect, no router config will ever make a difference. Seems to me a simple suggestion...provide a box to pass the host's local ip (or desired ip) to the client via the lobby...then the client will know exactly what to attempt, if this fails or if the box is left empty, it can proxy the connection through the lobby as normal. I am cool with using the lobby to help setup the Direct connection, but the point is making the gameplay connection to bypass the internet entirely. if the lobby is looking at the source ip from the packet it recieves, it will be the 'NAT'ed ip that the router translated in this scenario. Client and host will 'appear' to come from the same ip, which in this pic is my router's public ip.
Attachment (1)
< Message edited by WillKnott -- 12/6/2019 7:15:30 AM >
|