Outpost 3.0.543.5722 (431) released

I have still to upgrade Outpost but am still not sure about the new version when I have 2.7 running stable (I hope) GUI open/close works for me with the memory usage.
I know this involves a full uninstall and then install witha registry clean to make sure

Are things like MS antispy still needed of running OPv3 given its new AS features?

Previous versions had little fixes shortly after the release which has made me stop and think before a new install.

 

People who have slowing problems with outpost 3.0, Agnitum support has partially answered my questions. They want me to do following instructions. Others who have problem with outpost may do the same.
Regards
here is the answer from Agnitum support team.

Thank you for e-mail.

Please follow the instruction:

1. Download Debug plug-in from
http://www.agnitum.com/download/support/OutpostDebugInstall.exe
install it and reboot your PC.
2. Reproduce the problem.
3. Immediately after the problem is reproduced:
Right click on Outpost system tray icon and select "Save & archive
logs" item in menu.
4. Right click on Outpost system tray icon and select "Explore logs
folder" item in menu.
5. Send us logs.zip file
6. Send us your configuration files (for example configuration1.cfg and
configuration1.conf files) which are located in Outpost install folder).

PLEASE save log files immediately after the problem is reproduced,
otherwise they will be out of date.

Best regards,
Ksenia,
Agnitum Support Team
www.agnitum.com/support/

 

Any news regarding the browsing slowdown issue? I still have it with v3.0.

 

Stiil waiting an answer from Agnitum Support

 

Any news regarding Agnitum Support slowdown issue?

 

How many "slow" subjected topic are there in Agnitum support forum?
500
We should be patient, they will surely send an answer. I believe so...

 

You might want to read this........
http://outpostfirewall.com/forum/showthread.php?t=15061

I have been installing 'over the top' for the past three updates of OP.....no problems at all........i did a clean install, but not a super clean install......i only went into the Task Manager and closed what i could { very important to close security programs-------don't forget PG and whatever you might have that is similiar } follow the on screen instructions and you should have it..............some install this way and some don't............you decide..........also there seems to be a bug or two from postings here...........
i can tell you that i am very happy with the new version and have had no problems at all .......http://users.pandora.be/eforum/emoticons4u/happy/1074.gif

Cheers

 

Yes, I saw
http://outpostfirewall.com/forum/showthread.php?t=14897
http://outpostfirewall.com/forum/showthread.php?t=14615
http://outpostfirewall.com/forum/showthread.php?t=13619
http://outpostfirewall.com/forum/showthread.php?t=13461

It's a joke only. Don't misunderstand me. please.
I'm sure that you are a loyal user of agnitum since 2004.

I think that outpost has a little web browsing slowdown issue, isn't it?

Regards.

 

Errrrr......didn't i say the NEW VERSION.....

 

I noticed some slowing and a lot of timeouts when I made the intial upgrade. I edited my registry to reenable gzip since the compression has a nice effect on my limited bandwidth. I also noticed I was getting a lot of timeouts for DNS lookups so I also changed the other setting like it was when things were working smooth.
For any gaming I would suggest disabling realtime anti-spyware since I appeared to have problems with gamedata throughput.
HKLM\software\agnitum\outpost firewall\EnableGzipEncoding=1
HKLM\software\agnitum\outpost firewall\FixServerErrorsinSend=1

 

Please someone confirm that with these edits, outpost is once again fast! Thanks FirePost!

 

I tried these registry settings and the slowdowns have gone!!! Thanks a lot!

 

It appears that any hangups or slowness is gone. Thanks

 

Your registry hacks did the trick. Smooth and fast surfing has returned. Kudos to you!

 

This should be made sticky both here and the outpost forum!

 

Well there are downsides to those settings - if Gzip compression is enabled, the Active Content and Ad filters will not be able to function properly since they will be seeing compressed data. It has been mentioned on the Outpost forum a couple of times but in most cases slowdowns are due to CPU activity which is addressed in the Resolving High CPU Utilisation Issues with Outpost FAQ.

 

I have read your post over there Panaroid. I had no CPU Utilisation issues, just plain slow browsing! And i have till now not noticed anything get by the ad filtering and active content filtering plugins even after enabling Gzip compression. I had to search a LOT to find these settings in the outpost forum! So at least for me (and some others), this setting did the trick!

 

As Paranoid2000 pointed out enabling gzip encoding can allow some things to go past the ad filters but the bandwidth boost is well worth it at least for dialup.
The FixServerErrorsinSend setting is an old one. It may be you can just re-enable that setting and have things work the same as older versions for you. The Gzip setting has always been off, fixservererrors has always been on. Since I always turn gzip back on, I noticed the fixerrors had been turned off also. Someone may wish to try it with only the fixerrors setting

 

Nope! Just tried it. As soon as you turn off GZip encoding, the slowdowns are back again!

 

Thanks for trying that out kalpik.

 

You are most welcome! And once again, thanks for those registry settings!

 

Hi guys,

I have a little problem this last days with Outpost 3. It detects an "Ethernet Attack". It is a Ip Spoofing but the IP address is 255.255.255.255. Every time the Outpost detect it, then Outpost block it and I can not surf in the webs.
I am not an experte, obviously, but I think this is not a real attack and I should configure Outpost in a way to avoid this block but I do not know the way.

Please, if someone can help me I would apreciate.

Thanks in advance,

 

Please review Outpost 3.0 - What to expect, specifically Known Issue 3.