Thanks for pointing me in the right direction. I had searched the bugs but somehow I missed that one. I used the workaround that Chris Buechler had posted in the bug and it seems to be working for me.

I think I see a bug with the auto blocker in Snort.. Correct me if i'm wrong here. If snort auto blocks an IP because of of a rule trigger, should I still see the IP being blocked in the firewall log?

Did try that - makes no difference.

Thank for the feedback everyone… I made the step and started to mess around with 2.0.. OpenVPN work like a charm upgrading from my 1.2.3 config.. I few things dont work just right but i can live without for right now... Never thought of making slices on the HD for different ver of pfsense... Should had thought of that since I do have the HD space to make a few.. My motherboard has IPMI so i'm able to access the console anytime ;D

I still want to get snort and squid to work on my box but i'm going to clone/image the HD before I start to tinker more... Makes for a easy recovery... I was told that everyone will be going thru a proxy server soon at work... So i'm hoping to use OpenVPN and Squid for my web surfing at work..Oh and I work in IT but our VP said no one is exempt, WTF. FB has being a problem here, I wonder why, lol...

Thanks for the clarification Chris, I think then its most probably an issue with my switch or the software running on my ap's not passing the mac address correctly on random occasions, Ill have to investigate further.

Thanks

Slam

Snapshot 20100405-1403 still not working…same behavior.

Already made a ticket a few days ago.

@EmL:

oops … i'd thought i had understood, but you tell me different! Here's what DMESG tells me:

ad0: 1923MB <cf card="" ver2.21="">at ata0-master PIO4</cf>

Your CF card would probably be classified as a 2GB card, in which case you could install a 2GB image, or a 1GB image or a 512MB image, leaving increasing amounts of unused capacity.

Thanks cmb.

I noticed this was logged in the bugtracker.

I'll be available to test and provide feedback when it is fixed.

Thanks,
Ade.

I'll give it a try as soon as i have a few minutes.  It may take a day or two.  My immediate concern is lack of multi gateway load balancing.

As always, thanks for your help.
-V

Thanks slam. I'll do a downgrade now.

Cheers,
Ade.

You have the rules backwards. All traffic is filtered where it initiates, you'll never see LAN source traffic on wireless nor wireless sourced traffic on LAN.

Hi,
Please report what version you are using and what interface(s) you are using for LAN/WAN.
Thanks,
GB

@afrugone:

I invoked auto upgrade, Reboot and version still the same:
2.0-BETA1
built on Fri Mar 19 23:39:43 EDT 2010
FreeBSD 8.0-STABLE

Have you tried upgrading straight from the shell? It works for me.

Edit: minor correction

@_igor_:

Is there any news? Even with snap from yesterday I have frequent crashes! There is no change in behaviour.
Connection gets slower and slower till crash. Really lots of times a day if there is much traffic.

I second this. I've tried many different snapshots and many different types of hardware (Alix 2D3, Soekris 5501, multiple different pc's) and always the same.

The system keeps running for about a day (low traffic) and then crashes. I've not been able to grab error logs, but as far as I've seen, they seem to be quite similar to the ones posted to here at the forum.

This bug is REALLY annoying and prevents usage of newer (since BETA-stage) snapshots in testing environments. In my opinion, finding the solution for this should be one of the highest important issues.

in the next couple days, I'll give it a try.  I appreciate this not being the correct fix however, I'm in a production environment and can't afford downtime during peak hours.  So i needed a quick fix for the day and this was it.  I had stability issues running the 32 bit edition, so this was a solution and seems to be working so far.  I'm now just trying to get multi-wan working and i will be in business.

Thanks,
-V