SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0001486: firewall config including an ANY or ALL instead of a zone name, create wrong rules - MantisBT
MantisBT - Endian Firewall
View Issue Details
0001486Endian FirewallFirewall (iptables)public2008-11-25 16:222009-10-27 12:21
peter-endian 
peter-endian 
normalminoralways
closedfixed 
2.2-rc3 
2.32.3 
0001486: firewall config including an ANY or ALL instead of a zone name, create wrong rules
ANY/ALL will not be replaced by '' but taken as interface name. This creates wrong rules like these:

    0 0 ALLOW icmp -- ANY * 0.0.0.0/0 0.0.0.0/0 limit: avg 3/sec burst 5 mode srcip-dstip icmp type 8
    0 0 ALLOW icmp -- ANY * 0.0.0.0/0 0.0.0.0/0 limit: avg 3/sec burst 5 mode srcip-dstip icmp type 30

substZones() need to return '' when the value is ANY or ALL
No tags attached.
Issue History
2008-11-25 16:22peter-endianNew Issue
2008-11-25 16:22peter-endianAssigned To => peter-endian
2008-11-25 16:22peter-endianTag Attached: needsfix
2008-11-25 16:22peter-endianTag Detached: needsfix
2008-11-25 16:38peter-endianStatusnew => resolved
2008-11-25 16:38peter-endianFixed in Version => 2.3
2008-11-25 16:38peter-endianResolutionopen => fixed
2008-11-28 16:58AnonymousStatusresolved => feedback
2008-11-28 16:58AnonymousResolutionfixed => reopened
2008-12-02 09:18peter-endianNote Added: 0001833
2008-12-02 09:18peter-endianStatusfeedback => resolved
2008-12-02 09:18peter-endianResolutionreopened => fixed
2009-10-27 12:01peter-endianStatusresolved => closed
2009-10-27 12:21peter-endianTarget Versionfuture => 2.3

Notes
(0001833)
peter-endian   
2008-12-02 09:18   
no comment on reopen -> re-resolve it, since the bug is fixed