Well, 'trace' was useful!
On Sat, Apr 16, 2016, at 04:11 PM, [email protected] wrote:
> Unfortunately, when I change the "IPv4_0" usage in 'params', the firewall
> still compiles, but a bunch of my access breaks.
>
> I'm pretty sure it's @ the rules depending on that "$IPv4_0" variable.
>
> Should that be somehow moved out of 'params' and set/detected earlier? Is
> there a better way to get that 'sticky' IP address into shorewall?
My problem is that the 'params' fileis on my desktop, where I'm running the
compile, then pushing the result to a remote.
At compile
IPv4_0=$( /usr/sbin/shorewall-lite call find_first_interface_address_if_any
eth0 )
is setting the value to the compile-time IP address of eth0, of my desktop! not
the remote that I need it to be.
So, how do I correctly get that value to be set at run-time on the target
machine, so that I get *its* eth0-assigned IP?
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
