I think it's about time so peeps can focus on V2.0.  :) Darkk

I'm running on a Singlethreaded OS, which is running perfect for 7 days now. I've done a major DDOS on it and it had no problems taking that on singlethreaded. So i'm going to leave it for now. I've been to the datacenter and reinstalled too often to try another trial of multithreaded etc etc.

I found the answer to my own question.  We went to enbale the bluetooth on the printer and I had to go into the advanced settings.  It looks like I had set a static ip address server months ago.  It pays to weite this stuff down. The lastest version of PF-Sense is solid.  Overall it is a great product and I would not even think about switching to anythig else at this point.  I keep converting friends and business partners. The more I work with it, the better I like it.  The PF-Sense Team rocks.  I can't wait until release 2.0 hits RC. From what I have seen release 2.0 is going to be a great product.  I have run some virtual tests with it and have not reun into any issues. The Best way with a virtual machine I have found is to create one image and then export it.  Re-import the image with a different name.  Do not restart the image once it is imported.  Shut down your primary image.  Bring up the secondary image.  Upgrade that image to the 2.0 image.  It work like a charm.  I have done this on a few occasions and it has never failed me yet. Thanks. RC

The Devs are aware of your issue.  Please work with Centipede as cmb requested.

I doubt it will hurt anything.  Cosmetic.

Hi, Hmmm…dunno what happened to your box but I just did update to the latest 1.2.1 from the GUI, took ~3min to download, untar/patch then reboot as usual, the whole system came up in another 3min or so. I would say that whole update process should be done in NLT 10min. cheers,

Perry: Now that makes sense. And you're correct, they all do show up with a mouseover. It's just truncating the list for space considerations…? Can anyone confirm that?

That appears to be cosmetic only.

My Problem is that Intel Card is an integrated card on the motherboard  :-\ The other card is a 3Com card that works just fine. In the 1.2 (FreeBSD 6 based distro) all works just fine. FreeBSD broke intel nics that are installed with an adaptec SCSI controller. Something about a similar driver call or something. Anyways, it will probably have to be a kernel fix from the FreeBSD devs. I have done any research on it lately to see if there is a patch available. Iw ill have a look around.

We'll look into it.  Thanks

Hmm… this may have been Snort related. I turned off Snort to eliminate that possibility, but I'm guessing that didn't actually remove any existing firewall rules. I just cleared out all the blocks and restarted snort, and it's working for now.

The errors have stopped… it seems they appear right after a reboot, keep showing for some hours, maybe about a day and then stop. I don't have the serial cable connected BTW. Any ideas?

okey, tnx for clarifying /F

Thanks for creating the ticket on that. As for the new PAT rules not acting as expected, it seems to be working again in 1.2.1-RC2 Sun Nov 9 09:51:34 EST 2008, though looking at CVS, I can't figure out why.

To all who explained VLAN ID1 / Default VLAN to me: thank you, i'll have a second look at the configuration the comming week. @cmb: This isn't clear to me - does it just not work now that you added VLANs, or did the VLANs work fine in the previous version and when you upgraded they stopped working? Its not that the VLAN's are not working, they are, its just that the PPTP clients are nolonger able to reach the LAN clients and servers… though after reading GruensFroeschli's reply about the tagged/untagged traffic problems he had i am starting to suspect that might be the case for this problem aswell... The pfSense port has been set to 'tagged' and the win2k domain is mostly on 'untagged' ports (as they would be using the default VLAN). I'm going to play with the VLANs a bit more the comming week, i'll have a redraw on the network implementation and will give it a new go. I'll update this thread if it solved the problems we experienced or not.

The latest snapshot is fixed:  :) :) 1.2.1-RC2 built on Sun Nov 9 18:11:45 EST 2008 Darkk

You could also create an alias which contains both your LAN1 and LAN2. Then use this alias in your second rule (allow anything with as destination NOT the alias).

Ahh, that explains it is there anywhere i can dl the latest snapshot that was released? /F

m0n0wall didn't have IPsec filtering when the config import was created. The problem is m0n0 uses <interface>ipsec</interface> while we use enc0 instead. Same thing, different name. This is a bug, I opened a ticket. http://cvstrac.pfsense.org/tktview?tn=1829