So all of your devices are on same vlan and your switches are interconnected with 1 upstream connection to this router in the mail room, or do all the switches go directly to the uni router? If you only have one uplink to their router, you could just ask to have this block they gave you routed to you via a /30 or /31 transit network, then all their switches could maintain their same IP and you would just have pfsense as firewall between their network and the yours.  You could then allow them access to the IPs the switches are on and all your devices could maintain their public IPs you would just allow traffic at pfsense. Or you could nat off your network yes, you could then change all your switches to your private network and port forward to them via a public IP you put on pfsense wan.  Since you had a whole block to use.. You could the same switches IP and just forward to the new private IPs of the switches. The routed network is the cleanest option if you ask me. Your other option - which I don't like but would be to setup pfsense in transparent mode and bridge.  I would not recommend this option, but this is another way for you to leave all the ip addressing the same on your devices and their switches while still giving you a firewall between their network and yours. As to learning pfsense – just connect pfsense to one of your switch ports.  Put another switch behind it connected to pfsense lan interfacde and play with putting some devices behind pfsense.  This would be a mini version of option 2.

@cmb: Given that, it seems likely it's a hardware issue. Where it's a software issue, generally you'll find other reports via Google of similar backtraces, or within our crash reports. Yeah I would have expected hardware except this box has been a rock for 6 months now running pfSense, so I'm not sure what to think.  I would have used the cosmic ray excuse, but it's a Xeon E3 machine with ECC RAM.  It's behaving itself now so I'll just assume it wanted attention.  ;D

Same here…I've traded out NIC cards, drives, reloaded PFS a few times and an entirely new box.  I'm using Neoware Thin Clients with a 4GB DOM, 1GB of RAM, 1Ghz processor and Intel dual NIC.  I'm installing PFS 2.2.4  I've got this working on a few other Thin Clients with the same config but they were upgraded not freshly installed. Eventually it passes the "Configuring LAN interface…Starting DNS Resolver..." but it takes a very long time (up to an hour). kingsz1- Did you figure this out or are you using the kind of hardware I am?  What was the solution? Anyone else seen this or have any suggestions?

@doktornotor: If there was a working fsck, the journaling would help with some cases of unclean unmount/hard reset. Sadly, the fsck is totally borked and produces a giant kaboom in that case. Only with crap flash (though it's certainly very bad in that case). On a SanDisk CF in an ALIX, and a SanDisk SD in an APU, they survived a thousand power cycles each left rw mounted, SU+J, with some writing happening when power was lost. I took an affected CF card that fsck couldn't fix, dd'ed it to an img and booted it up in KVM, and fsck cleaned it just fine. Same when dd'ing it to another CF, was fine. Something screwy going on there with the problem flash, but didn't bother digging any further after confirming it doesn't happen minus SU+J.

It is upgraded to 2.2.4 and I've had this issue upgrading from a new install at 2.2.2 to both 2.2.3 and 2.2.4.  I'm wondering if it has something do with the suricata package, that package disappears and has to be re-installed (it remembers settings but doesn't show up as installed).

@neonflx: Im done a fresh install of pfsense 2.2.3 the issue I'm having is that while I'm pulling and ip from my ISP on the WAN side and i can access the pfsense web interface I can't access any website, connection is listed as limited on windows machine, also my ununtu box is the same. If I use just my wireless router without pfsense everything works fine, note that the I have tried just the pfsense box with wan to isp and lan directly to my computer bypassing the wireles router and switch and still the same, also when i use the wireless router has dhcp disabled an just act as AP. The same box used to worked flawlessly in the same house and same provider a year ago, then I went to Korea for a year and just got back and having this issue. Any suggestions would be appreciated. Thanks I have same problem like you. Here how I fixed it. Go to Interface - WAN - Uncheck Block private networks. Go to Services - DNS Resolver - Check Enable Forwarding Mode. Make sure everything else is default.

Is that the exact error given? Quickly Googling this shows a much more common error would be, for example: nfe0: tx v2 error 0x6204 <underflow>Are you actually having a connectivity issue or seeing the logs spammed? You could try switch the WAN and LAN assignments. Put the nfe device on the LAN instead. Steve</underflow>

By fixing what you type into your browser. Use https://

OK, I understand your views now. I'll still keep the renaming in my specific environment for now, as it makes my life a whole lot easier.

Not really understanding the questions, perhaps a language issue. If I was moving to two new boxes with different hardware, this is how I would go about it- Backup config on both old boxes. Shutdown old backup and remove from rack. Rack the new master and backup. Restore the config from the old master onto the new master, adjust interfaces, etc. Restore the config from the old backup onto the new backup, adjust… Verify the new units are now showing any errors. Shut down old master. Move connections to new master and backup. Cycle provider equipment. Test inbound and outbound connections. Get a beer.

Guessing your ALIX config probably had 38400 for the baud rate (or something other than 115200), check your ALIX config backup in a text editor for the baud rate and change your console to match that. It's probably at an interface mismatch prompt on the serial console at a different baud.

Great, thanks for confirming that.  :) Steve

Hello Thx, CTRL-F5 solved the problem ;) Przemko

Well, I have completely started from the scratch. As the problem occurred while installing the upgrade to 2.2.4, I assumed that this was the source. But I proofed myself wrong by installing pfSense 2.2.2 with my configuration file, and it did not work either. So, the source of the problem was somewhere else, and finally the fresh installation seemed to be easier than to screw up even more the existing configuration. Solved for me.

@phil.davis: You put firewall rule(s) on LAN that match traffic from LAN clients and then choose the wanted gateway group down in the advanced section of the rule(s). yes, that is how i did it. went to firewall rules, click on LAN select IPv4 *  then edit it and in advanced features i click the advanced button on gatewary and select my multi wan group. but it slower instead of faster. each wan has an 10mbps adsl but when i put it together it gives me 6mbps on my speedtest this is the topic whit this issue https://forum.pfsense.org/index.php?topic=97217.0

well its a fresh upgrade from 2.2.3 to 2.2.4 and btw on 2.2.3 never had the issue

Well, thank you for your help doktornotor and robi. I'll try to apply your solutions again. Robi, my boss wanted to install pfsense on a HDD (we already have 2 appliances with pfsense installed on a HDD and these appliances run). But these appliances are different than the new device. That's why I don't use a CF card for the moment. If it's the only way to configure it correctly, I'll try it. Thanks again