yes also its happen to me

but outbalance will not work if u turn on a AON.

I think you can find and / or define the default route of the LAN interface to the net by turning on advanced outbound NAT. Or are you asking about the default gateway assigned to each interface in a multiwan configuration? So far the new setup seems very intuitive for an Alpha Alpha release.

http://devwiki.pfsense.org/OpenVPNWishlist

It's on the wishlist.
I'm not sure if it will make it into 1.3, but as far as i read there are a lot of new things for openVPN in the pipeline :)

I've created the limiters. But i don't know how to do this [Open the default lan rule and select for in the limiter with the source address mask and out the one with destination address.]

When editing a rule there is a section at the end labeled "In/Out" match those values with what i said.

For the second part it can be done but not with the setup i have described above, you need some limiter childs for that.

Jupp, updated and now it is OK.  We can close this topic.

Hi sdale,

F.Y.I.

Tried the "ALPHA-20080801-0408.tgz" but is still the same.  Tried to remove the "widget" section from config.xml
and restarted and then added the CPU-graph but still the same.

//Dan Lundqvist

this has been fixed

Upgrades probably won't work on embedded, you have to reflash. I don't recommend using 1.3 embedded at this point, it's not going to use the same kind of setup it does now in the release version.

Surely that is not the best solution, but is resolved.

I remove this line:

In file /usr/local/www/services_imspector_logs.php

Thanks cmb!  It is enough to add it before 1.3 is released…

As this is just things to make administration more efficient it is better to focus
the attention to the more serious bugs and to implement the features that
was planned for 1.3 and take these nifties at the end when you have time
as it shouldn't take to long to add these and can be done when you have
time over...

If you want I can take a shot at it and make the adjustments and hand
it over to you so you could check it into the CVS.

Best regards
Dan Lundqvist

There is a problem with the static IP fields being grayed out when they shouldn't be, it's known and will be fixed likely within the next day or two.

ok… then we could close this thread...

signal 11 repeatedly like that is typically a RAM or other hardware issue, looks like that's what it turned out to be.

It needs to be smarter about version checking in the future, for now that's expected.

that isn't supported yet, watch the blog for updates

it's WIP you are treating 1.3 as a release which isn't so stop complaining about it.
Though, it iwll be implemented in time for 1.3.

Thanks.

Installed successfully with version pfSense-Full-Update-1.3-ALPHA-ALPHA-20080723-2313.tgz.

Have done the change and it seems to work for me as well…

///Dan Lundqvist

Yup your fine for power.