Could someone take a look at these logs from the packet capture (I picked an interface and then on a local device attempted to go to google.com): WAN Interface 16:57:41.101959 IP 75.144.79.144.13192 > 74.125.225.78.443: tcp 0 16:57:41.108078 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 23150, length 44 16:57:41.125294 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:41.144520 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 23150, length 44 16:57:41.455705 IP 10.0.0.0 > 224.0.0.1: igmp 16:57:41.580017 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:41.664690 IP 75.144.79.144.3756 > 74.125.225.78.443: tcp 0 16:57:41.685577 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:42.039584 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:42.118017 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 23406, length 44 16:57:42.149849 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 23406, length 44 16:57:42.180303 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:42.638573 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:43.128024 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 23662, length 44 16:57:43.161202 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 23662, length 44 16:57:43.380435 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:43.838306 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:43.995745 IP 75.144.79.144.39147 > 74.125.225.70.443: tcp 0 16:57:44.017177 IP 74.125.225.70.443 > 75.144.79.144.39147: tcp 0 16:57:44.098672 IP 75.144.79.144.13192 > 74.125.225.78.443: tcp 0 16:57:44.120593 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:44.137956 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 23918, length 44 16:57:44.170392 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 23918, length 44 16:57:44.383626 IP 74.125.225.70.443 > 75.144.79.144.39147: tcp 0 16:57:44.664647 IP 75.144.79.144.3756 > 74.125.225.78.443: tcp 0 16:57:44.685868 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:44.699328 IP 75.144.79.144.36950 > 74.125.225.68.443: tcp 0 16:57:44.722696 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:44.728673 IP 75.144.79.144.4217 > 74.125.225.70.443: tcp 0 16:57:44.749215 IP 74.125.225.70.443 > 75.144.79.144.4217: tcp 0 16:57:44.966891 IP 75.144.79.144.32177 > 74.125.225.68.443: tcp 0 16:57:44.988638 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:45.147931 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 24174, length 44 16:57:45.180448 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 24174, length 44 16:57:45.182179 IP 74.125.225.70.443 > 75.144.79.144.4217: tcp 0 16:57:45.184711 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:45.410414 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:45.781167 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:45.783714 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:46.010282 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:46.157899 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 24430, length 44 16:57:46.190517 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 24430, length 44 16:57:46.237759 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:46.691304 IP 75.144.79.144.38380 > 173.194.68.125.443: tcp 0 16:57:46.734180 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:46.941749 IP 75.144.79.144.33876 > 173.194.68.125.443: tcp 0 16:57:46.982674 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:46.983864 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:47.128039 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:47.167852 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 24686, length 44 16:57:47.202763 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 24686, length 44 16:57:47.210433 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:47.282514 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:47.700973 IP 75.144.79.144.36950 > 74.125.225.68.443: tcp 0 16:57:47.723263 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:47.729600 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:47.882395 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:47.961005 IP 75.144.79.144.32177 > 74.125.225.68.443: tcp 0 16:57:47.982889 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:48.116661 IP 75.144.79.144.26289 > 75.75.76.76.53: UDP, length 28 16:57:48.116694 IP 75.144.79.144.26289 > 8.8.8.8.53: UDP, length 28 16:57:48.116721 IP 75.144.79.144.26289 > 8.8.4.4.53: UDP, length 28 16:57:48.116746 IP 75.144.79.144.26289 > 75.75.75.75.53: UDP, length 28 16:57:48.132922 IP 75.75.76.76.53 > 75.144.79.144.26289: UDP, length 204 16:57:48.136766 IP 75.144.79.144.17085 > 74.125.225.130.80: tcp 0 16:57:48.153083 IP 8.8.4.4.53 > 75.144.79.144.26289: UDP, length 204 16:57:48.153130 IP 8.8.8.8.53 > 75.144.79.144.26289: UDP, length 204 16:57:48.164292 IP 74.125.225.130.80 > 75.144.79.144.17085: tcp 0 16:57:48.167216 IP 75.75.75.75.53 > 75.144.79.144.26289: UDP, length 204 16:57:48.177827 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 24942, length 44 16:57:48.209769 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 24942, length 44 16:57:48.456216 IP 10.0.0.0 > 224.0.0.1: igmp 16:57:48.549640 IP 74.125.225.130.80 > 75.144.79.144.17085: tcp 0 16:57:48.930197 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:49.084248 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:49.149509 IP 74.125.225.130.80 > 75.144.79.144.17085: tcp 0 16:57:49.187781 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 25198, length 44 16:57:49.221121 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 25198, length 44 16:57:49.385864 IP 74.125.225.68.443 > 75.144.79.144.36950: tcp 0 16:57:49.611598 IP 74.125.225.68.443 > 75.144.79.144.32177: tcp 0 16:57:49.695145 IP 75.144.79.144.38380 > 173.194.68.125.443: tcp 0 16:57:49.741328 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:49.945167 IP 75.144.79.144.33876 > 173.194.68.125.443: tcp 0 16:57:49.987475 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:50.108172 IP 75.144.79.144.13192 > 74.125.225.78.443: tcp 0 16:57:50.135905 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:50.197745 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 25454, length 44 16:57:50.229454 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 25454, length 44 16:57:50.351753 IP 74.125.225.130.80 > 75.144.79.144.17085: tcp 0 16:57:50.583027 IP 74.125.225.78.443 > 75.144.79.144.13192: tcp 0 16:57:50.668264 IP 75.144.79.144.3756 > 74.125.225.78.443: tcp 0 16:57:50.691144 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:51.040863 IP 74.125.225.78.443 > 75.144.79.144.3756: tcp 0 16:57:51.139318 IP 75.144.79.144.17085 > 74.125.225.130.80: tcp 0 16:57:51.160980 IP 74.125.225.130.80 > 75.144.79.144.17085: tcp 0 16:57:51.207707 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 25710, length 44 16:57:51.242954 IP 8.8.8.8 > 75.144.79.144: ICMP echo reply, id 46666, seq 25710, length 44 16:57:51.332369 IP 173.194.68.125.443 > 75.144.79.144.38380: tcp 0 16:57:51.484095 IP 173.194.68.125.443 > 75.144.79.144.33876: tcp 0 16:57:52.217676 IP 75.144.79.144 > 8.8.8.8: ICMP echo request, id 46666, seq 25966, length 44 ------------------------------------------------------------------ LAN Interface 16:58:53.524036 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.664922 IP 192.168.0.200.64336 > 74.125.225.134.443: tcp 0 16:58:53.723976 IP 192.168.0.200.64343 > 192.168.0.99.80: tcp 0 16:58:53.724061 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.724063 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.724594 IP 192.168.0.200.64343 > 192.168.0.99.80: tcp 0 16:58:53.724628 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.724630 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.724632 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.724634 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.725108 IP 192.168.0.200.64343 > 192.168.0.99.80: tcp 0 16:58:53.725146 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.725148 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.725150 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 1460 16:58:53.725152 IP 192.168.0.99.80 > 192.168.0.200.64343: tcp 495 16:58:53.725640 IP 192.168.0.200.64343 > 192.168.0.99.80: tcp 0 16:58:53.733891 IP 192.168.0.200.64337 > 74.125.142.125.443: tcp 0 16:58:53.983895 IP 192.168.0.200.64338 > 74.125.142.125.443: tcp 0 16:58:54.229110 IP 192.168.0.200.50855 > 192.168.0.99.53: UDP, length 33 16:58:54.246739 IP 192.168.0.99.53 > 192.168.0.200.50855: UDP, length 49 16:58:54.455911 IP 10.0.0.0 > 224.0.0.1: igmp 16:58:54.907004 IP 192.168.0.200.64339 > 74.125.225.32.443: tcp 0 16:58:55.137092 IP 192.168.0.200.64340 > 74.125.225.32.443: tcp 0 16:58:56.767269 IP 192.168.0.200.64341 > 74.125.225.131.443: tcp 0 16:58:56.987238 IP 192.168.0.200.64342 > 74.125.225.131.443: tcp 0 16:58:57.843056 IP 192.168.0.200.64350 > 74.125.225.130.80: tcp 0 16:58:58.612801 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:58:59.014081 IP 192.168.0.200.64351 > 74.125.225.134.443: tcp 0 16:58:59.363421 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:58:59.773368 IP 192.168.0.200.64352 > 74.125.225.134.443: tcp 0 16:59:00.113507 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:59:00.843563 IP 192.168.0.200.64350 > 74.125.225.130.80: tcp 0 16:59:00.910479 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:59:01.455647 IP 10.0.0.0 > 224.0.0.1: igmp 16:59:01.660603 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:59:02.013532 IP 192.168.0.200.64351 > 74.125.225.134.443: tcp 0 16:59:02.410700 IP 192.168.0.200.137 > 192.168.0.255.137: UDP, length 50 16:59:02.773546 IP 192.168.0.200.64352 > 74.125.225.134.443: tcp 0 16:59:03.163869 IP 192.168.0.200.52811 > 192.168.0.99.53: UDP, length 37 16:59:03.182386 IP 192.168.0.99.53 > 192.168.0.200.52811: UDP, length 106 16:59:03.187650 IP 192.168.0.200.64354 > 207.46.206.137.80: tcp 0 I don't care about hiding the external IP anymore…. I'm not going to be using it for long.

That's what happens when the firewalls can't talk to each other on the WAN, or at least can't pass multicast between them on the WAN though usually it's that they can't talk at all.

Sorry I got confused between threads. You are not running pfSense in a vm so you can't copy and paste from the console. To run ifconfig go to the console menu select option 8, shell. Then type 'ifconfig' at the command prompt. Confirm that your lan interface is UP and the media status is autodetect. Steve

Problem is that the AP just has 1 lan port and I know you can do vlan tagging but can't to figure it out. So I hoped someone already had done this kind of install.

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.