I have live migrated the good pfsense installation (from the second Debian host without LVM) to the first Debian host with LVM (which was having installation problem).  After a reboot of the pfsense guest, there was some some disk error which leads to kernel panic. This was solved after I ran fsck.  Now the guest pfsense is running ok.

Attached is the pfsense crash report after the live migration.

pfsense-crash.txt

I just wanted to follow-up on my own thread to let anyone in the future know that I've resolved this issue.  I have been able to get the transparent firewall up and running with just 2 interfaces, the LAN port set to type "none" as cmb suggested, the WAN port is still a static ip address port.  I still haven't tried the LAN, Any rule yet that wallabybob suggested to allow all traffic on the local network through; I'm still using the manually added rules in the firewall to get traffic out.

The ssh requirement I posted about is also working, I just had to make sure the port forwarding on my gateway was pointed to the correct address/port.

FreeBSD also won't partition the drive.

LBA set in BIOS causes errors, can't format.
Auto it sees the drive but cannot format, errors.

m0n0wall will have issues with both NICs on the same subnet as well, but such issues with both are intermittent generally, you're lucky if that didn't break with m0n0wall. It's not a valid or useful config anyway with any router or firewall.

sounds like you don't actually have a default gateway ("no route to host" indicates as such), though the other thing you pasted, "ping: sendto: Host is down" indicates a wrong subnet mask somewhere, or a wrong route. That indicates it can't ARP the destination host, which it won't ever attempt for an Internet-reachable host unless you do something crazy like assign a /1 mask to an interface or similar. It may also do that if it can't ARP the route for that network.

I ended up figuring it out.  It was a combination of a lot of things (rules, gateways, ips in general, etc) :D

More than 4 Gbps is out of my scope since I have 4Gbits static aggregated links between core switches. Not more. And this is more than enough..

Only thing I have tested so far was 2 x Quad Gigabit adapters teamed as single 8Gbit LACP and was fine to accepct many client connections.

update: can any admin move this thread to join into http://forum.pfsense.org/index.php/topic,7668.msg122803.html ?
(probably not :()

I take it that output is from the serial console?
It's a known bug. There are several work arounds, this is the one I used: http://forum.pfsense.org/index.php/topic,7458.msg241783.html#msg241783

Of course to do that you need access to the box. If you have setup the interfaces on the first boot, it looks like you have, you should be able to connect to the web GUI on LAN.

Alternatively you can try mounting the CF card under OSX and editing the files there.

Steve

It's still a capable box, like you say easily able to keep up with an ADSL connection.
The Pentium 3 Tualatin was a highly efficient CPU, when the Pentium 4 was introduced many people saw it as a backwards step. The actual CPU in the X-Core is a 1.2GHz Celeron but it has the same architecture. It uses about the same power as the X-e but has less processing power. Don't dismiss it yet.
There are many users who have no trouble with the Realtek NICs. It does seem to be largely dependent on what they're connected to but no hard facts have been established.
It's shiny and red!  :)

Steve

Thanks, I changed on the BIOS and the installation continued. I removed the LIVEcd but it seems stuck on the configurations it doesnt get to the web interface

@stephenw10:

The first thing to check is that your updater settings are correct.
Go to System: Firmware: Settings: in the WebGUI.
Select one of the 'Default Auto Update URLs'.
Make sure you select the correct one, i386 for 32bit amd64 for 64bit, for your system.
Don't select the development snapshots unless you really want that.  ;)

Steve

It worked. I though I tried that before though.
Thank you very much.

Did you notice the output you posted shows an incomplete copy to the output device?

Maybe it is broken and you need a new flash drive.

if you couldn't run the 64 bit version, it wouldn't boot. There is no config diff between 32 and 64 bit.

Thank you is solved.

;D

Thanks for the reply guys. I was aiming for a fresh full installed. It turned out to be quit easy. I did not even had to filddle around with /etc/fstab…

Well I figured it out - turns out there was an entry in Snort's Blocked list for the pfSense.org IP address.  Removing that and I was able to access the site.  That said, why if Snort was disabled on the WAN interface would it still be using the Blocked list?

One tip about PPPoE problems : try to disable ACPI on boot menu (option 2).

@podilarius:

Have you tried one intel and 1 realtek? If they are onboard, perhaps one is disabled in bios. IIRC there are some things you can do either in BIOS or in start up scripts that pertain to realtek nics. Search the forums :/

thanks sir. i solved the problem by changing my nic.