Released IMSpector 0.7, pfsense build is needed
-
Hey Bill,
I e-mailed the author of imspector for you regarding this issue, see below his feedback :
We have been using your imspector application and we are very happy with it!!
The only main problem we are having now is that microsoft recently released a new version of msn which is causing a horrible amount of groupchat logs.
See screenshot : (see above for screenshot)
Any idea's if this can be fixed somehow? I expect most people to start upgrading there msn versions soon..
_Good news: this is fixed in CVS. You can get a tarball from the daily snapshot directory:
http://www.imspector.org/downloads/snapshots/
Give the latest checkout a go._
I guess they fixed this issue in the latest snapshot?Is this something you can include in the package Bill?MSN is used mainly in the netherlands, other protocols and chat programs are barely used here, so I would love to get this working properly with the latest msn version. Thanks in advance for your efforts!
Thanks for the legwork, I'll see what I can do today…hopefully I don't need to do too much more to the port to make it work, I'd like to get to the other features. :)
--Bill
-
-
Can anyone confirm if the previous pfs version (0.4?) is experiencing problems? I had no problems what so ever until I updated the package to 0.8-0.
And these problems are….?
Have you looked at the screenshots posted…...?
Are you referring to AudiAddicts screenshots? I don't see any from you.
–Bill
-
Can anyone confirm if the previous pfs version (0.4?) is experiencing problems? I had no problems what so ever until I updated the package to 0.8-0.
And these problems are….?
Have you looked at the screenshots posted…...?
Are you referring to AudiAddicts screenshots? I don't see any from you.
–Bill
Yes I was. But I'll try to attach 2 pics using the attach feature here.
-
Most of this should be solved in the latest update/snapshot from Imspector Otto.
Now we wait for bill, hopefully he will be able to update the pfsense imspector package with the latest update from the imspector website.
No rush btw bill, I'm glad your willing to take some time to fix this!
-
Have you looked at the screenshots posted…...?
Yes I have but since you were referring to a problem that you didnt specify (=you didnt post the shots) and to an problem that was discussed in this very topic only couple posts before (and with an solution/answer from Bill) I tought you had something else.
Most of this should be solved in the latest update/snapshot from Imspector Otto.
Now we wait for bill, hopefully he will be able to update the pfsense imspector package with the latest update from the imspector website.
No rush btw bill, I'm glad your willing to take some time to fix this!
You mean old logs will be parsed properly in the new snapshots? Because like discussed on the previous page the problem doesnt occur on new material.
-
Have you looked at the screenshots posted…...?
Yes I have but since you were referring to a problem that you didnt specify (=you didnt post the shots) and to an problem that was discussed in this very topic only couple posts before (and with an solution/answer from Bill) I tought you had something else.
Most of this should be solved in the latest update/snapshot from Imspector Otto.
Now we wait for bill, hopefully he will be able to update the pfsense imspector package with the latest update from the imspector website.
No rush btw bill, I'm glad your willing to take some time to fix this!
You mean old logs will be parsed properly in the new snapshots? Because like discussed on the previous page the problem doesnt occur on new material.
-
Have you looked at the screenshots posted…...?
Yes I have but since you were referring to a problem that you didnt specify (=you didnt post the shots) and to an problem that was discussed in this very topic only couple posts before (and with an solution/answer from Bill) I tought you had something else.
Most of this should be solved in the latest update/snapshot from Imspector Otto.
Now we wait for bill, hopefully he will be able to update the pfsense imspector package with the latest update from the imspector website.
No rush btw bill, I'm glad your willing to take some time to fix this!
You mean old logs will be parsed properly in the new snapshots? Because like discussed on the previous page the problem doesnt occur on new material.
Audi refers to the MSN issues. The parsing of old logs is going to take some more work, the regexp that matches the new logs (needed so you don't have stray commas in them), fails to properly match the old logs. Now that I've seen the output, I'm going to see what I can do to match them both.
Here's what I'm working on in order:
Post a minor update tonight that fixes the MySQL logging
Update the IMSpector binary to the latest snapshot to fix MSN (the commit log says the code was untested, so who knows)
Fix parsing of old logs if possible (if not, just go to the shell and read the logs yourself, sheesh), new logs are FINE
Split package up into three (MySQL, PostgreSQL, and plain text logging) as I have zero desire to install 50M of MySQL crap I don't need and won't use
Add new protocols and options that came with updated IMSpector (this includes message injection)–Bill
-
Keep up the great work bill, I have imspector turned off right now, because the current used msn versions in our network seem to spam "groupchat" logs like crazy, thus causing the webinterface to be a complete mess.
I'm hoping the new update will fix this issue, do you have any idea's if you will be able to include the update/fix before the end of feb?
Btw, Mysql was working for me on the older version which(before you did the updates) (0,4?). It decided to not use it anymore, I don't want to keep this kind data logged for too long.
I just want to verify which users use msn and talk to them about it if needed. (msn or chat software may not be used in our network)
-
Starting a new topic to track updates to this package - locking this one.
–Bill