it works the way you configure it, there are no issues in rules

It seems to be memory issue, thanks!

You list 8 public IPs, do you have a /28 or larger? A /29 would only allow you a max of 6 IPs. If so, do you NEED a public IP on the servers themselves or will 1-1 NAT work? I know HTTP and FTP generally work fine with 1-1 NAT but Voip can be troublesome. If you can do 1-1 NAT then put both pfsense boxes on the WAN switch and they will both get a public IP. From there you would assign IPs via 1-1 NAT mappings to the various servers. This will still keep them protected by a firewall but of course hinges on that big 1-1 NAT issue. Otherwise I think you can do your original plan, you will want to turn off NAT and do manual static routes most likely. As for the services I'm not sure what is available besides snort.

I presume you have tried to add the interface rl2 from the web GUI by Interfaces -> (assign) Interface assignments tab then click on the + toward the bottom of the screen. There might have been an error detected on startup on rl2. Please post the output of the pfSense shell command # dmesg | grep rl.

First thing to check is that all your cables are good. Do you have led indicators on the switch? Are they lit to show connections correctly? You have two choices: 1. Keep your router/switch as a router and have it conneted to pfsense via it's wan port 2. Use you router/switch purely as a switch and have pfsense handle everything else. Neither are ideal. In case of 1 you will have double NAT which is usually fine but can cause problems. In 2 you are assuming that you can disable the routing functions of the switch. Since you have tried both unsuccessfully you need to ensure that the pfSense box is functioning correctly. How did you set it up? Directly on the box keyboard/monitor? Have you tried connecting a computer directly to the pfsense box? Traditionally you would need a cross over cable to do this but most modern NICs have auto MDIX so it might work. Steve

The change of ISP provider is a 1-3 sec thing. working with city fiber networks.

Yes you can use it.

Thank you very much jimp  ;D !!! In fact, i had a remember (at least in a previous pfSense version) to need to backup manually EasyRSA files, etc.. But, didn't think about the upgrades done on 2.0 :) ! Thank you : i tested & it worked like a charm :) ! Sincerely, XZed

Well, I upgraded from pfSense 1.2.3 to the latest snapshot. It was very easy and all is working great. I love the new psSense! I accessed my existing pfSense gui and upgraded to the latest snapshot. It was painless and fast. Everything seemed to work perfectly. What can I say, I like fresh installs, because it makes me feel good and I know that there aren't any misc or ill configured files hanging around that might mess things up. So I exported the config.xml file to my computer, performed a fresh install of the latest pfSense snapshot, and then uploaded the config.xml saved earlier. All is great and easy! Looking at the config files of 1.2.3 and the 2.0 snapshot, I can see the differences. All I can say is… NO PROBLEMS! Yeah!

The general lack of memory on the WRAP will hinder it quite a bit with 2.0. It might work, but just barely so.

Have you tried the USB memstick image instead of the CD? Either way, in order to say anything we'd need a capture of the panic message, a picture or some other way. If you get a db> prompt, type "bt" there and capture that output also

You wouldn't be able to use the WAN address for the GUI without firewall rules and/or NAT translations in place. I'm not too familiar with the VMware side (use Hyper-V mostly), do you have the right interface (LAN and WAN) assigned to the right network card? They should still be separate physical cards unless you have some special config or are trying to use VLANs. FWIW I had this exact problem with a 2.0BETA5 build on a firewall I built back in January. After several attempts and reinstalls I grabbed a current snapshot and it worked just fine. Not sure what the problem was, I had used the disc before with no problem so I don't think it was a bug in a snapshot nor do I think it was the disc. I was trying to access it plugged in to the wifi AP with my desktop on wireless but when that didn't work I pulled the firewall to my desk and used a small switch and made my own LAN (on a different range) and still no luck. So all that said, are you using a 2.0 build or 1.2.3?

Can you point me in the right direction for hand editing the config? Is there information on how to do this? I would assume I burn the image to the USB and then modify? I know the NIC assignments, just need help with pre-modifying this config

I have a load of asphalt and a local permitting system that's a pain in the butt to deal with in the way of using something wired. I have basically 10 days to get this working (they're moving on the 30th) and one of the IT guys at one of the companies has a pile of old WRT54G v3 routers running dd-wrt, so I'm thinking I'm going to build a directional antenna bridge with those and call it a day.

If you can get to the console you can get the LAN IP. If the GUI doesn't respond on the LAN side either your LAN has a problem (or the workstation you used to attempt a connection has a problem) or pfSense itself has a problem, either of which could be the cause of the problem for your client. I too am not sure what you mean by "changed WAN IP to online active system". That almost sounds like you had a static IP configured and now they are providing you with something like PPPoE or DHCP for the IP and the static IP you had configured is no longer valid.

@Snowman58: Worked great. Spoke too soon, the boot hangs after: "ppc0: SPP ECP". Searched the forum, but did not find any relevant threads. Solved the hanging problem - Changed parallel port in BIOS to STD. But now getting Error Messages:   GEOM: ad0s1: geometry does not match label (255h,63s != 16h,63s) Off to search for new error messages!