@dorrell: I am new to KVM and PFSense.  How do I install this in KVM?  If I extract it, the file has a .raw extension, not an .img extension which is used under KVM. Hi, File extensions don't matter in Linux. Just use this as your KVM hard disk image and you're good to go. Let me know how this works for you. Just make sure to set the proper devices when configuring your virtual disks and network interfaces i.e. virtio. Thanks, bert

Nice.  :) If you read through that upgrade guide you'll also see it lists a separate firmware for the LCD module so I imagine that generating some/all of those messages. It may be a standard part for which other firmware is available, have a close look at the LCD module. The administration guide for the box talks about some lan-bypass features. If it has those on some NICs then that can make them appear un-available. Often it is possible to disable that in the BIOS or via jumpers on the board. Steve

o_O Is it really that simple? I'm going to try this tonight when I can create some downtime. Thanks!

What is the model of the card? You may need to use a 2.1.1 snapshot.

I'm having the same exact issue with the same type of hardware : Poweredge 2950. Did you ever manage to get it working? Thanks,

@doktornotor: Yeah, it is solved. As said, do NOT use the broken package. Or get help from whoever has produced it. broken package ?? where to get the right package? and how? thanks

I Steve, I revert my config and now I'm ok. I don't wanna investigate further. My WAN address is public and I'm behind another router with another public ip address. During this period of crash I asked to my provider to change the configuration of their router to act like a "firewall". Now I'm going back hoping that my brand new machin will work like the old one… config seems perfectly ok... cross your fingers.... I hope not to bother you anymore but sound possible.... Thank you very much for your support. Enrico

In that how-to robi does not use a physical NIC for the host-only adapter. The only difference I can see is that he simply sets the pfSense interface to use the existing 192.168.56.X subnet created by VBox. I can't really see why that would make any difference but you could try that anyway. Steve

Nope I mean just re-install the client export package. Go to System: Packages: Installed Packages: and click the button next to the OpenVPN Client Export Utility labeled 'pkg' with an arrow symbol (presumably supposed to look like the recycling arrows or a reload arrow). The mouse-over hint tells you what it does. That's assuming you have installed that package in the first place of course!  ;) Steve

FYI: http://redmine.pfsense.org/issues/972

I figured it out! I created an Alias called InternetforVLANs for all VLAN traffic that require internet. After that I then created a rule to allow Any IPv4 traffic from InternetforVLANs to any destination. I have attached screenshots for those who may have a similar issue. [image: Alias.png] [image: Alias.png_thumb] [image: FirewallRule.png] [image: FirewallRule.png_thumb]

Uhm. Can I know how to set pfsense on router mode? thanks! I can't get my WAN work with my static wan IP.

"it was not uncommon that a specific gateway was way overcrowded " Exactly why I asked if his address space had changed - I have seen this sort of issue as well, where if you were on different address space you were fine, get unlucky and get other and speeds were crap ;)

Thanks!!  I got internet working, and it seems to pass through the router (now switch) via Ethernet, but still can't use it as an AP. Trying to figure it out still. EDIT: Enabled DHCP server on pfSense and all is well in the land (home network)! Networking is not my forte.

Well I am not sure if it was a bug or not.  I am positive that I entered the range correctly at the start, and it is not what I see in the picture.  In any case I have since redone the range via the GUI and it shows correctly in the GUI now.

pfSense is a FreeBSD based distribution. You don't "install" it on top of another OS. It's an OS itself.

Check the PPP log to see how authentication is going; Status/System Logs then select the PPP tab. I use a Cisco 857 in bridge mode.

There isn't a command that I know of. Generally the way to roll back is to save the config, then do a fresh install. After that recover the config from backup. If you don't have the config backed up, do so after every change group you do. :) Seriously though, if you have access to console, use something like winscp (if you have SSH enabled) to copy out the /cf/conf/config.xml file. Reinstall, I would suggest 2.1. I know your having problems now, but it looks like the upgrade was cut short. Then copy the config.xml back in place and reboot.