Imspector causes repeated disconnects from AIM?
I had installed Imspector on the pfsense box for my own personal use at home. I noticed that my AIM client kept repeatedly disconnecting from the server. It happened most predictably when I was receiving a relatively large IM from someone, but it would happen other times as well. Today, I got sick of it and figured Imspector might be the culprit in the disconnectivity issues, so I went ahead and removed the package.
(BTW, for anyone reading this with a similar problem, rebooting the pfsense box seems to be necessary before you will be able to successfully connect to any messaging servers again)
An hour has passed and I have yet to experience any further disconnect problems. Would anyone know how to configure imspector not to suck? The IM client I am using is Pidgin 2.2.0, if that makes any difference…
I also had this issue. In my case, it was iChat and, just like you, if I sent a large IM, it immediately disconnected.
I finally disabled IMSpector and the problem stopped completely…
The IMSpector website says that version .4 should be out by the end of June, but it is no where to be seen, so perhaps the author has been delayed, or it's just not ready for prime time yet.
Development has stopped somewhat. I have the patches that were going into 0.4. I'm working out the final stages of packaging. These patches solve the large IM disconnect issue.
I've updated the package. Reinstall the package via the webgui and let me know how it works for you.
Cry Havok last edited by
Any chance of bumping the version number so we know we've got the "good" one?
I had thought about it, but I didn't want to cause confusion over there being a new official imspector version. Not to mention the numerous files that needed be to changed. The binary is built off 0.3 with a patch applied using the freebsd port system. If the disconnect issue wasn't affecting you then there is no need to update. Otherwise simply clicking the reinstall button in the webgui -> package manager will bring you up to date. You can run this command and verify the md5sums if you want to make sure.
MD5 (/usr/local/lib/imspector/badwordscontentplugin.so) = ba91a4fdb7ac9c76aa4c02c2ab908aac
MD5 (/usr/local/lib/imspector/debugloggingplugin.so) = 2a40139faaf2f28a128c08533f44d543
MD5 (/usr/local/lib/imspector/fileloggingplugin.so) = 7f6feb4d4dbe71cb5991de2ea293e4fa
MD5 (/usr/local/lib/imspector/icqprotocolplugin.so) = 29a0cc87dffe349aa96a27b2bcba3083
MD5 (/usr/local/lib/imspector/ircprotocolplugin.so) = b9d2dd5faa089bf02c91e8bdf980e214
MD5 (/usr/local/lib/imspector/msnprotocolplugin.so) = 8b404e526694b12d3d7a87ec54a134ba
MD5 (/usr/local/lib/imspector/mysqlloggingplugin.so) = fa5966562bb462c73aa9ba254baff7a5
MD5 (/usr/local/lib/imspector/yahooprotocolplugin.so) = b5ba67bd6b7f98180fd21f6e62a44135
For me its not working trying to log in with MSN messenger, I even done a fresh install of pfsense since I had an issue with Snort too, another thing I noticed when I enabled it was that it complained about something like mysqlclient.so or similar not installed (I normally use it with sql logging enabled) so I installed the package from your site manually, it didnt complain about the sql after that but it still gave me the same errors
Oct 1 08:20:55 imspector: Connect socket, connect() failed to 126.96.36.199:1863 ```. Yahoo works fine as far as I can tell, the only other protocol that my clients have issues with is AOL, though personally I have not tested AOL/ICQ chat. Fresh install using 1.2-RC2 ISO built on Sun Sep 30 19:44:27 EDT 2007 Slam
Cry Havok last edited by
I had thought about it, but I didn't want to cause confusion over there being a new official imspector version. Not to mention the numerous files that needed be to changed. The binary is built off 0.3 with a patch applied using the freebsd port system.
How about tagging it as 0.3_1, or something similar? If nothing else it ensures that if/when people report bugs in 0.3 you know which 0.3 :)
I have imspector loaded up on my pfSense box. I can connect fine with aim and msn. I sent a message through aim with the max msg length and it didn't crash. I enabled mysql logging and it works as well.
I will tag it 0.3.1. If your having issues you must upgrade to that version before I can help you.
Hi. Sorry to report back so delayed.
I am no longer seeing symptoms of a problem. You have my appreciation.
Do you gonna update this to 0.4
I think it solve many problem for us users that want to log MSN.
I plan to update it to 0.4. I've just been really busy lately. Plus the site mentions that the logging format was changing, which would mean I need to update the log viewer.
Well I hope you get time to do this.
You are doing a good job and have great knowledge.