because it's nat related? idk
analyzing at this point leads to no results because, well, if you try setting up the ECI instead of the mikrotik and it works - guess what, it's the mikrotik.
how to fix the mikrotik - idk. first try replacing the mikrotik. if this game is worth that.
edit: maybe the bridge mode on the 1312 has a problem with the way mikrotik works.
i'm tired of speculation though since low chance the 1312 is the problem. if it's not the 1312, likely something on the mikrotik.
edit2: i think trial and error is better than speculation. the "what if" and "but it worked!" leads nowhere.
edit3: so i wanted to find out how the UI on the mikrotik looks. i didn't but i found this sort of NAT stuff:
https://wiki.mikrotik.com/wiki/Manual:IP/Services#Service_Portsudplite, and stuff like that, means the mikrotik can have a configuration weakness that plays out with the 1312. because the 1312 is a simple modem. it's so simple i doubt it's the problem.
edit4: so what you need to do now is single out the mikrotik by replacing it with ECI and if the ECI works then the mikrotik needs to be configured differently. if not then the 1312 is indeed the problem.
edit5: alternative. did i mention this? forgot. do this:
Network setting>NAT>ALGApplication-Level Gateway (ALG) allows customized NAT traversal filters to support address and port translation for certain application such as FTP, SIP, or file transfer in IM Applications.
NAT ALG : Enable
Disable (settings are invalid when disabled)
SIP ALG : Enable
DisableRTSP ALG : Enable
Disableif it still doesn't work, then go to DMZ and add the router IP as the ip there. if it still doesn't then put it back to "192.168.1." [disabled]
edit6: security>firewall>DoS
Prevent DoS attack
DoS Protection Blocking : Enable
Disable (settings are invalid when disabled)
edit7: i'm not saying the 1312 isn't the problem. i just need to learn more about it to maybe know what the problem with it is. if there's even a problem..
edit8: maintenance>remote mgmt> ICMP(WAN)>
tick.
edit9: see NAT isn't activated on 1312. it's on mikrotik.
https://forum.kitz.co.uk/index.php?topic=23138.0NAT is what blocks stuff. it could be some routing misconfiguration between the two that the ECI did not have. ]
edit10: did you disable DHCP on the 1312? [disable it]. did the ECI also have 192.168.1.1 255.255.255.0 as address ? are you using just one cable from LAN to WAN? [remove any cables and VLAN interfaces and leave just group "Default" and one cable from 1312's LAN1 to Mikrotik's WAN].
edit11: i wish i could see the mikrotik UI. i can't find anything about it on the internet.
edit12: have you tried using another computer to try titanfall2 on it? i know it sounds stupid, but sometimes it's the computer. i know this from experience.
edit13: ok there's definitely something mysterious going on between the 1312 and Mikrotik. i couldn't find an issue with mikrotik according to what i googled about it so far. i have no idea what the hell is going on.
edit14: do other games work perfectly? especially ones that use UDP like GunZ private server, Rakion-Steam? because if they do it's something NAT related. some games mess with the router even if it's set up without NAT aka PPP-IP. leave out the 1312 because at this point i say it's
sort of the problem but there's nothing wrong with it. Mikrotik NAT must be nuked/changed/fixed and you know what? NAT does the routing too. So it's not the bridge-mode 1312. bridge mode doesn't even do anything except link to the DSL. nothing to do with the internet part.
can you show me everything NAT in Mikrotik's UI? i don't know if the game uses UDP or TCP but it might not matter. sometimes even a TCP game can bug out if the NAT is a Restricted-Cone NAT rather than Full-NAT. an old router used to use that sort of technology. 1312 in router mode just has outbound-inbound type firewall.
and i'm sitting here wondering if i suck or this problem is deep. no one replying except me so i guess it is?