Both NICs are on the motherboard.  I don't believe I physically unplugged the server so you may be on to something there.

Does 192.168.100.0/24 somehow conflict with your WAN?

If not, then you have to change your client IP at the same time.  When you change your LAN IP, DON'T HIT APPLY.  Go to Services->DHCP Server.  It will need to be configured to offer addresses in the new IP scheme.  After that, you can go back to the interface and apply the interface changes.  You will then need to somehow make your devices release/renew DHCP.  You can either do this with something like ipconfig /release then ipconfig /renew, unplugging the ethernet for a few seconds and reinserting, or rebooting.

ok this should be in the virtualization section. sorry.
Its working now when i reboot pfsense - i read about this in another thread. Is there any solution to booting pfsense "twice" ? This machine is running 24/7 so its not such a big problem and pfsense isn't rebooted very often.

Hello friend. I just got a industrial grade SSD card from RENICE. The performance is amazing.
And they're now presenting some free CF, SD cards and SSD to Twitter followers http://goo.gl/o9we1A

The Updater checks the URL https://updates.pfsense.org/_updaters/version which is a file that contains the current version info.  Perhaps write a script that grabs it and compares it to your local version file in /etc/version.

First thanks to all.
I solved installing the image with linux command "dd" using the MSATA-USB adapter ( did OK on second try :) )

:D

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.