Thanks BBcan177, looks like that was the issue.  Following the fix in the thread you linked fixed it.

It looks like that when I uninstall and reinstall the LCDProc package the custom files I put in the directory get removed and then re-added. Where would those be held so I can delete them to start fresh?

Please search the forum on reverse proxy issue. pfSense wont allow squid to bind to a lower port. You'll have to use a higher port… Then using nat, redirect wan port 443 to that higher port, ex 8443? c-icap and clamd is part of squid proxy, config is under Proxy server - Antivirus.

yep, you are right! Infact, it's need to connect via ssh after installation for changing captive portal source code. Thank you very much for your support. Cheers SM

I have the same problem, a VSAT wan (supposed to be always more than 500ms) and a WIMAX (supposed to be always more than 120ms), after 2.2 upgrade (well, fresh installation) are 20/10/0ms

@Gertjan: Perfect  :) Can you screenshot your WAN interface ? Or, Diagnostics > Backup/Restore -> and show these resulting XML parts here: <interfaces><ppps>(mask out passwords)</ppps></interfaces> I will do so as soon as I get in front of the PC. thank you for the help and direction. great to know that there is a community of people willing to assist when things go a bit pear shaped.

Got my hands on a cable.  Problem solved.

Thanks for input. +1 for dublicating after a "burn in" period. Other argument to do so If booting the other slice means booting an old version, then it just might need the old config (from backup) to be restored at the same time. And if the old slice cannot boot without the old config then one will end up with only one functional slice. conclusion: dublicating slice so there is two identical slices that can use the same config file seems to be the preferred solution.

Are you saying Snort is not working, or are you just fretting about the change in displayed free memory?  If Snort is working, I would say don't worry about the free memory.  There could be several reasons for that not related to Snort.  While Snort is live reloading rules (for example, after a nightly rule update) it will possibly use up to twice as much memory as normal since it temporarily holds two complete copies of the configuration in memory (including rules).  It then switches the running Snort process over to use the newly built second in-memory configuration and then destroys the old configuration.  That will account for some of the memory decrease. Bill

thanks for your reply

Acording to this it seems OK. But, ill try to do some fiddling with settings. Thanks for pointing it out for me. http://vip.asus.com/forum/view.aspx?board_id=1&model=P5GC-MX&id=20110715191107398&page=1&SLanguage=en-us

Benefit of others?  So other people with layer 8 issues like yours?  So no errors in the log, showing your config would be a simple screenshot taking 2 seconds..  But your helping others by telling them hey if dns doesn't work exactly how you think it should work go back to 2.1.5??  Yeah that is going to help thousands I think :rolleyes:

And knowing your IPs is equally useful (-;

Thanks, that gave me an excuse to move to the 64 bit install. Everything went smoothly and populated /etc/rc.d appropriately. arri

It work!  :) Thank you!

Am also facing same issue after upgrading to 2.2 from 2.1.5. event_wait interrupted system call (code=4) Please help guys..