Hello all - I'm resurrecting this thread in hopes of getting some advice and/or clarity on what's going on.
As you can read in my previous email, I attempted an in-place upgrade from 2.0.1 to 2.1.2, which failed due to it (for some reason) not NATting packets correctly. Last night I finally got around to burning a clean 2.1.2 image on a CF card, installing it, then restoring one of my 2.0.1 backups. After doing this, I had the *exact* same symptoms as I did after the in-place upgrade: - interfaces were configured correctly - firewall and NAT rules correct - internet-bound traffic sourced from the pfsense itself worked fine (pings, DNSmasq, etc.) - it would not NAT LAN packets out the WAN interface I saw one anomaly that I doubt has anything to do with this failure, but I'm not certain, so I'll mention it. This install is on a soekris net-5501, which only has 256 MB RAM. As such, when pfsense booted, php was consistently getting killed due to memory contention. I needed to restart the web configurator from the console. Now, my assumption is that routing, NAT, firewall, etc. are kernel-level functions and should not be affected by an out-of-memory condition. Is this correct? Does anyone have other ideas as to what's going on? Thank you- Erik On Mon, Apr 21, 2014 at 2:23 PM, Erik Anderson <[email protected]> wrote: > I have an embedded (soekris) install running 2.0.1-RELEASE. > > This weekend, I attempted an in-place upgrade to 2.1.2-RELEASE. After the > upgrade, all interfaces appeared to be configured correctly: > > - while ssh'ed into pfsense, I could access internet hosts > - all internal VLAN interfaces were configured correctly, and were > accessible as expected from their respective VLANs > - from the "main" internal LAN, I could access the pfsense LAN interface as > well as the web configurator > > However, it didn't appear to be NATing packets correctly from any of the > internal interfaces to the WAN. I double-checked and re-applied the NAT and > firewall rules to no effect. > > Any ideas what could have happened? Are there any known issues with an > in-place 2.0.1 -> 2.1.2 upgrade? > > Next I'm just going to try to burn a clean 2.1.2 image on a CF card and then > restore the config file, which I *hope* will be successful. > > -Erik _______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
