31
Mods & Development / Re: Lat Trick Bot
« on: May 15, 2018, 10:13:33 AM »
Hi @iL
A couple things that you said:
1 - Is it a vulnerability to expose IPs?
Well no I dont think it is a problem, you already get everyones IP when you join a game with them, the only difference is now you can get everyones IP without joining a game
2 - Symmetric NAT is rare
I didnt know, I have a pfSense firewall. I will try a new firewall with another type of NAT and see if I can defeat that
3 - Step 5/6 - why do all other players need to respond to UDP?
They don't, I was just imagining a world where no one port forwards anymore and we all host games using the new NAT hosting fix
4 - Will your udp_client.py script work as you said?
No, I dont think so, the problem is that port 6112 isn't going to be opened, 49123 or something like that will be opened publicly and translated to 6112 on the LAN. Your friend will try to join <your-external-ip>:6112 and it will be closed... we have to somehow let PvPGN know to tell other players to join on <your-external-ip>:49123
Possibly this is a Symmetric NAT thing though and maybe your router will rewrite <internal-ip>:6112 -> <external-ip>:6112, in which case I think youd be good
more reading http://www.think-like-a-computer.com/2011/09/16/types-of-nat/
A couple things that you said:
1 - Is it a vulnerability to expose IPs?
Well no I dont think it is a problem, you already get everyones IP when you join a game with them, the only difference is now you can get everyones IP without joining a game
2 - Symmetric NAT is rare
I didnt know, I have a pfSense firewall. I will try a new firewall with another type of NAT and see if I can defeat that
3 - Step 5/6 - why do all other players need to respond to UDP?
They don't, I was just imagining a world where no one port forwards anymore and we all host games using the new NAT hosting fix
4 - Will your udp_client.py script work as you said?
No, I dont think so, the problem is that port 6112 isn't going to be opened, 49123 or something like that will be opened publicly and translated to 6112 on the LAN. Your friend will try to join <your-external-ip>:6112 and it will be closed... we have to somehow let PvPGN know to tell other players to join on <your-external-ip>:49123
Possibly this is a Symmetric NAT thing though and maybe your router will rewrite <internal-ip>:6112 -> <external-ip>:6112, in which case I think youd be good
more reading http://www.think-like-a-computer.com/2011/09/16/types-of-nat/