After using the 586 platform version for over a while now, I had established a comfort level with the software. However, few updates ago ( i think 152 ) it told me I was using obsolete platform. So i decided to download the x86_64 version and did a new install on a different drive ( i run ipfire off of fast 16gig class 10 U3 SD cards ).
I wanted to used my configs from my longtime 586 so that i would need to re-enter one by one all my firewall rules, etc etc. So I created a .ipf backup file without logs so that it could restore on the x86_64 version.
What a mistake ! The trace graphs ended up with errors. After doing research, turns out I needed to make changes so that the sensor modules would correctly load. After a number of mistakes and 3 full installs over again, I think I’ve got it working, but I’m not sure the FW is behaving as it should.
My main observation was that on the 586 version, when I unplug the RED network cable, after a while i hear the beep that the connection has closed, and when I re-insert it the beep comes up later to indicate connection is again established. When I look at the System->Home status, it toggles between connected and not-connected as I do this.
However, on the x86_64 version, disconnecting the cable has no change; no beeps. Even leaving the RED disconnected for a number of hours doesn’t change the status. It’s almost as if the software is not actually monitoring the RED’s interface card, but some secondary internal virtual interface, which has me a bit concerned. Even all the previously established internet connections remain shown as still established. The RED interface is static IP to the modem/router, and running 153 (but was same with 152)
Anyone have any ideas ?