ok, thanx for your log, i’ll give it to our network dev for analize.
ok. we’v analized the logs and that give us nothing.
But we’v added in upcoming version even more verbosibility around the session init stage
So please, wait untill the next version and repost the logs (with the /netlog 2 command enabled)
Ok.
Maybe another logfile could help more?
Could you enclose the problem? Could it be my provider? Or its IP-range or something like this?
A friend who uses linux as well did not have the problem.
Also I changed between ubuntu 14.04, 14.10 and debian 8 and the problem is still there.
here are the logs 1.0.16
% ping 91.230.61.14 15-02-20 - 20:27:18
PING 91.230.61.14 (91.230.61.14) 56(84) bytes of data.
64 bytes from 91.230.61.14: icmp_seq=1 ttl=121 time=50.2 ms
64 bytes from 91.230.61.14: icmp_seq=2 ttl=120 time=49.9 ms
64 bytes from 91.230.61.14: icmp_seq=3 ttl=120 time=58.7 ms
64 bytes from 91.230.61.14: icmp_seq=4 ttl=120 time=57.0 ms
64 bytes from 91.230.61.14: icmp_seq=5 ttl=120 time=55.9 ms
^C
--- 91.230.61.14 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 49.933/54.375/58.750/3.624 ms
# traceroute -n -I 91.230.61.14 15-02-20 - 20:29:28
traceroute to 91.230.61.14 (91.230.61.14), 30 hops max, 60 byte packets
1 192.168.0.1 0.418 ms 0.678 ms 0.937 ms
2 83.169.183.94 13.513 ms 14.891 ms 15.360 ms
3 88.134.234.65 12.069 ms 12.200 ms 12.219 ms
4 88.134.237.5 23.125 ms 28.550 ms *
5 * * *
6 * * *
7 81.91.177.66 54.583 ms 47.329 ms 52.387 ms
8 81.91.186.66 53.541 ms 52.240 ms 50.937 ms
9 91.230.61.14 50.706 ms 58.161 ms 52.779 ms
[game.log](< base_url >/applications/core/interface/file/attachment.php?id=8774)
[game.net.log](< base_url >/applications/core/interface/file/attachment.php?id=8775)
Ok, at first - its not a game code issue for sure.
The issue may be in:
- External library/function that behaves in such strange way.
- System sockets error / config (no chance to fix that one from our side)
To define wich one is your case, we gonna add some more debugging but in the next patch (on 5th of march)
p.s.: The common clue is that all of the missing packets are larger than your MTU value
I used several linux distros and had allways the same error. I will wait for the next patch and maybe I find something which let me set the MTU in my router or something. Or I could ask my provider for help.
Thanks for the help
Edit: Finally I know were the problem come from thank you 
Ok I think I found the problem. The problem was the router/modem of my provider. I set it up to bridgemode and put my own router on and it worked. Thanks for hint with the MTU After googling it with the name of my provider I had several discussions that it is a problem which could be solved if I set up the modem to bridgemode.