@ermal:

I actually pushed a new fix.
Please try with next snapshot.

That fixed it!!! Great job ;-)

fixed

2.1-BETA0 (i386)
built on Thu Nov 22 09:33:27 EST 2012

20121123013541.jpg
20121123013541.jpg_thumb
20121123013624.jpg
20121123013624.jpg_thumb

@phil.davis:

See pull request for fix: https://github.com/bsdperimeter/pfsense/pull/266

That is looking match better :)
Hope it will be updated with the next snapshot :)

Thanks.

I use Gigabyte GA-P61-S3 (Intel H61 Chipset) with Intel Core i3-2120 and 2GB DDR3 of memory. I also can't install from pfsense iso distribution. Always get error when mounting the root partition in CD drive.

Crash report begins.  Anonymous machine information:

i386
8.3-RELEASE-p4
FreeBSD 8.3-RELEASE-p4 #1: Tue Oct 30 10:57:28 EDT 2012    root@snapshots-8_3-i386.builders.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8

Crash report details:

PHP Errors:
[21-Nov-2012 21:07:19 UTC] PHP Parse error:  syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting ']' in /usr/local/pkg/zebedee.inc on line 92

Filename: /var/crash/minfree
2048

@jimp:

Next snap should be good. Either wait for that one or gitsync.

all better, thanks jim!

Yep, usually the first fails because of some missed port dependencies (is documented as such) then you redo the build and from then on everything works quite fine.
The first build run usually takes quite long time to  build all ports, so the more cores you throw at it, the faster it will go.

Hi Matsim…

Please guide me a little further ,cause i'm a newbie regards git.

Today I have changed the virtio driver to e1000.

Then everything works as expected...

/Best Michael

Patch to be used with the System Patches package:
Path Strip Count = 1
Base Directory = /
Ignore Whitespace checked

--- a/usr/local/sbin/ppp-linkdown      2012-11-20 23:51:28.000000000 +0200 +++ b/usr/local/sbin/ppp-linkdown      2012-11-20 23:55:26.000000000 +0200 @@ -20,7 +20,9 @@         fi fi # delete the node just in case mpd cannot do that -/usr/sbin/ngctl shutdown $1: +### disabled because of the following bug: +### http://redmine.pfsense.org/issues/1943 +#/usr/sbin/ngctl shutdown $1: if [ -f "/var/etc/nameserver_$1" ]; then         # Remove old entries         for nameserver in `cat /var/etc/nameserver_$1`; do

I think Wallabybob has already given the answer multiple times.

http://forum.pfsense.org/index.php?topic=46325.0

I'll see if the order in which the delay and the fw load command are, makes the difference?

Many thanks for all the help!

@cmb:

You're probably running the Widescreen package, which I don't recommend because it overwrites base system files. It overwrites the menus with ones that are wrong for 2.1.

Hi there,

Yes, there was widescreen plugin.
1. remove plugin (re-login - din't help)
2. downgrade to previous snap-backup and install current snap.
Reboot & fixed.

You probably have noscript enabled as my first guess. Otherwise something else in your Firefox is breaking javascript.

The provider broke network connectivity on that host. I changed its DNS a while ago to switch it over to its backup at another datacenter until that gets sorted

Hi CMB,
it appears to be working now with the latest snap this morning. cheers

regards,
louis-m

Yes, that was the reason as I found out that the backup FW wasn't able to connect anywhere as it was using carp IP as a source one so all replies went to master FW.
There are no issues since I've upgraded to newer snapshot.

Thanks guys.

Hi Msi…

I can not boot into a Stock FreeBsd 8.3 64-bit , FreeNAS etc ....

check this link on Proxmox Forum : http://forum.proxmox.com/threads/11843-Proxmox-2-2-Freebsd-8-3-AMD64-freezes-can-not-start-installation

Testing the i386 , with a dual port Intel I350-T2 , seems to works fine...

/Michael

would it handle nat etc properly as i have advanced manual outbound nat enabled?

in port forward the destination ip i need to set as pfsense ip?

The logs reference the PF rule number, which changes if you add rules, but doesn't that change the logs from before the rule change. There is no historical record of previous rule numbers, hence that's the expected behavior.