With a standard pfSense you won't be able to do it.

If both websites are on the same physical server, running under the control of a single web server (eg. Apache), then virtual host configuration will be able to handle it.

If you have physically different servers (eg. 192.168.1.2 and 192.168.1.3), then you will have to set up some kind of proxying facility. You can use a third box (ugh), or install something like ffproxy, varnish, or mod_proxy on Apache on one of the servers.

If you go for the second option (recommended) then you'll forward all incoming HTTP requests to this box and the proxy will have to analyse the "Host" header on the incoming HTTP requests and route it to the relevant web server.

and root instead of admin

Could it be a problem with the MTU? Maybe try reducing the MTU on the client interface on pfSense. Something just a little lower like 1492.

@chpalmer:

Go to "System- Advanced- down to Network Address Translation - Uncheck "Disable NAT Reflection".   Id reboot the box to make sure it takes but you may not need to…

My box is still set to port 80. I see my webserver fine by looking at my domain name...

awesome.  just had the same problem and this fixed it immediately…and a reboot wasn't necessary.  thanks!

I see a FreePBX is one of them, which ISTR can be configured as a SIP proxy, which is probably what we want..

Call Center Software

are you using a wireless AP that your hosts are connecting through? i had this same exact problem and it turned out to be my wireless access point. once i connected my hosts directly to the switch i could access all my pages as normal…

Well, I'm afraid this is not an option as the network contains web servers with "unknown" SMTP senders, so we would not know who to block and not to block.  This is why we are looking at the "SPAMBLOCKER" route for outgoing traffic.

You should not be running pfSense 2.0 in production.  It is labeled an "alpha alpha alpha" release and is not suitable for any sort of production use.

oh really? Ok, I will have to give it a try then.

Thanks!

I simply make firewall rules to allow the sip server access and no port forwarding involved…

oh yeah, duh. i forgot that it they are connected with cat 6 but to a 10/100 switch. thanks for pointing that out!

Well the new fix was tested for more than 700 users and it behaved really well.
Even the status->CP was fixed to be usable under load.

It is better to get a snapshot rather than the 1.2.3-RC1 that is in the mirrors cause they might not have updated the new image with the fixes.

Not saying this is always the case, but typically random weirdness of that nature is indicative of hardware issues.

If you can get to a shell, running top -S might help figure out what is taking so long. Pay particular attention to RAM usage.

I'm not sure if it works during the boot process, but pressing Ctrl-T should print on the console what the current active process is when you're waiting on it.