[LEFT]I have installed interworx, and I’m in the panel just fine… however, this is because there is no firewall currently operating, and iptables has an open rules list.
In attempting to start APF, interworx does not start it (although it says it starts successfully).
I tried it from ssh, and found that it was having an issue with the configuraiton, specifically at CNF_FUNC="$FWPATH/internals/functions.apf", this was being interpreted as /internals/functions.apf, so for whatever reason the $FWPATH variable is getting destroyed before that.
There are quite a few spots where this occurs.
When I attempt to fix this by just simply setting a global path variable, I get a whole junkload of errors, and the firewall blocks all access (literally).
1.) Are you on a VPS?
2.) Do you get any error messages on the console when restarting APF? Be sure to put APF in debug mode when you do restart.
3.) Do you have SELinux disabled?
1.) Are you on a VPS?
2.) Do you get any error messages on the console when restarting APF? Be sure to put APF in debug mode when you do restart.
3.) Do you have SELinux disabled?
Socheat[/quote]
No
Yea, I stated them above.
Not sure, but no? I havent disabled it, and I wasnt aware I even had it installed. So, unless it requires me to explicitly enable it, I haven’t touched it.
After giving static paths to the errored line (makign it /etc/apf/internals/functions.apf) i get:
/etc/apf/internals/functions.apf: line 27: $IPTLOG: ambiguous redirect
/etc/apf/internals/functions.apf: line 27: $IPTLOG: ambiguous redirect
/etc/apf/internals/functions.apf: line 27: $IPTLOG: ambiguous redirect
/usr/local/sbin/apf: line 65: /vnet/vnetgen: No such file or directory
/usr/local/sbin/apf: line 67: /firewall: No such file or directory
/etc/apf/internals/functions.apf: line 27: $IPTLOG: ambiguous redirect
Created. I’ve also left the config files alone, however, you might be wary of starting APF successfully… I’ve done it twice now and I’ve had to VPN in and fix it. I may be going to sleep soon
This issue was resolved. The problem was that OffbeatAdam had his public interface on eth1, and APF, by default, only allows traffic on one interface. There’s a trusted interface directive, TIF="", a few lines down that needed to be set to eth1. I force re-installed the InterWorx APF RPM, set TIF=“eth1”, and then APF started up without problems.