A commit a day or couple days ago broke package reinstall, that was fixed earlier today.

In addition, I got these errors: php: : There were error(s) loading the rules: /tmp/rules.debug:46: syntax error /tmp/rules.debug:47: syntax error pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [46]: nat on $WAN from $tonatsubnets port 500 to any port 500 -> 77.0.204.115/32 port 500 Thanks a lot for your help! Juel

The floating rules fix the DNS and UDP problem after bootup, but do nothing for the start times (adding 5 minutes to the boot up time).  Of course, rebooting pfsense should be a rare thing…...    I haven't been able to solve the package lookup or version lookup yet, but I suspect that is just another floating rule.

@Nachtfalke - Deleted 7zip file from post to get rid of confusion and reposted what JimP had put.  I couldn't download it either for some odd reason.

@LostInIgnorance: One of two things.  Either snort didn't install correctly, or when you upgraded, you forgot to sync up the rules.  Right after an upgrade I always re-download the rule definitions. they get deleted when the package is re-installed..So you have to re-download them :-( Until Snort is updated by the dev for 2.0, you will see bugs in it. Example, whitelist doesn't work correctly.. It will block IPs on your whitelist if an alert comes up.

thanks for the response! I will give it try as I get a chance

What kind of information were you expecting to see on that page? There are some other articles in the "Bridging" category (click the link at the bottom of that wiki page) : http://doc.pfsense.org/index.php/Category:Bridging There is always room for improvement of course, but the book will always be the official source of the most complete information. If there are specific topics that people would like covered on the wiki or to expand existing wiki pages, we're always open for suggestions (or even better, volunteers to write the content).

We keep notching the sizes down and the manufacturers keep shrinking their cards…  :-\

@jimp: Not until you see a blog post and official signed images. roger :-)

Given that it's a 12+ year old board there probably isn't going to be much hope if you haven't found it by now.

Hi, Maybe there is a kind person that has made this described change directly in the image file (for thouse of us that don't have BSD installed -> can't make this change themselves…) /Kind regards, MrP

that's normal in some circumstances with FreeBSD, google the error for details.

There are a number of different constraints that apply to sysctl variables. Consider the following from my system: sysctl kern.ipc.nmbclusters kern.ipc.nmbclusters: 8000 sysctl kern.ipc.nmbclusters=7999 kern.ipc.nmbclusters: 8000 sysctl: kern.ipc.nmbclusters: Invalid argument sysctl kern.ipc.nmbclusters="7999" kern.ipc.nmbclusters: 8000 sysctl: kern.ipc.nmbclusters: Invalid argument sysctl kern.ipc.nmbclusters=8000 kern.ipc.nmbclusters: 8000 sysctl: kern.ipc.nmbclusters: Invalid argument sysctl kern.ipc.nmbclusters=8001 kern.ipc.nmbclusters: 8000 -> 8001 Looks like the only allowed modification to this parameter is to increase it (though there might also be a maximum value).

Thought I'd add something here as I've just struggled to get this working using information from the forum and the wiki. As gnhb says above I have access to my modem without using any outbound NAT mappings or extra firewall rules. I simply added an extra interface, assigned it to the NIC attached to my modem and set it to static IP in the same subnet as the modem. The last step was to add an extra gateway on that interface with the modem IP address. If someone would like to explain why the outbound NAT is needed here I'd be glad to know. For me it's working fine without it and adding it only caused problems. Steve

Thank you Ermal for the tip! (faleminderit ;)

@Nachtfalke: put it in /boot/loader.conf.local If it does not exist just create it. Thanks, havent used *BSD  in like 10 years Thinking of going back to it from Gnu/Linux