@stephenw10:

@stephenw10:

Hmm, confusing indeed. It looks like the console itself is not failing rather the shell is. The only vaguely similar thing I have seen is where the menu fails to spawn completely at the end of boot and you're left with no prompt at all. There were a few workarounds in that case. One was to simply change the serial baudrate. Seems unlikely to make a difference here but it's an gui setting now so an easy test. For example:
https://forum.pfsense.org/index.php?topic=34814.0
Could try running at the #:

/etc/rc.initial

Not entirely sure what that might do to an already running system so probably best not to do it in 'production'!

Steve

I previously had the baud rate set to 9600 (default), but my ALIX BIOS uses 38400 … so a few weeks back I switched it to 38400 on pfsense as well.

In my case the menu does spawn on boot, but dies some hours later.  Each time (in this thread) I've said I rebooted my ALIX, I did verify I had a workable menu on the serial console.

I just tested running /etc/rc.initial from the serial console ... which so far appears not to have any ill effects (though I'm typing this up a few minutes after running it!).  And restores the serial console menu.

[2.1.5-RELEASE][admin@fw0.localdomain]/root(4): date Sat Oct 11 18:17:45 EDT 2014 [2.1.5-RELEASE][admin@fw0.localdomain]/root(5): uptime 6:17PM  up 25 days, 19:33, 2 users, load averages: 0.00, 0.00, 0.00 [2.1.5-RELEASE][admin@fw0.localdomain]/root(10): ps auxff | grep rc.init root  83274  0.0  0.6  3644  1512  u0  I+    6:11PM  0:00.02 /bin/sh /etc/rc.initial root  36527  0.0  0.4  2444  1060  0  R+    6:21PM  0:00.00 grep rc.init root  80618  0.0  0.5  3644  1320  0  Is    6:11PM  0:00.02 /bin/sh /etc/rc.initial

@MaxPF:

@MaxPF:

<…snipped...>

I removed [SOLVED] from the title.

Thanks Max!
I'll continue to use this thread at this point.

@Rewt0r:

The firewall was rejecting the packets until I forwarded the packet using a forward rule even though I already had a firewall pass rule and a nat 1:1.

Then your firewall rule was wrong, NAT applies first, private destination is probably what you missed.

sorry… the script is /etc/rc.initial. Change the shell under option 8 to bash.

To me, its not clear what you are asking?

If you are asking can pfsense be ran as a VM in any of those OSs you listed, the answer is yes.  All of them, under vmware.

Well, I figured it out.

I was using a usb ethernet device with the MCS7830 chipset, that I had to load the kernel module to get recognized.  From here:
https://forum.pfsense.org/index.php?topic=50241.0

It did recognize it, I could configure it and everything, but it just didn't work.  I pulled an old pci ethernet card out of the junk box and now everything works just fine.

thanks everyone

details can be found here:
https://redmine.pfsense.org/issues/2770

@imanz:

I just wanted to let you know that it is working correctly after the change. Thank you for the quick response. Not that install and basic configuration is complete I will move on to correctly setting up all the subnets; will probably be back with more questions :)

An OT question. Since I just installed pfSense 2.2.Beta on a similar set up, same board, same amount of RAM but using an INTEL S3500 SSD 80GB.
I am using a M350 case, 1 Noctua Fan (40x40x10) blowing from the upper case directly to CPU and RAM.

Can you kindly report your operation temperatures, case used and fans (number, position and flow direction)?

Thanks

Firewall Log DNS Lookup Dialog Box Missing in 2.1.5
https://forum.pfsense.org/index.php?topic=81145.0

Pentium 4 chips were all single core with Hyper Threading.  They changed the name to include a "D" when they made them dual core.  Truth told though, HT was a liability on those original chips.  In many workloads they actually performed better if you disabled it.

1 - you should be able to give LAN devices a static IP like 192.168.1.2 up to 199, set its gateway and DNS to 192.168.1.1 (pfSense LAN IP) and it will have internet. The default LAN to any rule will allow all LAN addresses out.

2 - you need to port forward on each modem - since pfSense itself is a firewall, I usually just take the "port forward all" option on front-end devices. Often they cal it "DMZ" when actually it is just an internal private IP address to forward all traffic to. This way you do that on all 4 front-end devices 1  time only (no need to go back opening extra ports in future0. From a security point oof view it is nno different to bridging the front-end device through to pfSense. In both case all incoming connects (friendly or otherwise) arrive at pfSense.
Then use pfSense as you normally would to port forward into your server/s.
You will then want public DNS name/s that point to your public IP/s and have them point to a suitable list of your public IPs if you want outside users to be round-robin connected to your various public links…

3 - the firewall is already enabled. By default clients on LAN can start outgoing connections to internet resources, and all incoming connection attempts are blocked. Put pass rules on wan1-4 to allow what you want.

You could argue that the actual problem here is an underlying requirement to re-write the gui. That's a topic for another day.  ::)
Your problem is almost certainly that you're running a Linux based OS and you've installed some Miscrosoft fonts. They have have been included in your distro or been a added as a requirement of some other package you installed. The key is that with no MS fonts installed it displays fine. With all the MS fonts installed (including Tahoma) it displays fine. However if you have only the basic package(mscorefonts) it tries to use Verdana which doesn't fit.
See: https://forum.pfsense.org/index.php?topic=81049.msg443393#msg443393

Either remove all MS fonts or install Tahoma.

Steve

lol , you are right about the font size .
I don`t know why i did not remind myself of that !!!
the gold item still have the same error , but i am not worried about it because my firewall is installed in my personal system , and since this here is not a company or a corporation then there is no need for 24h/7 support .
thanks for the tip ;)

You should start a new thread for this unless your setup is exactly the same as the OP.

Steve

Nice. Ware your t-shirt with pride.  ;D

Stevd

Trick for my machine (a while ago) was changing the SATA ports from AHCI to "Legacy" in the bios. So, more things to look at there than just "turning stuff 'off' "

I'm often out of touch…

On the off hand chance that it works, I'd love to know how well it works.

Morbid curiosity.

Both NICs are on the motherboard.  I don't believe I physically unplugged the server so you may be on to something there.