Good solution! :-)

There are new snapshots every day. Here you can find the changelog of the snapshots.
https://github.com/bsdperimeter

It is not neccessary to update every day but it makes sense to do so once a week or every two weeks.
If you think you found a bug, first check for an update and then report to the forum if the bug is still persistent.

You'll find that a USB memory stick is a great way to install as no optical drive is required.  I posted my newbie wanderings here: http://forums.smallnetbuilder.com/showthread.php?t=5379

Cheers,
Dennis.

I tried "update error" in the search box and it gives me this: Pages: [1] 2 3 4 5 … 38

Maybe you are searching in just a particular section of the forum.
For the Installation and Upgrades section: Pages: [1] 2 3
For 2.0-RC Snapshot Feedback and Problems section: Pages: [1] 2 3 4 5 … 13

Did this solve your problem?
@stephenw10:

Have you read this?
http://forum.pfsense.org/index.php/topic,38687.0.html

Steve

np, keep an eye on that board for 2.0 related stuff.

I have the same problems, albeit a bit different, I get this message only for one interface, when I try to put it into the same gateway group and put it on the same level to have loadbalancing.

Connections trying to use the new interface fail and the connections do not work proberly at all (most of them time out).

I use VLAN's for my WAN connections. Each ADSL Router has it's own VLAN and Network (a 10.100.<vlan>.0/28 net) where vlans are counting up from 100. So there is no overlaping.

Another symptom I have is with the failover pfsense box, which when started does not recognize it's Backup and everything is Master, I have to deactivate CARP and activate it again on the Backup-Router to have it become Backup. Then all gateways are offline except the one which is on the interface which gives me the problems described above with llinfo stuff, it stay's online and I get packet loss on both, the primary and the backup box …

The servers are no-name computers with Intel PRO dual-port server network cards.

Hope someone can figure out what's going on, i have this since the Beta through 2.0-RC3 (i386) built on August 3rd.

best,
Ray</vlan>

@Gradius:

I see.

Thanks.

But if you like to help the developers to fix bugs it is neccessary that you are running an actual snapshot so that they can narrow down between which snapshot there exists a new bug.

@stephenw10:

Create the file /boot/loader.conf.local and add the line there.
See: http://doc.pfsense.org/index.php/Boot_Troubleshooting

This doesn't work for everyone but it does in most cases.

Steve

Worked for me!  Got the box working.  Thanks.

Ken

stephenw10 sorry, I forget to get a bigger image, thanks!!!

Boot the other slice (the one that is still from the 4gb image size) and then re-run a proper upgrade.

If that doesn't work, you'll have to reimage the entire card.

Read howtos for cf installation, that should handle it

Well… That's why I am testing this.
I don't mind the startup / leaning issues so long as I can figure out in a few weeks of testing if I can get it done.

At the same time I have an openSUSE server box I am working on. While not on-line yet, if pfSense does not pan out I will turn my efforts over to it.

btw: any recomandations on a working Reverse Proxy? or a way to get a simular screen working?  ;D

Covered in the FAQ ;)

In short, each are for the respective size of media (1 GB, 2 GB and 4 GB CF cards etc).

I also experienced this from the last snapshots, from July 18 - 31. All I have to do is uninstall and reinstall. Although my chance of success was very minimal, but it worked later on. I think it has something to do with the packages. I also experienced this perl error with ntop and squid.

Aside from that, this is what I experienced in the last few days: http://forum.pfsense.org/index.php/topic,39420.0.html

There were also times that the installation was a success, but I cannot find the menu in the gui. So when I remove the package or do a reinstall, the installation process got to a halt or hang.

yes, I'll just reinstall and restore, thanks!

@jahonix:

You cannot install packages from the internet without a connection there from WAN interface.

True. But I don't recall any packages being required unless one or more packages is selected for installation.

So you did a full install to a HD then?
There seem to be a number of other users running Varnish on 2.0. Search the forum.

Steve

Edit: Doesn't seem to be in the package list though.  :-\

@central:

When I boot without any media (CF/HD) connected the display shows a boot error message and menu options proving that the display does in fact work.

When I boot from the CF card the display turns on, iIget one beep and the display then turns off….

Once the boot is complete and I'm faced with the console menu (like in wallabybob's post) the display turns back on but nothing is displayed.

Hmm, well that's odd.
The normal sequence for the LCD (if you haven't loaded the firebox LCD driver) is something like:

Turn the box on: backlight comes on displays 'Watchguard Firebox' or something similar.

Shows 'memory testing' followed by 'complete'

Beeps and then shows 'Booting OS' (or boot error if the CF is wrong or missing)

The display then remains the same, with the backlight on, as pfSense does not talk to it without additional drivers.

Steve

Did not do a reinstall I did a fsck -t ufs /dev/ad0s1a and everything was clean but I still get a trying to mount from ufs:/dev/ad0s1a at the console screen and just hangs their.  But I am log into the web gui of pfsense and I am passing traffic through and making changes with no problem.  This is very weird.

@stephenw10:

I'm not sure I follow what you have to type in.

You can set the dns forwarder to resolve local hosts. In Services >> DNS Forwarder: you can set DHCP leases or static IPs to be resolved.
You can also add dns records manually to point at internal servers.

Steve

I got it to work. In DNS forwarder i pointed my domain name to the ip address of my server so when I just type in localnet.me in the browser it takes me to my servers intranet wiki webpage. Just dont type in the hostname.

@jasonlitka:

The drop is probably due to the latency of the extra hops to send all traffic through the VPN provider.  I lucked out in that sending traffic through Vypr only adds 6-8ms to my pings.

I will build another pfsense box and try the vypr as well. Giagnews and vypr isnt a bad deal at all.