Over time it does increase, but then stops at a certain point. I've gone 60+ days with it running ok. The thing is once you update the rules periodically anyway, Snort has to reload the rules and memory will decrease some anyway.

Some fixes for Captive Portal locking required an extra PHP module which apparently didn't make it into the builds yet. Looks like they were just added in, so perhaps the next snapshot that comes up should have them.

here's the log:

May 19 01:14:14 SnortStartup[46853]: Ram free BEFORE starting Snort: 22M – Ram free AFTER starting Snort: 22M -- Mode lowmem -- Snort memory usage:
May 19 01:13:54 php: : phpDynDNS: (Success) IP Address Changed Successfully! (81.193.71.203)
May 19 01:13:54 php: : phpDynDNS: updating cache file /cf/conf/dyndns.cache: 81.193.71.203
May 19 01:13:54 php: : DynDns: Current Service: dyndns
May 19 01:13:54 php: : DynDns: DynDns _checkStatus() starting.
May 19 01:13:53 php: : DynDns: DynDns _update() starting. Dynamic
May 19 01:13:53 php: : DynDns: DynDns _update() starting.
May 19 01:13:53 php: : DynDns: cacheIP != wan_ip. Updating.
May 19 01:13:53 php: : DynDns: Cached IP: 81.193.103.122
May 19 01:13:53 php: : DynDns: Current WAN IP: 81.193.71.203
May 19 01:13:53 php: : DynDns: _detectChange() starting.
May 19 01:13:53 php: : DynDns: updatedns() starting
May 19 01:13:53 php: : DynDns: Running updatedns()
May 19 01:13:51 check_reload_status: updating dyndns
May 19 01:13:49 check_reload_status: reloading filter
May 19 01:13:49 php: : Configuring slbd
May 19 01:13:49 php: : pfSense package system has detected an ip change 81.193.103.122 -> 81.193.71.203 ... Restarting packages.
May 19 01:13:48 SnortStartup[46556]: Ram free BEFORE starting Snort: 22M – Ram free AFTER starting Snort: 22M -- Mode lowmem -- Snort memory usage:
May 19 01:13:45 SnortStartup[46549]: Ram free BEFORE starting Snort: 22M – Ram free AFTER starting Snort: 22M -- Mode lowmem -- Snort memory usage:
May 19 01:13:21 php: : Resyncing configuration for all packages.
May 19 01:13:19 SnortStartup[46454]: Ram free BEFORE starting Snort: 22M – Ram free AFTER starting Snort: 22M -- Mode lowmem -- Snort memory usage:
May 19 01:12:51 snort[24729]: Snort exiting
May 19 01:12:51 snort[24729]: Snort exiting
May 19 01:12:51 snort[24729]: ===============================================================================
May 19 01:12:51 snort[24729]: ===============================================================================

Well, I just tested today's snapshot: FreeBSD 7.2, pfSense 1.2.3RC1 (2008-05-18), and I still get no traffic in qVOIPUp.  Again, going back to 1.2.2 release works fine with the same configuration.

Also reported by another user here (although with ipsec): http://forum.pfsense.org/index.php/topic,15450.0.html

Let me know what info would help ….....

regards, ...... Charlie

ok,
the RC1 is great!

squid + shaper + captive portal it's ok

thx

I had the pfsense ipsec VPN working flawlessly to my 3000 series cisco at my previous job.  It was, however, a bit of a bear to make it work on the Cisco side.  It is certainly doable, as I said, mine was rock solid but the cisco config side wasn't exactly straightforward.

nb

Usually the reason the snapshot stops is that there is a problem in the build that they don't want people using and breaking their systems. When its fixed then they continue to make snapshots available again.

someone mind telling me if load balancer is fully functional without issues in the latest 1.2.3 snapshot? I plan on upgrading from my 1.2-RC2 lol. Load balancer is very important for me.

I used the Pf-Sense setup document and I am recieving the following:

May 6 20:08:55 racoon: INFO: received Vendor ID: DPD
May 6 20:08:55 racoon: INFO: received broken Microsoft ID: FRAGMENTATION
May 6 20:08:55 racoon: INFO: received Vendor ID: RFC 3947
May 6 20:08:55 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-03
May 6 20:08:55 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
May 6 20:08:55 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-01
May 6 20:08:55 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-00
May 6 20:08:55 racoon: INFO: begin Aggressive mode.
May 6 20:08:55 racoon: [Remote Connection]: INFO: respond new phase 1 negotiation: xxx.xxx.xxx.xxx[500]<=>xxx.196.xxx.72[500]

I have not had a chance to test with any other verison.
RC

I attached a monitor and looked at the box booting, but I couldn't really see anything in particular. It says something about not being able to load kernel and returns to some kind of command prompt saying "OK" to the left.

The image I used was ok and md5 checked ok.

I will not yet reinstall pfSense on that box (it now serves as an AskoziaPBX test install instead).

Cheers,

There are others which have reported similar IPsec stability issues even on 1.2.3 RC1, so I would hold your hopes up too high that it will be better:

IPSec Tunnel dies but shows as up still

I don't think those fixes hit 1.2.3, I think they were exclusive to the 2.0 line.

Adding it in an image would likely not happen, as those are all part of the individual themes.

That said, it might be possible to display it somewhere in the GUI. I suppose it could be part of the System Information widget on the Dashboard. (Technically I know it's possible, I'm just not sure that it is desirable to do so)

Many people probably don't know or care what version of FreeBSD that it is based on, and it's rather easy to run "uname -mrs" or consult a chart.

if networking devices r to be talked about then mayb a bluetooth card, some routers which can be connected through USB and in other devices, a USB flash drive to repalce the use of CF cards and i know its not possible and its been discussed also but if possible a way to use a USB ADSL modem (Aztech)