Suggestion about logs

[Nyebodnye]

OK, so I get a balloon up about some IP that was blocked, go into the logs

and it's from a Moldova IP address.

WHICH PORT ?

Is this just a rogue torrent leecher trying when I've shut down ?

Is it a spammer ? Real hacker sweeping ports on an IP range ?

I don't know.

How about putting the port in as well instead of just the IP address ?

(Like peerblock does)

Thanks

[exile360]

Here's an example entry from my protection log. I'm running Windows 7:

19:22:30 Exile 7 x64 IP-BLOCK 77.222.56.35 (Type: outgoing, Port: 50327, Process: avp.exe)

[Nyebodnye]

Do I need Windows 7 for that ?

All I get on XP is

21:47:36 Nyebodnye IP-BLOCK 89.28.94.180 (Type: incoming)

22:01:56 Nyebodnye IP-BLOCK 77.78.224.103 (Type: incoming)

Apparently I'm on 1.51.1.800

[Nyebodnye]

oops 1.51.1.1800

[exile360]

Yes, unfortunately XP and 2000 do not support the API's that we are able to use in Vista/7, which enable much more detail in the logs. You can use a program like TCPView to track down the details of a connection as described in Section G of our FAQ.

[Nyebodnye]

TCPView is kind of real time, so when the connections eventually close,

they're gone and you don't to see them later or get logs.

XP seems to be supported just fine by Peerblock :-)

Must be using older API's that work ;-)

Pity I can't import your blocklists into Peerblock.

My PC won't run Windows 7 multimonitor - it's one of the old

ones with loads of PCI slots which I need for cards I rely on.

I guess I'll just have to take it at face value then that what was blocked was blocked.

Thanks

[exile360]

Yeah, I believe peerblock uses their own API's to do this, nothing native to the Windows networking stack. That's why they're able to do it on XP and we aren't.