I recommend you plug a computer into the LAN interface and configure the firewall rule through the web GUI.

If necessary, make le2 the LAN interface (from the console) do your configuration through the web GUI, then reboot and configure le2 as OPT1 again.

Actually, this no longer really applies to the original post.  I'm going to post the new problem in the correct subforum since it isn't related to installation or booting anymore.

I switched to a different PC and am seeing things correctly now on the serial port.

Please don't post unrelated questions in somebody else's topic - start your own topic and it'll be easier to help you without confusion.

When you do that, don't forget to give us more information. All you've said is that "nothing worked" - but not what you mean by that. Knowing all the IP ranges in use would be helpful too.

Hi Aziz, great to haer you got it all working now… so we can conclude it was down to the ACPI?

regards
N.

Thanks for all the responses, I can go on now with my project :-)

when you replay a pcap you have to do it in both directions, usually with two NICs on the same box, one replaying in each direction. You also may need to change things such as the MAC addresses in the pcap, depending on what they were when it was obtained.

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!