Ok thank you. It works  :)

For sure … I hope to get back to 64bit when 2.1 comes around. I am hoping that FreeBSD 9 improves on 64bit stability. ( I think it will as part of that time progression thing).

Hi conehead, On your screen the size reported is close than 4Go. I had the same question when I wrote a 4Go image, because physdiskwrite reported less byte than total byte written… In fact writen byte equal exactly the file size of image (see attached file). Did you check your real file size ? [image: physdiskwrite_size.png] [image: physdiskwrite_size.png_thumb]

Thank you for your aswer. In fact, when the modem is not plugged the Wan is "disabled". I have changed the computers and the wan does to be linked with the pppoe0 interface. The public IP appears on the console and the wan is up and enabled. I was afraid for nothing  ;)

@stephenw10: Looks like you've had some fun!  ;D Where are you using the 500GB drive? What are you going to be running Samba on? Steve Samba and Transmission are actually running on the pfSense router itself, thus freeing me from needing my computer on all the time. For those long downloads with few seeders, I can now divert that task to the router instead. I'll explain in more detail how to get multiple static IPs combined with a dynamic IP on Cox HSI in my next post, after that I'll probably delve into the Samba + Transmission setup, the highlights of the setup. The 500GB is connected to the router ideally, I haven't set that up just yet, but if that becomes another adventure, I'll document that too.

thanks for the ideas have to give g4u a try and the check out rc.fullbackup thanks all

@dsagud: What can I do ? Follow the suggestion and verify you have correctly configured the pfSense interfaces (WAN interface particularly), verify you have correctly configured DNS for pfSense and verify that your connection to the Internet is working (that it is up and you get a response when you ping your ISP's router). It would also be helpful to provide some information about your configuration and the results of the troubleshooting you have done so far.

Thanks guys for the input … I will test the firewall again without the Wireless device and hope it will not panic anymore or whatever happened. The CPU might be te culprit too, it doesn't have a fan since it's an embedded one ... But it's in a cool enough environment that it shouldn't be a problem, guess I'll be monitoring that one as well. The strange thing is that it happened only the next day, while before it worked without a problem, but that's the name of the game isn't it. Thanks again.

@argie01: Hi, and thank you for the link. I fixed the problem. The cause was I setup aditional network interfaces on Vmware as "VMXNET 3", and PFS didn't detect them. When I changed it to "flexible" the interfaces were detected correctly. Where did you make this change? I'm asking because I'm setting up pfSense to run in a VMWare virtual enviroment as well.

Thanks for the quick reply and happy hollidays

Update: Today i've got an IP from VLAN1002 (public wifi) from the PFSense router : 10.102.0.100. Screenshot:http://kris.derocker.name/pfsense/merakivlans/pfsense-dhcpoffervlan1002.jpg But : no IP on the other SSID's and no internet activity…

Deleting the widget section did the job. I think the problem was the snort widget, which could not be deleted by the GUI. The widget is not running at all, so no one will miss it. Thx!

OK Thank you! I tried change to enhance mode, but also without success. In an next step I will try with smaller partitions.

@impire: I think the problem boiled down to using the 2 NICs of same exact model. This will conflict with the built-in NICs as  Pfsense or FreeBSD seems to assign the same IRQ to both NICs. Its very unlikely that interrupt sharing is a problem for modern NIC drivers. When I saw multiple bce NICs, problem on enabling fourth, I immediately thought of the page Steve linked to. It seems the bce driver preallocates a lot of mbufs (network buffers) on enabling a NIC and this causes causes exhaustion or near exhaustion of the default mbuf allocation when there are "enough" NICs.

@jimp: http://doc.pfsense.org/index.php/What_are_the_512M,_1G,_2G,_and_4G_NanoBSD_files%3F thank you.

You can download that upgrade.img.gz file and apply it from System > Firmware. That upgrade image would not require a "reflash" from 1.2.3 there, it upgrades in-place via the GUI (or console update), and retains your configuration. If you want to wipe the card and reflash starting with 2.0.1 you would need the full image (it does not say upgrade in the filename), and that would not keep your config you'd have to take a backup before starting, and then restore that config backup after booting the newly imaged card.

Package reinstall probably failed. Check the console. You can clear the lock by going to Diagnostics > Backup/Restore and hitting the button at the bottom to reset the lock. Then you can reinstall the packages you need.

It already checks the availability of the package server before it starts the reinstall process. However, if a package pulls in data from a different server than where the package's main files come from, it can fall into a different kind of trap there. There are probably ways to make the whole process more robust, but there isn't an easy way to redesign the whole process to download all of the files first and then reinstall.

Some more information might be helpful: What variant of pfSense (nanoBSD, full, full embedded)? What motherboard? What else is displayed on the screen (or serial port)?

Update worked fine on the first site but failed on the second site, reinstalled using the full install ISO (i386) but I am faced with the same issues, packages wont reinstall also I have X3 WAN's using PPPoE and the third WAN keeps disconnecting  :( Now reinstalling Version 2.0