i'm realy sorry for mislead you. Because I was playing on 192xxxx IP ranges, and did not disable the general restricting rule it was not allowing me to pass. Case to be considered as resolved! Regards!

I updated to the december 24th snap and it is working correctly.

opps…. went to todays snap and.... Warning: fopen(/usr/local/etc/snort/snort_19540_vr0/oinkmaster_19540_vr0.conf): failed to open stream: No such file or directory in /usr/local/www/snort/snort_download_rules.php on line 774 Warning: fwrite(): supplied argument is not a valid stream resource in /usr/local/www/snort/snort_download_rules.php on line 776 Warning: fclose(): supplied argument is not a valid stream resource in /usr/local/www/snort/snort_download_rules.php on line 779 same again...... a lot of mounting rw & manual install of snort. then an reinstall from the gui got snort going again.

I confirm, the bogon table reset only when i upgrade to a newer snapshot, when rebooting, the bogons table stay updated.

aha … 64 bit work on proliant ml110 on latest snapshoot i think its broken when burn an image ... duhhh @wagonza thanks for ur confirmation ...

@ebo2002fr: It does not work with snapshot built on Fri Dec 24 00:25:29 EST 2010. But I must have wrong configuration. I have read that in 2.0, it is not mandatory to create 3 routing groups. Is the document http://doc.pfsense.org/index.php/Multi_WAN_/_Load_Balancing still accurate for version 2.0 ? Found Howto http://forum.pfsense.org/index.php/topic,28121.0.html

Should be fixed now.

I am getting the same error when trying to install snort on the latest 32bit snapshot.

OK, I just added OSPF to the protocols drop-down so it should be easier to craft a rule for this in the future. The OSPF package could also be changed to add such a rule behind the scenes.

Updated to latest (23 dic) snapshot and works fine.

Yup, looks like 2.0-BETA4 from 12/23/2010 does indeed fix the problem. Thanks!

I can see the /etc/inc/vpn.inc file using vi, but i can't search or anything…even backspace or delete give me some strange characters?

What I don't understand, is it was working perfectly (with no modifications) before the update. As soon as I updated, the Wireless Router wouldn't get a LAN IP from the pfSense (and yes, I did try to assign it one) or the WAN IP (which I was able to get under pfSense).

Hey! :) I just changed the HDD to try if it is really a problem with the geometry. The other HDD is working fine! I do not really af an idea what is the problem with the geometry of the other HDD… So my problem is solved...but the general problem not! Malte

Same problem here :) But I fixed it manualy by adding a ; and removing a ) See also: https://rcs.pfsense.org/projects/pfsense/repos/mainline/comments/commit/0d86d650183febdd57c89d6fe1fe6c76eebee838 https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/1e312328572b5f583fe34cf71c1efa89df460260

Thanks bro  ;D

Yeah that will do it most of time unless there is a binary that needs update. Then you need a full-update through snapshots.

Get a new snapshot or look at the solution provided here. http://forum.pfsense.org/index.php/topic,31404.0.html

You don't give nearly enough info there to speculate. Is OpenVPN trying to use the same subnet as LAN? Was PPTP? How is your OpenVPN server setup? How was PPTP setup?