Probleme nat modéré sur black ops 4 PC

Bonjour,

J'essaye de jouer a black ops 4 sur pc mais rien n'y fait mon nat restait tjs en strict.
J'ai donc décidé d'utiliser frozenway, ajouter dans les ports le 3074 en udp comme demandé par le jeu et une fois ca fait le jeu passe en modéré mais jamais en natouvert comme a pu le faire la personne sur ce post :
http://www.frozendo.com/forum/discussion/2725/resolu-nat-modere-strict-4g-black-ops-iiii

Pour information je suis actuellement en afrique du sud pr le boulot sur un routeur qui utilise une puce 4G

Voici mon journal de connexion

FrozenWay version 1.6.7
----------------------------------
Server: premium-01-fr-04
Protocol: OpenVPN
----------------------------------
C:/Program Files/FrozenWay/openvpn.exe --client --dev tun --dev-node {72F66A66-C087-493A-8565-11E52BE39FF3} --proto tcp-client --remote 178.33.23.183 443 --management 127.0.0.1 49848 --management-client --management-query-passwords --ca C:/Program Files/FrozenWay/ca.crt --remote-cert-tls server --reneg-sec 0 --auth-user-pass --auth-nocache --compress --resolv-retry 0 --ping 10 --ping-exit 30 --persist-tun --persist-key --persist-local-ip --connect-retry 1 --ip-win32 dynamic --verb 3
Mon Nov 12 05:24:48 2018 WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure

Mon Nov 12 05:24:48 2018 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZ4] [AEAD] built on Sep 24 2018
Mon Nov 12 05:24:48 2018 Windows version 6.2 (Windows 8 or greater) 64bit
Mon Nov 12 05:24:48 2018 library versions: OpenSSL 1.0.2o 27 Mar 2018

Mon Nov 12 05:24:48 2018 MANAGEMENT: Connected to management server at [AF_INET]127.0.0.1:49848

Mon Nov 12 05:24:48 2018 MANAGEMENT: CMD 'username "Auth" sajo'

Mon Nov 12 05:24:48 2018 MANAGEMENT: CMD 'password [...]'

Mon Nov 12 05:24:49 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]178.33.23.183:443

Mon Nov 12 05:24:49 2018 Socket Buffers: R=[65536->65536] S=[65536->65536]
Mon Nov 12 05:24:49 2018 Attempting to establish TCP connection with [AF_INET]178.33.23.183:443 [nonblock]

Mon Nov 12 05:24:50 2018 TCP connection established with [AF_INET]178.33.23.183:443
Mon Nov 12 05:24:50 2018 TCP_CLIENT link local: (not bound)
Mon Nov 12 05:24:50 2018 TCP_CLIENT link remote: [AF_INET]178.33.23.183:443

Mon Nov 12 05:24:50 2018 TLS: Initial packet from [AF_INET]178.33.23.183:443, sid=cc4bda00 235e6930

Mon Nov 12 05:24:50 2018 VERIFY OK: depth=1, C=FR, ST=PACA, L=Sorgues, O=Frozendo SARL, OU=FrozenWay, CN=FrozenWay OpenVPN CA, name=FrozenWay OpenVPN CA, emailAddress=contact@frozendo.com

Mon Nov 12 05:24:50 2018 VERIFY KU OK
Mon Nov 12 05:24:50 2018 Validating certificate extended key usage
Mon Nov 12 05:24:50 2018 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Mon Nov 12 05:24:50 2018 VERIFY EKU OK
Mon Nov 12 05:24:50 2018 VERIFY OK: depth=0, C=FR, ST=PACA, L=Sorgues, O=Frozendo SARL, OU=FrozenWay, CN=server, name=server, emailAddress=contact@frozendo.com

Mon Nov 12 05:24:51 2018 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1544', remote='link-mtu 1543'
Mon Nov 12 05:24:51 2018 WARNING: 'comp-lzo' is present in local config but missing in remote config, local='comp-lzo'

