Indeed, pick the "Boot from USB" option, 3 IIRC, at the boot menu.

Did you restart postfix after your adjustments to the configuration file? (I don't know if this is necessary and don't know enough about postfix to comment on the details of your configuration file.)

Go to this thread and read it. By the way, since your native language is Arabic, you should probably know that "I want to help" means that you want to provide help to someone else.  "I need help" means you want to receive help from someone else.   It's the difference between the verb (action) form and the noun (thing) form.

If you have time, energy and/or resources, maybe try a vanilla BSD install, non pfSense style.  Just to see if there's something that BSD doesn't like about your machine, or something specific to pfSense. List of FreeBSD distributions: http://www.freebsdwiki.net/index.php/FreeBSD-Distros

hi, thanks guys for sharing your ideas and suggestions. I can't wait when i am physically back in the office (cc. 24.9) in order to try suggested options & share back with you all results. Roberto

This is working now.  Not sure what magic caused it to start working, I tried turning off acpi which didn't help, changed mbufs, re-enabled the onboard NIC's, did a few other things and it's working.  Sorry I don't have a better report of what fixed it. Even the jumbo frames is going and happy so I'm happy. Thanks for your suggestions.

OK i figured out the reason the load balancer status for the extra pools was red was simply that they were not assigned to a virtual ip address yet. Once I assigned new virtual ip addresses to point to the secure pools everything turned green  :)

Understood.  Turns out, through some trial and error, it may have been due to a Snort-HTTP DOUBLE DECODING ATTACK.  While I noticed this message in my SYSTEM LOG, it did not appear among the BLOCKED tab.  Only visible among the ALERTS tab.  I've since suppressed this alert rule and it seems to have restored external access to my pfsense box without requiring a reboot. Will monitor my system since suppressing this rule to see whether it recurs in which case it may be attributed to snort (possibly). I think the HTTP DOUBLE DECODING ATTACK may have been the cause as once I cleared it, I was able to access my Web GUI login page from multiple external systems originating from multiple different internet IP addresses (without clearing any blocked IPs from the snort blocked tab).

Good idea - I actually have another near duplicate system in my spares pile.  I'll set up 1.2 on that, load the config backup, then upgrade to 2.0.1 and swap the ethernet cables.  That way if I manage to overlook or break something during the upgrade I can switch back to the existing setup by just swapping cables. Thanks for all your help!

What did you upgrade from? How did you upgarde? The Firebox X (X500, X700 etc) has an issue with the serial console not showing the menu after boot. This has been a problem since around 2.0 Beta5 though. It can easily be worked around by setting the serial port speed to something other than 9600. In 2.1 there is an option to do this in the webgui, however you can't access that!  ::) Steve

Got it fixed. Had to make: loader.conf.local and add: hint.apic.0.disabled=1 On reboot, it works fine in normal mode. Safe mode disables a few more things like DMA, APCI, SMP, and hdd caching.

@cyclone3d: I also need to know if it is possible to: 1. Set IP according to MAC address In pfSense DHCP can assign a fixed IP address determined by the MAC address of the DHCP client. @cyclone3d: 2. (This one is kinda strange and hard to understand, but I will take a stab at it) - If a user has a specified IP by MAC address, and the user changes their IP, disable(block) that user. If a user is smart enough to change the IP address they are probably smart enough to change the MAC address. If you are worried about such users it would be better to put them on a separate interface (or interfaces) and use firewall rules to restrict access.

install the shellcmd package and set it up as a shellcmd, which gets executed during the boot process.

Are you sure that you don't have a keylogger on the system you are accessing the pfsense web GUI with? Could be that your system is compromised and somebody is changing your passwords without your knowledge.

Well, thanks for at least looking into it… :)

@asura: thanks i will give a try .. by the way ..i installed pfsense 2.0.1 on 500gb harddisk its stuck at boot screen. Screen only show me : F1 pfsense F6 PXE Boot: F1 \ mayb pfsense 2.1 will support my 500gb harddisk? thanks :) edit: with one shud i download? 1- pfSense-LiveCD-2.1-BETA0-i386-20120828-1442.iso.gz 2- pfSense-LiveCD-2.1-BETA0-i386-20120828-0823.iso.gz 3- pfSense-LiveCD-2.1-BETA0-i386-20120903-2218.iso.gz If you press ther F1 key on your keyboard, it should then continue to boot.

Thanks for that. That sounds like quite a handy feature, and good to know for the future.

It's been discussed many times here on the forum, list, etc. It's a security risk, and also unnecessary bloat. If you need more detail than that, search around on here and it'll turn up.

thanks!