Having been with IPCop, and still running on a very old, but thus far
very reliable, 32-bit machine (having begun decades+ ago on P4, gone to
K7, now Celeron), I became concerned about single point of failure and
installed it on another 32-bit machine.
That was just meant as a stop-gap until I could find a good replacement
and from all I read, Endian Community looked to fit my needs:
- both 32 and 64-bit versions;
- multiple red zone support (I have that need for protection against
single point of failure there too)
- community support SEEMED robust (youtube, MLs, blogs, ...)
Decided that's the ticket.
Looking for 32-bit version, googled, reviewed all I could find, watched
several Youtube videos, ...
Closest I came was a development version, "Endian Firewall Community
release 3.0 devel".
Installed it once and said to myself looks like virtual machine stuff
and I'm trying to do bare metal. And I don't know VM stuff anyway other
than bridging (Brx pseudo device(s)) is needed to share the NICs between
the host and the VM image.
Tinkered a small bit, couldn't make it work.
Put IPCop back on that node.
More google, search mailing list for 32-bit and/or x86 and didn't come
up with anything I could recognize would be what I thought I needed.
After repeatedly googling some more and finding proclamations that BOTH
32 and 64 bit versions were available and found one post that made me
think both versions are in the ISO image to download, I thought I'd try
what the download button offered.
All I got from the download button was
efw_community-x64_3.3.0_recovery_softwarex86-64_20181026164637
I don't know if I clicked something wrong or what.
Well, I tried to install anyway figuring it might have some "magic"
(like booting 32-bit & setting configuration for 64-bit future boots?)
that would detect 32-bit (x86) and load a 32-bit version I THOUGHT might
be included in the ISO image, but no joy. Told me the kernel was 64-bits
and I needed a kernel appropriate to my hardware.
DOH! Of course it didn't know I had been pursuing exactly that.
Today tried the "Endian Firewall Community release 3.0 devel" again
determined to explore more forcefully.
Got red zone working no problem, never got it to connect to a laptop in
the Green zone running CentOS 6.10 LiveDVD.
Being restricted by the ... "stuff" locking me into the jail that
exists, I couldn't do the normal ifconfig, lspci, ... CL stuff I
normally do.
But I did see eth1 (red zone) get assigned an IP44 address and I can
ping the wide world and run traceroute (thank you for those two). But
eth0 (Green zone) just lays there. Br0 has an IP44 address and is
showing the same MAC as eth0, so I'm hoping to review one more youtube
that will give me the clue (assuming I just need to do what would be
done in VM instead of on bare metal).
I'm not hopeful though
So, likely end of the road unless someone can hit me with a clue bat.
IPCop continues to work, runs on my old equipment and I'm perfectly
content to stay with it because I have no Orange Zone needs and I met my
Blue Zone needs "through a back door approach". It just means my
fallback solution will be manual (power up the standby and move one end
of an ethernet cable) instead of having my multiple red zones up and
ready (FYI: 100MB cable ISP, Sprint Samsung Galaxy S10+ with hot spot
and satellite service).
Any help would be appreciated.
I've enough hardware around that with sufficient instructions I could
throw another CentOS up on an idle box to compile & such if need be, but
I'd rather not do it while I'm trying to set up meet my basic need first.
Currently running CentOS 6, and trying to hang in there as long as
possible, to do my normal stuff. It's EOL in November though - might
switch to some BSD variant or ...?
TIA for any/all proffered solutions, other than buying MORE hardware
when I can't use up what I've already got (some on the way to
electronics recycling when I get "a round tuit".
Bill
_______________________________________________
Efw-user mailing list
Efw-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/efw-user
