The config file structure has changed in Shorewall 3.x
(possibly previous versions as well).
This breaks the Shorewall Webmin module included with
1.260.
At least the structure of:
/etc/shorewall/zones
has changed from:
###############################################################################
#ZONE DISPLAY DESCRIPTION
to:
###############################################################################
#ZONE TYPE OPTIONS INOPTS
OUTOPTS
There are quite possibly other changes as well.
This is the cause for bug:
http://sourceforge.net/tracker/index.php?func=detail&aid=1452357&group_id=17457&atid=117457
And soon to follow several others I suspect.
Cheers,
TC
Logged In: NO
As reported by maggycell, as of 1.270 this bug is still
present. The only way to use Shorewall 3.x at present with
webmin is to edit the config/rule files manually.
Cheers, TC
Logged In: YES
user_id=1381163
So, the bug will not be corrected ? Webmin will no longer
suports Shorewall ? It is the first time I report a bug in a
core Webmin module that is not corrected in subsequent version !
Logged In: NO
Maggycell > I hope the bug will be corrected. Sorry you
misunderstood. I haven't seen any aknowledgement from anyone
other than you and I though about the existense of this bug.
Hopefully as you said, since it is a bug in core Webmin
module, that it will be corrected soon!
Cheers, TC
Logged In: NO
Maggycell > I hope the bug will be corrected. Sorry you
misunderstood. I haven't seen any aknowledgement from anyone
other than you and I though about the existense of this bug.
Hopefully as you said, since it is a bug in core Webmin
module, that it will be corrected soon!
Cheers, TC
Logged In: YES
user_id=129364
Webmin 1.270 should handle this new shorewall format.
Logged In: NO
Obviously we still have the same problem in the current
version (1.270). That is what has brought me here.
Logged In: YES
user_id=129364
Funny, I thought I'd solves this problem..
Could you post an example line from your shorewall zones
file to this bug report, so I can see what exactly Webmin is
doing wrong?
Logged In: YES
user_id=1381163
the link hass a screenshoot, note the destination shows zone
type !
http://hpp.ajato.com.br/fabior/device/rules.jpg
And following is the conttent of my rules file :
#############################################################################################################
#ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL RATE USER/
# PORT PORT(S) DEST LIMIT GROUP
#SECTION ESTABLISHED
#SECTION RELATED
SECTION NEW
Ping/ACCEPT $FW net
AllowICMPs/ACCEPT $FW net
DNS/ACCEPT $FW net
ACCEPT $FW net tcp ftp,http,ntp,smtp,pop3,37,53,80,9120
ACCEPT $FW net udp ntp,37,53,80
Ping/ACCEPT net $FW
ACCEPT net $FW tcp ssh,ftp,10000
ACCEPT local $FW udp ntp,37,53
Ping/ACCEPT $FW local
SMB/ACCEPT $FW local
ACCEPT $FW local tcp ssh,ftp,ntp,25,53,110,548,631,10000
ACCEPT $FW local udp ntp,53,548
Ping/ACCEPT local $FW
SMB/ACCEPT local $FW
ACCEPT local $FW tcp ssh,ftp,http,ntp,25,53,110,548,631,10000
ACCEPT local $FW udp ntp,53,548
#LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE
I hope it helps !
Logged In: YES
user_id=129364
Does it help if you upgrade to Webmin 1.276, from
http://www.webmin.com/devel.html ?
Also, is the shorewall version shown correctly on the
module's main page?
Logged In: YES
user_id=1381163
Yes, even the 1.26 version allready shows the correct
version of shorewall, 1.27 too .
After upgraded to 1.276 apparently rule is showing the
correct dest. and source, and when I tryed to create a new
rule using macro fuction and leaving the "protocol" field
with "any" it generates correct rule line .. I'm still
testing.. any trouble I'll back .. thanks ....