Mon Nov 12 05:24:51 2018 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Mon Nov 12 05:24:51 2018 [server] Peer Connection Initiated with [AF_INET]178.33.23.183:443

Mon Nov 12 05:24:52 2018 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)

Mon Nov 12 05:24:52 2018 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.51.4.1,dhcp-option WINS 10.51.4.1,route-gateway 10.51.4.1,topology subnet,socket-flags TCP_NODELAY,compress lz4-v2,ifconfig 10.51.4.73 255.255.255.0,peer-id 0,cipher AES-256-GCM'

Mon Nov 12 05:24:52 2018 OPTIONS IMPORT: compression parms modified
Mon Nov 12 05:24:52 2018 OPTIONS IMPORT: --socket-flags option modified
Mon Nov 12 05:24:52 2018 Socket flags: TCP_NODELAY=1 succeeded
Mon Nov 12 05:24:52 2018 OPTIONS IMPORT: --ifconfig/up options modified
Mon Nov 12 05:24:52 2018 OPTIONS IMPORT: route-related options modified
Mon Nov 12 05:24:52 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Mon Nov 12 05:24:52 2018 OPTIONS IMPORT: peer-id set
Mon Nov 12 05:24:52 2018 OPTIONS IMPORT: adjusting link_mtu to 1627
Mon Nov 12 05:24:52 2018 OPTIONS IMPORT: data channel crypto options modified
Mon Nov 12 05:24:52 2018 Data Channel: using negotiated cipher 'AES-256-GCM'
Mon Nov 12 05:24:52 2018 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Nov 12 05:24:52 2018 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Nov 12 05:24:52 2018 interactive service msg_channel=0
Mon Nov 12 05:24:52 2018 open_tun
Mon Nov 12 05:24:52 2018 TAP-WIN32 device [FrozenWay] opened: \\.\Global\{72F66A66-C087-493A-8565-11E52BE39FF3}.tap
Mon Nov 12 05:24:52 2018 TAP-Windows Driver Version 9.22

Mon Nov 12 05:24:52 2018 Set TAP-Windows TUN subnet mode network/local/netmask = 10.51.4.0/10.51.4.73/255.255.255.0 [SUCCEEDED]
Mon Nov 12 05:24:52 2018 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.51.4.73/255.255.255.0 on interface {72F66A66-C087-493A-8565-11E52BE39FF3} [DHCP-serv: 10.51.4.254, lease-time: 31536000]

Mon Nov 12 05:24:52 2018 Successful ARP Flush on interface [16] {72F66A66-C087-493A-8565-11E52BE39FF3}

Mon Nov 12 05:24:52 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0

Mon Nov 12 05:24:57 2018 TEST ROUTES: 0/0 succeeded len=0 ret=1 a=0 u/d=up
Mon Nov 12 05:24:57 2018 Initialization Sequence Completed

IPv4 routing table :
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 50
0.0.0.0 128.0.0.0 10.51.4.1 10.51.4.73 25
10.51.4.0 255.255.255.0 10.51.4.73 10.51.4.73 281
10.51.4.73 255.255.255.255 10.51.4.73 10.51.4.73 281
10.51.4.255 255.255.255.255 10.51.4.73 10.51.4.73 281
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 331
127.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1 331
127.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 331
128.0.0.0 128.0.0.0 10.51.4.1 10.51.4.73 25
178.33.23.183 255.255.255.255 192.168.1.1 192.168.1.101 50
192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 306
192.168.1.101 255.255.255.255 192.168.1.101 192.168.1.101 306
192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101 306
224.0.0.0 240.0.0.0 127.0.0.1 127.0.0.1 331
224.0.0.0 240.0.0.0 10.51.4.73 10.51.4.73 281
224.0.0.0 240.0.0.0 192.168.1.101 192.168.1.101 306
255.255.255.255 255.255.255.255 127.0.0.1 127.0.0.1 331
255.255.255.255 255.255.255.255 10.51.4.73 10.51.4.73 281
255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101 306

Si vous avez une idée pour resoudre le probleme je suis preneur

Mercid d'avance