Try putting your file in /conf.default on the CD

Glad to hear you got it working. [image: attach.png] [image: attach.png_thumb]

Restore worked this time, so it was the above setting and/or something else that prevented a proper restore last time.  All good! Also, the original crash may have been to a failed/failing USB stick; CAM error today.  :(  Went with hdd this time.  Hopefully no problems for a while.

@stephenw10: Hmm, OK. We've tried the usual suspects here. You can see this behaviour in a multiwan setup with gateway groups. The clients on LAN use the gateway group to access the internet, in your case you have a failover setup. If you have firewall rules on LAN that catch all traffic and specify the gateway group then you are never using the system routing table to select a gateway. The pfSense box itself cannot use a gateway group it always uses the system routing table. Thus if it's default gateway is set incorrectly it will not be able to access the internet. Using the ping test in the diagnostics menu will fail to find this since you have to specify which interface you want to ping from. Go to System: Routing: Gateways: make sure the default gateway is set to something sensible, like your primary WAN connection. Steve Steve, thanks a lot for this. It makes sense now why as I'm testing my failover setup, once off my "default gateway" which is set to the "primary" wan connection, pfSense refuses to check updates or download from the available Package list. If I swap the default gateway to the (2nd) wan connection, it immediately works. Shouldl this behaviour affect my client workstations (DHCP) at all? Or would it just affect the web configurator from accessing the internet when the primary wan is down. Is there a way to add a firewall rule ahead of the failover gateway group "catch all", so that pfSense web configurator traffic is captured first? Hmmm Andrew

Sounds like some lame rebranding attempt to me…  ::)

Opened a support ticket.  Turns out that the issue was related to pfBlocker not being properly uninstalled during the upgrade and leaving behind a broken alias/rules.  Once the config was cleaned up the Firewall/NAT rules loaded properly and the box worked.  I am now in the process of upgrading the primary as well. No idea on the ix interfaces with vLANs though.  That is still broken for me.

@divsys: [What version of pfSense are you running? [/quote] 2.2.5. Thanks for the autoreplace tip, that's probably what I would have done. I'll make sure to do it manually.

Newbie here.  Working through all things pfSense.  This was one of them. I put an old Dell laptop to use with pfSense for routing and radius functions.  Had problem where, from the main console menu, when I choose reboot (option 5) it goes until it stops the system and the last message is the "Uptime…"  then it just hangs.  I have to force a hard power off. Googled everything I could find, most folks suggested ACPI, so I went looking for it in the BIOS, but it's not there.  While I was there I noticed that this system had AHCI enabled for the HD controller, which is fine for windows and intel parties, but I dont' think it helps in pfSense under freeBSD!  Or am I wrong here ? Anyway, I changed the HD controller function back to the Dell default of ATA, not thinking it was connected.  When I booted and did a reboot, it worked. For what it's worth, something about AHCI seems to mess with the reboot process.  I'm running 2.2.5

Once u get vlans they are not that difficult understanding native and tagged vs untagged and different switch makers use terms a bit different but if you understand the basics just need to know what switch your dealing with

@Seif: I was hoping to find a way to make them work. The only way to make them "work" is the one you mentioned in the OP. I.e., force the ports to 100Mbit.

After following article i was able to boot pfsense but it wont survive reboot .. it will be at that screen requiring me to input ufs:/dev/da0s1a http://mundofreebsd.blogspot.com/2012/09/mounting-from-ufsdevadaxs1a-failed-with.html here is my fstab contents /dev/ufs/pfsense0 / ufs ro,sync,noatime 1 1 /dev/ufs/cf /cf ufs ro,sync,noatime 1 1 how to set them to make .. below are pictures after i entered above command .. (ufs:/dev/da0s1a)      

I am using one of these, and used it to talk to an X1000 console last week: http://www.amazon.com/gp/product/B000067SCH I bought a bunch of them a few years ago for each site. Any similar spec cable should do the same.

See my reply in your other post about this same issue.

Hello i am new to this too . I have as a project to make a Computer work as DHCP ,  Firewall , DNS , http(s) proxy and L3 routing  and route traffic from trusted and DMZ to and the outside network of the school that has internet connection threw another proxy.  (Proxy support isn't working for me either) Is there any way to install the packages manually (even the pkg is not installed)?I can download any packages from my trusted network but i have no internet connection on pfsense.I posted here as its similar problem .

For posterity: The problem ended up being the wireless card. The Fit-PC2i has a Ralink wireless card taped to the motherboard where a PCI-E card would normally go, but it's connected to a small USB header. To even see it you have to completely disassemble the machine. After getting underneath the motherboard I disconnected the USB wifi card and installed an Atheros card in the PCI-E slot. It booted up fine. It's it's any help for debugging for devs, it was the RT2870  ver. 0.33 driver causing the crash. The wireless card was working fine in the current Gentoo installer kernel and current kernel.

I also had some problems at first with a USB NIC. Apple USB Ethernet Adapter for MacBook Air worked for me.

Would have to know what IP the crash reports came from to tell. The IP you're coming to the forum from doesn't have any.

A router is not a switch. Bridging interfaces tries to make it a switch but never succeeds. This has been discussed in all possible (and quite some impossible) configurations already.