Invalid TCP flags from bnet??

[d2fcukit]

Anyone have any idea if bnet sends invalid tcp flags or not or what the hell does invalid tcp flags means? Coz heres wat happened to me:

1. I was playing d2 with no maphack or hacks turned on and was frequently interrupted by the "your connection was interrupted" but had not "realm down" yet.

2. I felt strange so press "alt + tab" to the windows screen

3. I saw that my firewall (norton) always alarmed me when i was "your connection was interrupted".

4. It said an IP of 6x.xxx.xxx.xxx was send this invalid tcp flags (wtf). And it was always a range of 6x.xxx.xxx.zzz to 6x.xxx.xxx.yyy doing that to me.

5. I used the firewall and scanned the ip from where it came from and it was somewhere in the US.

6. I blocked the ip range of 6x.xxx.xxx.zzz to 6x.xxx.xxx.yyy

7. Then reconnected the internet and started d2 again.

8. Couldn't connect to fastest server of bnet. (wtf)

9. Removed the blocked ip range of the firewall.

10. Then reconnected the internet and started d2 again.

11. Could finally connect but still those invalid tcp flags still appear occasionally

My conclusion: bnet is sending those to me, if so, why??

PS: Sometimes when i get interrupted, my character dies with exp lost and i'm sure i couldnt have a chance to die, it pisses me off.

 

[ÖChAoTiCÖ]

u should call bnet up or email them about that, but i bet its the AT&T server, proably nothing to do with The code of bnet itself

 

[Placebo]

It may be just an incomplete portation of the code to your client.

Remember Blizzard didn't code the actually d2 battle.net client correctly.