"Data logging" can mean many things. What sort of data rate are you looking to log? Is it bursty, or coming in at a constant sample rate like temperature readings or similar?
Another thing to consider is power - can the power go out suddenly? If it can then you need to make sure you're not buffering stuff in RAM, and (if using a Linux-based solution) use a log-structured filesystem that won't get corrupted by a sudden power loss.
For the firewall job you could use a BeagleBone Black (the new rev. C has proper Debian as standard, and the eMMC is doubled to 4GB capacity now) with a decent-quality USB<->Ethernet adaptor.
Olimex is just now rolling out a SOM based on the same TI chipset as the BeagleBone Black, and the eval board has
two ethernet jacks:
https://www.olimex.com/Products/SOM/AM3 ... e-hardware
Another thing you could do if your data rates aren't above a couple of megabits per second is get two BeagleBones (or similar SBCs), sit them side by side, and connect them via their UART pins. Then you could write your own code to run on each to sling data between the two otherwise isolated subnets. That'd probably be better if you've got a specific job in mind, though, rather than if you're building a general-purpose firewall.
I personally wouldn't touch the Raspberry Pi with a ten-foot pole for industrial use. Its Ethernet socket is really just a USB Ethernet adaptor munged into the the board, and I'm still not convinced its USB stack works properly. Great for kids to play with and for people to make little MAME cabs and such with, but not something I'd trust mission-critical stuff to myself.