Goetz Reinicke
2002-Jul-23 05:59 UTC
[Shorewall-users] update shorewall 1.1.17 to 1.3.4 - simple rpm -Uvh ?
Hi, AFAIK the usual way to update shorewall is a "simple" :-) rpm -Uvh, but as I didn''t updated for a long time I''d like to be shure that an update from 1.1.17 to 1.3.4 will still work the same way with an simple rpm -Uvh... Or have there been changes which force to make changes to the configs? (not for using new features) Thanks for hints! cu... ...Götz - Götz Reinicke -------------------- mailto: greinick@filmakademie.de - IT Koordinator Tel: 07141/969-420 IT-OfficeNet Filmakademie Baden-Württemberg Fax: 07141/969-55420 - Mathildenstr. 20, 71638 Ludwigsburg ----------- www.filmakademie.de -
Tom Eastep
2002-Jul-23 13:24 UTC
[Shorewall-users] update shorewall 1.1.17 to 1.3.4 - simple rpm -Uvh ?
Hi Goetz, On Tue, 23 Jul 2002, Goetz Reinicke wrote:> Hi, > > AFAIK the usual way to update shorewall is a "simple" :-) rpm -Uvh, but > as I didn''t updated for a long time I''d like to be shure that an update > from 1.1.17 to 1.3.4 will still work the same way with an simple rpm > -Uvh... Or have there been changes which force to make changes to the > configs? (not for using new features) > > Thanks for hints! >You shouldn''t have any problems simply updating the RPM. While the format of port-forward and port-redirect rules has changed, the old rule syntax still works. Try "shorewall check" after you have upgraded -- there is at least one case (documented in the errata) where an incorrect configuration would work on older versions but will fail on the later ones. The "check" command will catch this and the fix is easy (add an entry to /etc/shorewall/interfaces). -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net