IMSpector, file?

whitto

Hm.. Strange.
When running in debug mode, I get only this output and nothing happens, even if I chat over MSN:


# imspector -d -c "/usr/local/etc/imspector/imspector.conf"
imspector: Protocol Plugin name: MSN IMSpector protocol plugin
imspector: Listening on 0.0.0.0:16667
imspector: Logging Plugin name: Debug IMSpector logging plugin
imspector: Logging Plugin name: File IMSpector logging plugin

And this is my config file:


# cat imspector.conf
plugin_dir=/usr/local/lib/imspector
msn_protocol=on
file_logging_dir=/var/log/imspector
icq_trace_error=on

I tried yet many other possibilities (turning imspector on for only one network interface, turning all protocols on and off, I tried also fetching and running that script which I found on some other topic (sh-update-imspector.sh) and it did not return any error).

Just for info: imspector is my only package and I have only two nat/firewall rules for entering my pfSense from the web (http and ssh).

Any Idea, what is wrong?
Thanks,
Vito.

rsw686

Just dawned on me. Are you leaving MSN signed on while changing the settings. You need to sign on to MSN again after you start imspector. Otherwise it will not get redirected through imsepctor.

whitto

Hey,

I thought that could be an issue, yes. Now I waited for couple of days, I am now sure that everybody re-logged to msn. But still nothing.
Should I try ICQ or some other IM protocol?

Thanks for help!
Vito.

whitto

I thought there might be another disturbing thing… My personal firewall from zonelabs. I have ZoneAlarm Security Suite installed, which should scan also my IM traffic. But now i turned IM security off and still nothing.

Is my case hopeless?

rsw686

I don't understand what is going on. The founder of SmoothWall wrote the code and it is included in SmoothWall Express. I have worked with him to add many enhancements. He uses MSN exclusively and I have also verified that it works. Have you tried other protocols? I've been running IMSpector for months now. The only thing that comes to mind is you have some firewall / nat rules above that is blocking it from going to IMSpector.

whitto

Thanks for help, I see that it's hopeless case. But I can tell you that I have NO rules (except of two for entering my pfsense from other location). I will try other protocols soon as I arrive home again. Will tell you when I succeed!

Best regards,
Vito.

rsw686

Could you run the following command on the pfSense box. It will show the rules created by IMSpector. I'm wondering if the rules are not being put into place.

pfctl -aimspector -sn

You should get output similiar to

rdr pass on fxp1 inet proto tcp from any to any port = 1863 -> 127.0.0.1 port 16667
rdr pass on fxp1 inet proto tcp from any to any port = aol -> 127.0.0.1 port 16667
rdr pass on fxp1 inet proto tcp from any to any port = mmcc -> 127.0.0.1 port 16667

What version of pfSense are you running? The anchor for pf was added beginning on 1.0.1-SNAPSHOT-11-24-2006. If your running a version older than that you will need to upgrade to get IMSpector to work.

In one way I hope this is the problem as it would explain everything. Hopefully this didn't waste too much of your time. I didn't even think about it since it is mentioned in the package description.

rsw686

If you get it working you should run the below command to update IMSpector. I have added in real time log viewer.

fetch -o - http://wgnrs.dynalias.com:81/pfsense/imspector/sh-update-imspector.sh | sh -

whitto

Me idiot. I am really sorry for "spamming" the forum. Of course, I made it finally. As I wrote on my first post here

…I installed new pfSense (today)...

I did not do anything wrong. But the point is that I downloaded last release which was not "snapshot". I noticed yesterday, that even if I downloaded it on 2007, my version was dating October 2006. And of course updating did not succeed. Today I downloaded latest "iso" snapshot and installed it fresh, installed also imspector package and it is working perfect now.

Once again, many thanks to rsw686 for help!
Vito.

rsw686

Glad you got it working. The forum is here to help people out, I don't mind at all. :)

akula169

I'm using MySQL logging.

Which, with the update you posted, works just fine - I can see the entries in the MySQL database.

However, the entries do not show up in the IMSpector LogViewer in the pfSense interface.

rsw686

@akula169:

I'm using MySQL logging.

Which, with the update you posted, works just fine - I can see the entries in the MySQL database.

However, the entries do not show up in the IMSpector LogViewer in the pfSense interface.

The log viewer only supports file based logs.

simpat1zq

I'm not sure if this should go here or if i need a new thread:

Is the imspector log file supposed to empty out with every reboot? imspector works fine, but after i reboot the log folder is empty. Is there some setting i'm missing?

Also, the word "viwer"(viewer) is misspelled on the log page. I have the build from about 3 days ago, so i'm not sure if it's fixed.

thx.

rsw686

@simpat1zq:

I'm not sure if this should go here or if i need a new thread:

Is the imspector log file supposed to empty out with every reboot? imspector works fine, but after i reboot the log folder is empty. Is there some setting i'm missing?

Also, the word "viwer"(viewer) is misspelled on the log page. I have the build from about 3 days ago, so i'm not sure if it's fixed.

thx.

I fixed the spelling mistake. I never even noticed it. Thanks.

As far as the logs being emptied on reboot it I'll have to look into that.

rsw686

I changed the log directory to /var/imspector for now. Reinstall the package, navigate to the imspector settings page and click change.

If you want to keep your current logs you can stop the package, move the logs from /var/log/imspector to /var/imspector and then do the above.

We're going to look into making a /var/log/persistent directory so the logs will probably get moved to /var/log/persistent/imspector in the future. I will update this thread if/when that occurs.

akula169

@rsw686:

@akula169:

I'm using MySQL logging.

Which, with the update you posted, works just fine - I can see the entries in the MySQL database.

However, the entries do not show up in the IMSpector LogViewer in the pfSense interface.

The log viewer only supports file based logs.

Understood - and it is something that I can live with - I'll just have to make my own PHP log view - no big.

Thanks for package and the prompt reply :)

rsw686

@akula169:

@rsw686:

@akula169:

I'm using MySQL logging.

Which, with the update you posted, works just fine - I can see the entries in the MySQL database.

However, the entries do not show up in the IMSpector LogViewer in the pfSense interface.

The log viewer only supports file based logs.

Understood - and it is something that I can live with - I'll just have to make my own PHP log view - no big.

Thanks for package and the prompt reply :)

You'll need to add mysql support to php. The file log viewer works in almost realtime with ajax. You could probably use the same javascript and just change the php reading the files to sql statements pulling data from mysql. I've been real busy lately and just haven't had much time to work on things. If you get it working it would be great if you would share the code so I can include it in the package.

akula169

@rsw686:

@akula169:

@rsw686:

@akula169:

I'm using MySQL logging.

Which, with the update you posted, works just fine - I can see the entries in the MySQL database.

However, the entries do not show up in the IMSpector LogViewer in the pfSense interface.

The log viewer only supports file based logs.

Understood - and it is something that I can live with - I'll just have to make my own PHP log view - no big.

Thanks for package and the prompt reply :)

You'll need to add mysql support to php. The file log viewer works in almost realtime with ajax. You could probably use the same javascript and just change the php reading the files to sql statements pulling data from mysql. I've been real busy lately and just haven't had much time to work on things. If you get it working it would be great if you would share the code so I can include it in the package.

Oh, I was going to do it all on a the same machine that has the mysql server running

But now that you mention it, I'll take a look at the code that is there. If I get it working, I'll certainly let you know.

simpat1zq

Under services, it lists IMSpector twice for me. Is it doing that for everyone else?