[Server] - Man in the middle attack
When a server is hosted on a secondary IP and a client tries to connect an error pops up that says.
'Potential man in the middle attack detected. Your client claims it connected to: xxx.xxx.xxx.xxx, but the server does not consider this reasonable.'
Any ideas what might cause this?
PS. Primary IP's work fine.
'Potential man in the middle attack detected. Your client claims it connected to: xxx.xxx.xxx.xxx, but the server does not consider this reasonable.'
Any ideas what might cause this?
PS. Primary IP's work fine.
Comments
$IPv4::InetAddress = $Host::BindAddress;
If you pop this into any file that loads before our scripts are run (maybe create a new .cs file to pop in autoexec if you run multiple configs) it should be fine assuming it's set to the IP the clients see.
I'm asleep at the moment myself, but in the morning I can open the script on our end and check it out.
Edit: I've updated the installer with something that should fix this particular problem (as well as an uninstaller, but that's unrelated). If you don't want to download the whole thing, you could just replace your existing T2csri.vl2 with this: http://www.tribesnext.com/krash/T2csri.vl2
Thanks!
Is this file available anywhere?
I am getting the error listed above.
Are you connecting to a local server? If so, what address are you attempting to connect to?
I am trying to set up a server on my other computer and it seems to be working but when I try and join I get the man in the middle error.
The server is called "Boot" in the server list.
I also tried adding that bit of code in the VL2 but when I zipped it back up the file was half the size which was weird. Anyway it seemed to work and I could join but I would drop after a few minutes.
I tried applying the patch again but it didn't fix the problem.
If you use non-standard addresses for your LAN and want to connect yourself using your internal address, you might need to add the format to the IP check. However, if you're trying to connect to your server's bound WAN address, it should automatically allow the connection if the bind preference is correctly set.
If you're able to connect and are dropped after minutes, it's not caused by this issue, as the check occurs only when joining. A common cause of delayed disconnections is the $Host::CRCTextures preference, which will disconnect any players running custom skins. I would make sure it is set to $Host::CRCTextures = 0; in your serverprefs.
I am new to this so am trying to figure it out.
My server seems to reset itself pretty often which is why I was getting disconnected.