Hi all, I''m currently running Shorewall 4.4.0.2 on CentOS5.4 (2.6.18-164.15.1.el5) and plan to upgrade ShoreWall to current. In order to do the upgrade, do I need to walk through each point-release (ie 4.4.1, 4.4.2, 4.4.3) or can I jump to the latest version? I''m having problems with MASQ/SNAT with multiple ISP''s, which I''m sure is my misconfiguration, but before I start asking questions here it seemed prudent to get everything current. Kernel will end up at 2.6.18-238 (CentOS5.5) and hopefully they don''t cripple anymore NetFilter functionality along the way (neither trace nor connbyte are available) Thanks for putting such a great compiler together, this makes managing iptables much, much easier. Regards, Lee ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
Hello Lee, On Apr 17, 2011, at 2:43 PM, Lee Brown wrote:> In order to do the upgrade, do I need to walk through each point-release (ie 4.4.1, 4.4.2, 4.4.3) or can I jump to the latest version? >You can jump to the latest version. -Tom Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev