2010-12-01 17:24:02 +01:00
|
|
|
1) On systems running Upstart, shorewall-init cannot reliably secure
|
|
|
|
|
the firewall before interfaces are brought up.
|
|
|
|
|
|
|
|
|
|
2) If the output of 'env' contains a multi-line value, then
|
|
|
|
|
compilation failed with an Internal Error.
|
|
|
|
|
|
|
|
|
|
Workaround: In /etc/shorewall/params, reset any exported variables
|
|
|
|
|
that have a multi-line value.
|
|
|
|
|
|
2010-12-02 19:47:23 +01:00
|
|
|
Corrected in 4.4.15.1.
|
2010-12-02 19:32:54 +01:00
|
|
|
|
|
|
|
|
3) If a params file does not appear in the CONFIG_PATH, compilation
|
|
|
|
|
fails with the error:
|
|
|
|
|
|
|
|
|
|
.: 31: Can't open /etc/shorewall6/params
|
|
|
|
|
ERROR: Processing of /etc/shorewall6/params failed
|
|
|
|
|
|
|
|
|
|
Workaround: 'touch /etc/shorewall/params' (or
|
|
|
|
|
/etc/shorewall6/params).
|
|
|
|
|
|
2010-12-02 19:47:23 +01:00
|
|
|
Corrected in 4.4.15.1.
|
2010-12-10 21:27:05 +01:00
|
|
|
|
|
|
|
|
4) When logical interface names are used, proxy ARP does not
|
|
|
|
|
work. Symptoms include numerous Perl runtime error Messages.
|
|
|
|
|
|
|
|
|
|
Workaround: Don't use proxy arp involving an interface with a
|
|
|
|
|
logical name that is different from its physical name.
|
2010-12-11 19:29:25 +01:00
|
|
|
|
|
|
|
|
5) Unknown interface names in the proxyarp and tcinterfaces files
|
|
|
|
|
result in Perl runtime errors.
|
