Shorewall 4.5.21.6 on Ubuntu 14.04.1 kernel 3.16.0-51.

For the last month I have had the following entries (and a few more)
working fine:
main            10.1.13.0/24    10.1.15.3
main            10.1.8.0/21     10.1.15.1

I am halfway into implementing LSM. I am not yet allowing it to change
shorewall states, but I do have IFUPDOWN=0 in /etc/default/shorewall-init.
Therefore, I also have "shorewall restart" in a couple of openvpn up/down
scripts.

What I am seeing when shorewall attempts to restart:

Adding Providers...
RTNETLINK answers: File exists
   ERROR: Command "ip -4 route add 10.1.13.0/24 via 10.1.15.3 table 254"
Failed
...and shorewall ends up Stopped.

There have been some other recent config changes but I haven't been able to
pinpoint one that "caused" this, and it may be that it happened right from
the time the routes file was created and I didn't notice the issue.

If I reboot then it comes up clean as expected. Or, if I temporarily rename
/etc/shorewall/routes then shorewall starts OK.

Is this a bug? Shouldn't the startup sequence be doing a route replace
rather than route add? Or potentially, deleting the routes as part of
stopping Shorewall?
------------------------------------------------------------------------------
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

Reply via email to