Menu

#2478 Shorewall rule generates messy rule when macro is used

1.270
open
5
2006-04-06
2006-04-06
Madtrek
No

This bug is already reported in webmin 1.26, but
version 1.27 still have the same bug .
When adding a new "macro" option in shorewall rule
editing in the "protocol" field MUST have a "null"
option, becouse in shorewall 3.0.x if there are ANY
option in this field whem "macro" is used then all rule
are ignored, so the webmin generated rule is messy and
do not work .

Discussion

  • Madtrek

    Madtrek - 2006-04-06
     
  • Nobody/Anonymous

    Logged In: NO

    The problem is that as of Shorewall 3.x the config file
    structure and layout has changed quite a bit. The reason you
    are having these problems is reported in this bug:
    [1463929] Config structure change in Shorewall 3.x breaks
    webmin module
    Cheers, TC

     
  • Jamie Cameron

    Jamie Cameron - 2006-06-08

    Logged In: YES
    user_id=129364

    So does the protocol have to be - if a macro is selected?
    If so, could you post some example Shorewall rules file
    entries to this bug report? I'm not too familiar with this
    format..

     

Log in to post a comment.

MongoDB Logo MongoDB