I have done a few mods for SEQ, none added to a diff, mainly because I am such a novice that IF i were to do it, and knowing how people here act to "idiots" I would have been slammed from one side of the moon to earth and back.
Besides the point.
I have a trace function I have put into SEQ that trys to check packets attached to outbound data.
I get it from SEQ.
INVALID PACKET: Bad CRC32 [192.168.1.7:1418 -> 64.126.90.137:3823] seq 0000 len 2 crc32 (5a614100 != 83a68812)
INVALID PACKET: Bad CRC32 [192.168.1.7:1418 -> 65.35.119.250:2930] seq 0000 len 2 crc32 (5a614100 != 83a68812)
INVALID PACKET: Bad CRC32 [192.168.1.7:1418 -> 24.218.34.117:1214] seq 0000 len 2 crc32 (5a614100 != 83a68812)
INVALID PACKET: Bad CRC32 [192.168.1.7:1418 -> 24.213.30.149:4729] seq 0000 len 2 crc32 (5a614100 != 83a68812)
INVALID PACKET: Bad CRC32 [192.168.1.7:1418 -> 24.247.250.161:2984] seq 0000 len 2 crc32 (5a614100 != 83a68812)
INVALID PACKET: Bad CRC32 [64.126.90.137:3823 -> 192.168.1.7:1418] seq 0000 len 3 crc32 (5a614100 != 1f6ac2ad)
INVALID PACKET: Bad CRC32 [24.218.34.117:1214 -> 192.168.1.7:1418] seq 0000 len 7 crc32 (0ca6001e != 4102615c)
Then Isolate the possibles, and block the IP's from recieving information .. HOWEVER.. My question is,
WTF is SEQ doing sending packets to those IP's?
(Edited
Using "Sniffit" I managed to gather some packets and now trying to decrypt the packets.
My goal is to secure SEQ from sending information to anyone. I have a firewall setup, I have a blocking code in my router. But I still would like to know what/who the EQ Game PC is talking to and why.
Reply With Quote