Quote:
|
Originally Posted by Nimrod
Looks like we need to get Link in here :\ This could be bad if thats why as ApprehendJJ2 was the only way to find there real IP :\
|
ApprehendJJ2 will only display and log specific types of JJ2 packets. Specifically, join requests, server confirmations (sending client ID), and client information. All TCP packets that fit the specifications of one of these types will be detected. As far as is generally known, these packets are necessary to cause problems in a server, however, if there is a new JJ2 exploit that does not use one of these types, ApprehendJJ2 will not display or log it.
ApprehendJJ2 takes the IP address from the IP header, not from the JJ2 packet data. Any IPs displayed or logged are authentic.
The best thing to do is to save the binary log file, and include that with any reports. It contains all packet data, so even if there is a problem with AJJ2 the log can be examined manually. I can't make any conclusion in this case unless I see the log file.
__________________
With our extreme gelatinous apology,
We beg to inform your Imperial Majesty,
Unto whom be dominion and power and glory,
There still remains that strange precipitate
Which has the quality to resist
Our oldest and most trusted catalyst.
It is a substance we cannot cremate
By temperatures known to our Laboratory.
~ E.J. Pratt
|