Thanks for the clarification.  Just a guess here, but I'm guessing you had snort installed somewhere before June3rd or so.

Going through that process on a new install of RC3, and repeating your process:

Jun 30 09:05:57 SnortStartup[36413]: Snort HARD Reload For 45292_re1…
Jun 30 09:05:57 SnortStartup[33404]: Snort Startup files Sync…

So with SNORT loaded, reset, interface reset, pfsense updated to latest snapshot, rules downloaded again, updated, and a few rules selected to filter...no go.  Based on the removal of the 32 bit snort package, I'd guess there are known issues with the 64bit version too that are not being shared here.

Cheers,
D.

a normal host alias accepts domain names.
But it only resolves those domain names nothing down the domain hosts itself.

@Gloom:

http://forum.pfsense.org/index.php/topic,37557.30.html

It's been removed by the maintainer and will be restored after he's finished the updates.

Ok, thanks for updating me… I will upgrade again in some days, fortunately I was updating my secondary server only, so on the primary machine snort is still working...

Thanks,
Michele

1:1 is fine, your existing rules will be upgraded to the new format for 2.0's 1:1 (which allows additional capabilities not previously present, but will work the same). It sounds like it's working fine but your VIPs aren't. Sounds like either you have an upstream ARP cache preventing that from working, or have the wrong type of VIP (don't use type Other in this case, any of the other types will work). If you're swapping out hardware between 1.2.3 and 2.0, you must clear your upstream ARP cache (or wait hours for it to timeout). If your upstream router is on premise, just power cycle it. Otherwise you may have to call your ISP.

wowowowow i am dumb, I am used to seeing it on the home traffic shaper page  :P
Thanks brah

As I read your comment regarding the disappearing menu items I remembered, that I installed the widescreen-package some time ago. So I restored an older snapshot without that package and this problem was gone.
Concerning my traffic shaper issues I spent some more time with configuration yesterday. As far as I know I did not changed any options but suddenly it worked. After saving the configuration I tried to get the limiters running to define a minimum bandwith for my p2p-queue but had no success.

The only remaining issue is up on the nat reflection. As resulting problems can be avoided by connecting the services via lan-ip directly I can live with that but for the final release it would be a nice to have feature…

Thank you for your reply.

greetz,
plex

Can you send me the packet traces at ermal at pfsense.org?

One of my mentors would mention here: "you're learning, making mistakes helps"
;)

i did the zeroes and all other recommendations
it's a 250 gb hard drive and i was able to install 1.2.3 on it no issue but rc3 is a no go no idea why for now i have just switched the harddrive and am doing a manufactures diagnostic on the disk

No need for a full xml editor. Any text editor that understands unix line endings would do fine. (Ultraedit, I'm sure others like Notepad+ and such do as well)

Then it should be operating normally. If you're seeing some other issue, the IPsec logs might be helpful, and/or the setkey -D and setkey -DP output. It probably isn't the SA preferral.

Make a lagg with the second (unused) interface, edit the VLANs and move them to the lagg, then once the vlans are off the original interface, add it to the lagg. Shouldn't be any downtime with that. It's just not easy.

After first reboot it shows that freedadius as running in GUI Mode and shows in the system process as well. But when I try to authenticate any user it says Error: No valid radius response received. and then if i restart the service manually it works fine.

But when system boots, it does not authenticate users automatically. Although it shows that service is running but does not authenticate.

I restart this service every time I start pfsense for radius to work.

The next new snapshot should be ok.

@leap:

I can't find any debug mode enable on System: Advanced: Miscellaneous. I am using 2.0 version.

What snapshot are you on? If you are on a current snapshot (Or at least RC3) it should be there. It's under "Security Associations" and above "Maximum MSS"

A package must not have reinstalled properly. Check your console for errors.

You can reset the package lock under Diagnostics > Backup/Restore.

@Liath.WW:

Okay, I think I know what the issue is.  In 1.2.3 the menu option for the traffic shaper took you to the rules for the shaper as well.  In 2.x the "Rules" page is where the shaping rules appear.  So, you need to go to the Firewall rules page.

Thanks bud  ;D

The default assigned NICs have always been correct out of the box for ALIX. What you're describing sounds like you're on an old snapshot with check_reload_status not working, some from early this month would have issues along those lines.