1)  On systems running Upstart, shorewall-init cannot reliably secure
    the firewall before interfaces are brought up.

2)  The 'enable', 'reenable' and 'disable' commands do not work
    correctly in configurations with USE_DEFAULT_RT=No and optional
    providers listed in the DUPLICATE column.

3)  The BLACKLIST action was inadvertently omitted from Shorewall6 in
    Shorewall 5.1.1.

    Corrected in Shorewall 5.1.4.1.

4)  Support for the NFQUEUE '--queue-cpu-fanout' option, introduced in
    Shorewall 5.1.0, contained a defect which can result in the
    following compile-time error:

      Use of uninitialized value $fanout in concatenation (.) or string
      at /usr/share/shorewall/Shorewall/Rules.pm line 643,
      <$currentfile> line 2.

    Corrected in Shorewall 5.1.4.2.

5)  When running on prior-generation distributions such as RHEL6,
    IPv6 multi-ISP configurations fail to start due to an error such as
    the following:

       ERROR: Command "ip -6 -6 route replace default scope global 
              table 250 nexthop via ::192.88.99.1 dev tun6to4 weight 1"
              Failed

    Corrected in Shorewall 5.1.4.3.

6)  A defect in 5.1.4.3 causes a startup failure when two or more
    'fallback' providers are configured.

    Corrected in Shorewall 5.1.4.4.
