Upgrading to 2.1 is easy to do, there's a link on the dashboard that informs you an update is available. You will have to attach your WAP directly if you have only two NICs. You can probably add another NIC easily enough or you can use VLANs to add interfaces if your switch supports it. Unless you have to I wouldn't try adding unify to pfSense. There have been many reports of problems and not many (any?) of it working perfectly. Mostly it seems to run incredibly slowly for some reason. If you only have one access point there not much point anyway. Steve

thanks, will attempt it.

Ah interesting. This is explained here: https://www.freebsd.org/doc/handbook/serialconsole-setup.html Specifically: The boot loader will determine whether the internal video or the serial port should become the console by examining the state of -h. This means that if -D is specified but -h is not specified in /boot.config, the serial port can be used as the console only during the boot block as the boot loader will use the internal video display as the console. It seems as though the Netgate box is setup for dual console (special image) and that somehow in restoring your old config file you ended up removing some part of that setup. Not sure how though.  :-\ Steve

Your WAN subnet mask is wrong, it's way too big. That mask means you're telling the system that 66.216.34.x block we have is local to your WAN subnet, which it of course isn't. Fix the subnet mask on WAN to the appropriate value as provided by your ISP and you should be good.

So you booted from the a pen drive with the memstick install image on it and used that to install the full version of pfSense onto another pendrive? You may have killed the pen drive if it's low quality. If you haven't you probably will trying to run Squid from it unless you disabled it's caching features. I was hoping to see the names of your interfaces as listed by ifconfig. Steve

Dude a domain with a _ is not standard, not support - CHANGE IT!! Make whoever came up with the bright idea to use a _ in a domain do the work ;) Other option is use something else that supports _ in the name for name resolution and dhcp, etc.  Are you on a MS Active Directly domain?  If so none of your machines should be pointing to pfsene for dns or getting dhcp from pfsense in the first place.

Win32 Disk Imager works well. Steve

That's unlikely to work since /dev/da0 is not a listed device. You have copied the image to /dev/vda but that is also not a GEOM recognised device. The only thing recongnised is a CD-ROM drive. Is that the virtual drive from the hypervisor? Steve

Best way to learn in my opinion.  :) So it didn't work then? The only packages you are adding are gutenprint-cups py26-cups. Neither of those specify a version so the most recent will be installed. The only conflict might be with the pfSense Avahi package which might include older components. What erros are you seeing? pfSense was never intended to be a print server, others have added the functionality but unless it's added to the project in some official way it's always at risk of becoming outdated. Steve

Thank you.  That did it I just changed the boot path to the correct device name and that fixed it. Marty

Figured out the issue in the end.  Checked the logs straight after trying to download the list of available package and noticed the following errors: php: /pkg_mgr.php: XML_RPC_Client: Connection to RPC server www.pfsense.com:80 failed. Operation timed out 103 php: /pkg_mgr.php: XMLRPC communication error: Operation timed out Googling these errors landed me at the following wiki page: https://doc.pfsense.org/index.php/Controlling_IPv6_or_IPv4_Preference By preferring IP V4 with the following command: env ip6addrctl_enable="yes" ip6addrctl_policy="prefer_ipv4" /etc/rc.d/ip6addrctl start i was able to download and install packages!

We'd have to know more details about the LCD module in that box. I believe there have some similar questions on the forum though. Try searching. There is (or was) a Nexcom driver in the lcdproc package but I don't know which models it was designed for. Steve

How are you testing the pfSense box's connectivity? Do you have any custom firewall rules in place or just the default LAN to any rule? Two things that can cause this: The pfSense box will always use the system routing table where as connections from downstream clients can be directed to a particular gateway. If the default gateway is wrong or not present that can give these symptoms. If the pfSense box has IPv6 connectivity it can default to trying to use that. If that connectivity is not correct that can show as this. Try: https://doc.pfsense.org/index.php/Controlling_IPv6_or_IPv4_Preference Steve

thanks for your help jimp but i have a problem and that is this: Some of files of packages is filter for me and these not in my access so i can not install some package on pfsense. How i install this packages? Can i get packages from installed packages on another pfsense that it access is full?

It's time to move on from that device. :-) Even if you manage to get it to boot, you're going to have a bad time. 128MB may have been good on 1.2.x and passable on 2.0.x, it's not really sufficient for 2.1. The WRAP has been EOL for many years for good reason.

I think I have this figured out. When I first installed I gave it an IP on another subnet, thinking I would use that IP as the management IP, since it will be a transparent bridge. The machine seemed to cache that IP number and attempted to set the wrong default gateway, which I found had failed in the logs. I removed the second IP from the configs, and the gateway, and it seems to be working now.

Hmm, not too sure what to suggest here. Normally the boot loader should timeout and automatically select F1. Quite why it isn't I don't know. Have you changed anything in the box since you installed, like perhaps added or enabled something that provided the PXE boot option? You could try this: https://doc.pfsense.org/index.php/Remove_F1_Boot_Prompt That carries some risk though. Make sure you know which disk you're using! Steve

Ok so thats pretty embarrassing even by my standards  :-[ Thanks Steve