been trying out LnS here for a few days, but obviously I've got something configured wrong. This is from my Jammer1.95 log (whatever it is is going straight through LnS and getting stopped by Jammer: Jammer v.1.95 build 0820 (Registered to Steven Yevchak) Back Orifice and NetBus protection. Copyright (C) 1998-2001 Agnitum Ltd. All rights reserved. Adapter name: XXXXXX Current network address: XX-XX-XX-XX-XX-XX Starting network monitoring Allocated 99072 bytes for buffer ------------------------------------------------------------------------- Type of attack: Possible TCP port scanning Time: The time is Thu Feb 21 12:14:20 2002 [Local GMT bias -5:00] Source IP: 200.77.0.156 () Ports: 1075->1214 ------------------------------------------------------------------------- Type of attack: Possible TCP port scanning Time: The time is Thu Feb 21 12:44:57 2002 [Local GMT bias -5:00] Source IP: 200.77.0.156 () Ports: 1198->1214 ------------------------------------------------------------------------- Type of attack: Possible TCP port scanning Time: The time is Thu Feb 21 13:15:17 2002 [Local GMT bias -5:00] Source IP: 200.77.0.156 () Ports: 1321->1214 ------------------------------------------------------------------------- Type of attack: Possible TCP port scanning Time: The time is Thu Feb 21 13:44:33 2002 [Local GMT bias -5:00] Source IP: 200.77.0.156 () Ports: 1428->1214 ------------------------------------------------------------------------- Type of attack: Possible TCP port scanning Time: The time is Thu Feb 21 13:56:01 2002 [Local GMT bias -5:00] Source IP: 200.77.0.156 () Ports: 1451->1214 ------------------------------------------------------------------------- Type of attack: Possible TCP port scanning Time: The time is Thu Feb 21 14:26:50 2002 [Local GMT bias -5:00] Source IP: 200.77.0.156 () Ports: 1638->1214 As you can see, they're all from the exact same place (Mexico somewhere). I'm not concerned, because they're getting stopped - I just need to know what I'm doing wrong with LnS? (Nothing in LnS log about these). Anyone? Pete
Hi Pete, first go to to welcome screen and see if received packets are recorded. ou should also show as connected with your i.p. showing. Second, go to options screen and make sure you selected the proper adapter for your connection.
Yes and yes. I've got a log full of stuff here in LnS, it's just that none of it pertains to those alerts from Jammer. Pete
The answer might just be at the download page for jammer : "Important Notes Jammer is not compatible with Outpost. We strongly recommend that you uninstall all other firewalls before installing Jammer. Running Jammer along with any other firewall software will very likely result in system instability (i.e. crashes) and almost certainly will result in Jammer operating in an insecure fashion."
Whatever the problem was, upgrading to 2.03 Beta 02 seems to have solved it. It's still puzzling, though. I rotate through firewalls pretty frequently, so as to have at least a bare knowledge of most of them. When using TPF, ZA (free) or SPF nothing ever got through them to where Jammer 1.95 had to pick up the slack. With the Beta 02 version of LnS, I can make this problem repeat simply by switching back and forth from the standard ruleset to the Enhanced ruleset (the standard ruleset is what's failing - and it's obviously not something i changed, because re-loading the standard ruleset brings them all back in their default setting, correct? Pete
