03 Sep 13, 08:52AM
(03 Sep 13, 05:12AM)RPG Wrote: Seems that I told you that this IP doesn't mean anything. My ISP shares dynamically allocated IP. It changes every time.You posted on 31 August @ 05:56 UTC with IP 128.69.156.211. The MS log shows that IP being banned at 05:55 UTC on that day. Do you expect me to believe that this is a different person? That's one super co-incidence.
Quote:...didn't tried to connect using others clients. unarmed? How???If you type "telnet assault.cubers.net 28760" then "list", this is what I see:
[SELECT ALL] Code:
2013-09-03 06:54:20 list sent: x.x.x.x unarmed AC1000
Quote:Some connectinng attempts were successed (where you told me that I'm lied) but most of them were failed.
[SELECT ALL] Code:
2013-09-01 19:29:18 list sent: 176.14.224.114 RPG AC1104
2013-09-01 19:32:49 list sent: 176.14.224.114 RPG AC1104
2013-09-01 19:41:26 list sent: 176.14.224.114 RPG AC1104
2013-09-01 19:58:22 list sent: 176.14.224.114 RPG AC1104
2013-09-01 19:59:33 list sent: 176.14.224.114 RPG AC1104
Quote:Currently I really can login, but when I use some IP's I can't, so that issue may corresponds with following:Let's see how many AC1000 requests I've seen from any of your IP ranges in the last six months:
1) Bug in AC that sends wrong version info first...
[SELECT ALL] Code:
2013-08-31 05:55:06 sban entry: 128.69.156.211 unarmed AC1000
Quote:1.1.04 is VERY glitchy with config home dir!Maybe, if you have no control over your OS, but that's nothing to do with this thread.
Quote:Too wide IP range were banned (but you even didn't told what really IP range you were banned)I don't know what you mean by "Too wide". If you mean that it encompasses any IP that the cheat could get, you'd be right.
[SELECT ALL] Code:
37.144.0.0/15
89.178.0.0/16
93.80.0.0/16
95.24.0.0/14 // 95.25 95.26 95.27
95.28.0.0/16
128.68.0.0/15 // 128.69
128.72.0.0/16
176.14.0.0/16
Quote:I tried to connect to servers and I got this everywhere: "you were banned on this server".When you get banned from the MS, your IP is sent to the servers for 24 hours, hence the "wait 24 hours" warning. The server keeps that ban until it next reports to the MS, which may not be regularly and is beyond my control. This is the one, minor, issue which I would like to see solved.