search for: upgrade_issues

I''d like to ask for clarification on the upgrade procedure using tarballs. In the past, with version 4.4, I have downloaded shorewall-4.4.x.y.tar.bz2 and shorewall6-4.4.x.y.tar.bz2, extracted each, and executed ''install.sh -s'' in each directory. Now there is a new package shorewall-core-4.5.x.y.tar.bz2. As I understand it, with version 4.5, this core package needs to be

Shorewall 1.4.0 is released and is available at both SourceForge and at the mirror in Washington State. Other mirrors will be updated shortly. The content of 1.4.0 is the same as 1.4.0-RC3 with the exception of the updated version number. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.sf.net Washington USA \ teastep@shorewall.net

I have an "old and decrepit" install of Shorewall, installed from a Debian package. I''m having a problem, so in order to get support, I''m working on upgrading to the most recent stable version. What I''d like to do, is to test the new version with my configuration files, without actually installing it -- just untarring it. Is this possible? How can I

Everyone, Progress was slow today. I started out well, but then I ran into Documentation.htm. Progress slowed considerably, as I analyzed the document structure. I''m up to /etc/shorewall/hosts Configuration. I hope to finish Documentation.xml by tomorrow evening. Converted documents: 6to4.xml CorpNetwork.xml FAQ.xml Please post feedback, if you see any problems with the converted

On the upgrade issues page (http://www.shorewall.net/upgrade_issues.htm) you will find a number of sections with names like "Version >= 1.4.0", "Version >= 1.3.14", etc. The section entitled "Version >= 1.4.0" presents the considerations if you are upgrading from version 1.3.14 only. So If you are upgrading from version 1...

Hiya. I am currently usiong Shorewall 1.4.8 on my Mandrake box. I want to look at upgrading it to the Latest build of shorewall. Is there anything I need to look out for before doing this ? Is there a FAQ as to the easiest way or doers it upgrade ok following the usual Upgrade via RPM instructions. cheers in advance. _________________________________________________________________

I''m happy to see shorewall 3.0 is released. My server is running 2.4.6 and I want to upgrade to 3.0. What should I pay attention to upgrade to 3.0 ? ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache''s Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your

Hello Tom, I''ve been using Shorewall for years without problems. My previous version of shorewall was 1.4.6b-1. Everything worked just fine. Today I upgraded using rpm to 2.0.8-1. After update no one can connect to any interface from net. Server can connect to outside world fine and those described in routestopped have no problem connecting. Any help correcting this problem would be

Hey gang, I was wondering if all that documentation could or has been put into PDF format. I usually like to download documentation and read it while I''m sitting comfortably at home and I don''t want to tie up the phone line all night. Thanks, Nino p.s. If so, please feel free to attach the PDF formatted document to my e-mail ;-)

...default settings. Then I started shorewall: /etc/rc.d/init.d/shorewall start And I''ll be darn, the outside world is not able to connect to any services which I enabled via "rules" (can''t connect to anything). I''ve read everything in http://www.shorewall.net/upgrade_issues.htm for Version >= 1.4.6 to current release and I see nothing there that would cause this problem. When shorewall is disabled everything works fine so I can''t see it is a network problem. Also everything worked fine in previous versions. So I can only assume there is something with...

We''ve just upgraded to a new firewall machine, and a new version of Shorewall. We''re now on 2.04; previous version was 1.3.9b (!). So I''m pretty sure whatever problems we''re having are related to the big version jump. We''re using config files that exactly match our old (working) configuration (IOW, these are things which _were_ working on the old

...ll_quickstart_guide.htm shorewall_setup_guide_fr.htm shorewall_setup_guide.htm Shorewall_sfindex_frame.htm standalone.htm starting_and_stopping_shorewall.htm support.htm three-interface.htm traffic_shaping.htm troubleshoot.htm two-interface.htm upgrade_issues.htm VPN.htm whitelisting_under_shorewall.htm" for file in shorewall-docs-xml-$VERSION/*.xml; do a=$(basename $file) b=${a%.*} list_search $b.htm $HTMFILES && b=$b.htm || b=$b.html f="shorewall-docs-html-$VERSION/$b" report "Con...

This is a minor release of Shorewall. WARNING: This release introduces incompatibilities with prior releases. See http://www.shorewall.net/upgrade_issues.htm. Changes are: a) There is now a new NONE policy specifiable in /etc/shorewall/policy. This policy will cause Shorewall to assume that there will never be any traffic between the source and destination zones. b) Shorewall no longer creates rules to govern traffic from an interface:subnet to i...