Also line 705, for the queuedrop, same case, $t need initialize to 0

Not sure if this might be some of your issue, but the webgui defaults to HTTPS now, so you should be using https://lan.ip

If you still have issues that doesn't fix, I'd start a new thread for it since it's a different topic than an update issue.

Should be ok in later snaps.

Sure, have a look at this thread: http://forum.pfsense.org/index.php?topic=10629.msg63490

I downloaded 2.0-BETA1 built on Wed Dec 30 08:56:00 EST 2009 FreeBSD 8.0-RELEASE-p1 today.

The wizard is fixed  ;)

-JR

Thanks for your help, but pkg_info shows:
pkg_info: no packages installed
But squid is still running, system activity shows:
1148 proxy    44    0 18976K 12340K kqread  0  0:51  0.00% squid

+1 on this. Fully agreed.

I know….also why I look forward to seeing the PF with L7. As long as its as easy to implement and do specific rule logging as well as ISA, I would change in an instant.

@onhel:

Also, if you happened to use LZO compression in 1.2.3, that setting does not transfer over to 2.0 so double check to make sure that if you require it that it is indeed checked.

That should be entered into a ticket on http://redmine.pfsense.org if you have more details about that.

Definitely a bug, all settings should carry over.

You can't always just gitsync, unless you stay up on source changes and their implications, you may end up with breakage because you must have binary updates in addition at times.

Shows up there fine for me. Type in the first letter of the alias and it shows up, just as always.

Shaper doesn't really work at the moment, so I guess I will have a look when it starts working ;)

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

Could you also help me with this one?

Now I changed my identifier to user distinguished name on both ends and just entered user@domain without a .something at the end and the tunnel established ;)
I'll have a look at the stability right now.

Crossing fingers ;-)

Yes, you can create any number of groups that do load balancing, failover or a combination.

Just reference them in your rules.

ill test it with the 28th december snapshot

It periodically (re)resolves hostnames contained in aliases so you can have filter rules which are not tied to a specific IP (or in the case of one using google.com, it could be many IPs)

Do not disable mwexec. It does many, many, many things for the system.

And keep tracking the latest snapshots for potential fixes.

If that's the same Supermicro 1U atom 330 I have, there is a PATA controller inside. Hook a CD-ROM up to that and install.

Or install 1.2.3 and do a firmware update to 2.0.