I now have wifi with pfsense. It was something from comcast blocking they said. I now cannot login to pfsense still with 192.168.1.1 the machine is working and allowing internet. I would like t add packages now :D

@nicolaih: Turned out to be quite simple. I downloaded the newest development version of the NanoBSD, the first one I downloaded was without VGA so it didn't work very well. With the NanoBSD there is no need to install anything, there isn't even an 99 option in the menu. Also I was using USB 3.0 ports, so that might be why I couldn't make the install from the memstick image. Thank you Jason! No problem.  The 2.2 snapshots might actually work in the USB 3.0 ports, I haven't tested it yet.

Worked fine for me once the correct images were in place. Worked fine before that if you specified the correct image at the cli. I haven't tried a nano+vga image personally though which the OP may well be running. Steve

No.

Enjoy.  Let me know when its up (-:

Thank you very much. Exactly what I needed :) I know it does it automatically, but I want to check it from PRTG (www.paessler.com)

I know it is been a long time, that is why I'm asking is anyone configured above settings? if so please share how u did it thank you!

Buy a USB to mSATA adapter and get an image for pfsense for that device and size drive and image it to the msata maybe… I'm not a serial interface loving guy.

Ipv4/v6 issue can cause update check failure. https://doc.pfsense.org/index.php/Controlling_IPv6_or_IPv4_Preference Could it be ipv6 enabled sites that are loading slowly? Steve

Ah, OK that's the config file version not the pfSense version. The most recent version is 10.1 so I guess your backup file is quite old! Where are you testing the port forward from? To test it correctly you need to be coming from an external public IP address. Otherwise: https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks Steve

http://en.wikipedia.org/wiki/X86-64 Blame Intel for using AMD's specifications for a change. :-)

@larynx: Seems like the pfSense 2.2 snapshot works, I guess I'll use that for now and upgrade to the stable release when it comes out. Good to hear it works for you!  If you run into any bugs or unexpected features, post them over on the 2.2 testing forum.  Response has been pretty quick in fixing bugs as they are posted.

Ok it still hangs. At least it is 'reproducible' not sure if that is a good thing, but does help for diagnosing the issue.. As for the xml part, what you posted is ok, but i was asking for another part which looks like what i post below starting and ending with <haproxy></haproxy> , as the configuration itself is probably somehow not upgrading the proper way.. There could be some information in there that you do not want 'visible' for everyone to read though..: <haproxy><logfacility>local0</logfacility> <loglevel>warning</loglevel> <maxconn>600</maxconn> <ha_backends>..also include this info..</ha_backends> <ha_pools>..also include this info..</ha_pools> <nbproc>1</nbproc> <remotesyslog>192.168.0.40</remotesyslog> <localstats_refreshtime>5</localstats_refreshtime> <localstats_sticktable_refreshtime>2</localstats_sticktable_refreshtime> <localstatsport>2200</localstatsport> <enable><ssldefaultdhparam>2048</ssldefaultdhparam> <log-send-hostname></log-send-hostname></enable></haproxy>

When I go to restore from the GUI, I am running 2.1.4 BTW, I assign all the interfaces correctly and then click save.  The firewall proceeds to reboot and then hangs.  If I connect to the console, I see that it is stuck at an interface assignment prompt. It asks me if I want to configure VLANs and I select N and then it prints out my current correct VLAN assignments.  It then asks for WAN interface assignment which I already did in GUI.  I set it to re1 any way and then hit enter to not configure any more interfaces. It then loads to the CLI menu and only shows the WAN interface as being setup. Any way I can manually edit a file to set the correct assignment?

This has been covered to death in 10+ different threads in several subforums, mainly the WebGUI forum. 1.  Clear your cache, or 2.  Reload with Ctrl-F5, or 3.  Reduce your font size, or 4.  Install the Widescreen patch -> https://forum.pfsense.org/index.php?topic=81167.0

Huh?

I will check it out.  I did notice that Snort did an update to the rules and it looks like this is what was happening.  Yes it is strange that I never got this before, so it must have been the Snort update causing the issue.  It was just a matter of timing in this case.  The suppress that I did worked, so all is good and everything else with 2.1.5 upgrade is good, so i am happy.