Hi! I installed shorewall shorewall-2.1.7-1 on a newly installed box. When using 1.4 versions I could enable shorewall in ntsysv, now shorewall doesn''t show up in ntsysv? I am running shorewall on a RedHat Enterprise Linux rebuild (www.taolinux.org). Is this a bug or a feature?
Sorry for replying to my own message but I just upgraded to 2.0.8 using rpm -Uvh --force shorewall-2.0.8-1.noarch.rpm but still shorewall doesn''t appear in ntsysv On Mon, 6 Sep 2004, Remco Barendse wrote:> Hi! > > I installed shorewall shorewall-2.1.7-1 on a newly installed box. > > When using 1.4 versions I could enable shorewall in ntsysv, now shorewall > doesn''t show up in ntsysv? > > I am running shorewall on a RedHat Enterprise Linux rebuild > (www.taolinux.org). > > Is this a bug or a feature? > _______________________________________________ > Shorewall-users mailing list > Post: Shorewall-users@lists.shorewall.net > Subscribe/Unsubscribe: > https://lists.shorewall.net/mailman/listinfo/shorewall-users > Support: http://www.shorewall.net/support.htm > FAQ: http://www.shorewall.net/FAQ.htm >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Remco Barendse wrote: | Sorry for replying to my own message but I just upgraded to 2.0.8 using | | rpm -Uvh --force shorewall-2.0.8-1.noarch.rpm | | but still shorewall doesn''t appear in ntsysv What version of Shorewall were you running previously? I have no idea what ntsysv is (although I can probably guess) so I have no idea what changed that could affect how it works. - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBPKmcO/MAbZfjDLIRAucxAJ42wJ2fIE/DMQNikhPlgrRLILkKBwCbB4kT gb5UesgI0S3yvMXFpzeP0f4=lCcR -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom Eastep wrote: | Remco Barendse wrote: | | Sorry for replying to my own message but I just upgraded to 2.0.8 using | | | | rpm -Uvh --force shorewall-2.0.8-1.noarch.rpm | | | | but still shorewall doesn''t appear in ntsysv | | What version of Shorewall were you running previously? I have no idea | what ntsysv is (although I can probably guess) so I have no idea what | changed that could affect how it works. | I found ''ntsysv'' on my Fedora Core 2 system (ntsysv 1.3.9) and Shorewall ~ is listed. I tried running ''ntsysv'' with both Shorewall 2.0.3a and Shorewall 2.1.7. - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBPLF+O/MAbZfjDLIRAmg/AKCV2vzsc8Brs7Arv1yuvNltUYXIwACdFTWz RfiKG88KvMqoMGRPg4WYcNE=Oi1Y -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom Eastep wrote: | Tom Eastep wrote: | | Remco Barendse wrote: | | | Sorry for replying to my own message but I just upgraded to 2.0.8 using | | | | | | rpm -Uvh --force shorewall-2.0.8-1.noarch.rpm | | | | | | but still shorewall doesn''t appear in ntsysv | | | | What version of Shorewall were you running previously? I have no idea | | what ntsysv is (although I can probably guess) so I have no idea what | | changed that could affect how it works. | | | | I found ''ntsysv'' on my Fedora Core 2 system (ntsysv 1.3.9) and Shorewall | ~ is listed. | | I tried running ''ntsysv'' with both Shorewall 2.0.3a and Shorewall 2.1.7. So in other words, I can''t reproduce the problem -- is shorewall listed by ''chkconfig'' (e.g., ''chkconfig --list shorewall'')? - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBPLlMO/MAbZfjDLIRAvs5AJ9jHNCkhBvydAAilCvcNuYqxGINwQCfc5r9 rbNAYA+ET2OxevHXHeOGxWY=ocdP -----END PGP SIGNATURE-----
On Mon, 6 Sep 2004, Tom Eastep wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Tom Eastep wrote: > | Tom Eastep wrote: > || Remco Barendse wrote: > ||| Sorry for replying to my own message but I just upgraded to 2.0.8 > using > ||| > ||| rpm -Uvh --force shorewall-2.0.8-1.noarch.rpm > ||| > ||| but still shorewall doesn''t appear in ntsysv > || > || What version of Shorewall were you running previously? I have no idea > || what ntsysv is (although I can probably guess) so I have no idea what > || changed that could affect how it works. > || > | > | I found ''ntsysv'' on my Fedora Core 2 system (ntsysv 1.3.9) and Shorewall > | ~ is listed. > | > | I tried running ''ntsysv'' with both Shorewall 2.0.3a and Shorewall 2.1.7. > > So in other words, I can''t reproduce the problem -- is shorewall listed > by ''chkconfig'' (e.g., ''chkconfig --list shorewall'')?Sorry for my late reply. I wasn''t running any shorewall version on that box previously, it is a completely new (full install) of RHEL rebuild. This is the output from the command : [root@localhost tmp]# chkconfig --list shorewall service shorewall supports chkconfig, but is not referenced in any runlevel (run ''chkconfig --add shorewall'') After running `chkconfig --add shorewall'' shorewall does appear in the ntsysv list all of a sudden. Weird...... I guess it is because previous versions of shorewall were marked in ntsysv to be started at boot time (did you have the rpm run chkconfig --add shorewall during install??) and killed shorewall with the donotstart file in /etc/shorewall? The dont start file is gone, maybe the chkconfig command wasn''t issued either which caused this behaviour?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Remco Barendse wrote: |> So in other words, I can''t reproduce the problem -- is shorewall listed |> by ''chkconfig'' (e.g., ''chkconfig --list shorewall'')? | | | Sorry for my late reply. I wasn''t running any shorewall version on that | box previously, it is a completely new (full install) of RHEL rebuild. | | This is the output from the command : | [root@localhost tmp]# chkconfig --list shorewall | service shorewall supports chkconfig, but is not referenced in any | runlevel (run ''chkconfig --add shorewall'') | | After running `chkconfig --add shorewall'' shorewall does appear in the | ntsysv list all of a sudden. Weird...... | | I guess it is because previous versions of shorewall were marked in | ntsysv to be started at boot time (did you have the rpm run chkconfig | --add shorewall during install??) and killed shorewall with the | donotstart file in /etc/shorewall? | | The dont start file is gone, maybe the chkconfig command wasn''t issued | either which caused this behaviour? Hmmm -- I thought I saw a similar problem when I use rpm to install Shorewall on a new SuSE box earlier in the week. I''ll investigate. Thanks, - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBPO88O/MAbZfjDLIRAn6iAJ9iibLVO8R9O4R5YQEvl50lWCyz7gCdFBlS 8WFWRQvZsUtEBFpWUKV14gE=YZYD -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom Eastep wrote: | Remco Barendse wrote: | | | | This is the output from the command : | | [root@localhost tmp]# chkconfig --list shorewall | | service shorewall supports chkconfig, but is not referenced in any | | runlevel (run ''chkconfig --add shorewall'') | | | | After running `chkconfig --add shorewall'' shorewall does appear in the | | ntsysv list all of a sudden. Weird...... | | | | I guess it is because previous versions of shorewall were marked in | | ntsysv to be started at boot time (did you have the rpm run chkconfig | | --add shorewall during install??) and killed shorewall with the | | donotstart file in /etc/shorewall? | | | | The dont start file is gone, maybe the chkconfig command wasn''t issued | | either which caused this behaviour? | | Hmmm -- I thought I saw a similar problem when I use rpm to install | Shorewall on a new SuSE box earlier in the week. I''ll investigate. The problem is in the 2.1 shorewall.spec file -- It will be corrected in 2.1.8. Thanks, - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBPPRwO/MAbZfjDLIRAgRiAJ9NbMBQxrIqoiJVgeGtoSKvhme3rwCgreHU pk4brcHWYCswGgKfSRU/IZI=0IfJ -----END PGP SIGNATURE-----
On Mon, 6 Sep 2004, Tom Eastep wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Tom Eastep wrote: > | Remco Barendse wrote: > || > || This is the output from the command : > || [root@localhost tmp]# chkconfig --list shorewall > || service shorewall supports chkconfig, but is not referenced in any > || runlevel (run ''chkconfig --add shorewall'') > || > || After running `chkconfig --add shorewall'' shorewall does appear in the > || ntsysv list all of a sudden. Weird...... > || > || I guess it is because previous versions of shorewall were marked in > || ntsysv to be started at boot time (did you have the rpm run chkconfig > || --add shorewall during install??) and killed shorewall with the > || donotstart file in /etc/shorewall? > || > || The dont start file is gone, maybe the chkconfig command wasn''t issued > || either which caused this behaviour? > | > | Hmmm -- I thought I saw a similar problem when I use rpm to install > | Shorewall on a new SuSE box earlier in the week. I''ll investigate. > > The problem is in the 2.1 shorewall.spec file -- It will be corrected in > 2.1.8.Thanks! Weird that the ''upgrade'' to the latest stable release of shorewall didn''t solve the problem either. Guess that rpm doesn''t touch any of the init stuff when updating.... Thanks for checking and the quick fix :)> Thanks, > - -Tom > - -- > Tom Eastep \ Nothing is foolproof to a sufficiently talented fool > Shoreline, \ http://shorewall.net > Washington USA \ teastep@shorewall.net > PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFBPPRwO/MAbZfjDLIRAgRiAJ9NbMBQxrIqoiJVgeGtoSKvhme3rwCgreHU > pk4brcHWYCswGgKfSRU/IZI> =0IfJ > -----END PGP SIGNATURE----- > _______________________________________________ > Shorewall-users mailing list > Post: Shorewall-users@lists.shorewall.net > Subscribe/Unsubscribe: > https://lists.shorewall.net/mailman/listinfo/shorewall-users > Support: http://www.shorewall.net/support.htm > FAQ: http://www.shorewall.net/FAQ.htm >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Remco Barendse wrote: | | |> Thanks! Weird that the ''upgrade'' to the latest stable release of |> shorewall didn''t solve the problem either. Guess that rpm doesn''t touch |> any of the init stuff when updating.... | Defining Shorewall to init is only done during an install (rpm -i) and not during an upgrade (rpm -U). - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBPfDOO/MAbZfjDLIRAgo4AJwJxQXA1xKT8r2JJ14nlcGHTDdZZgCeNoxL CD+xtK3XgIFehPgmrqNMQRY=/0qA -----END PGP SIGNATURE-----
I never use -i to install packages (for years, except for kernel pkgs), only -U. In a fresh machine -U install Shorewall at init files. Maybe if you disabled Shorewall after -U ou -i, subsequent -U don''t "re-install" Shorewall at init files. -Gilson Soares On Tue, 07 Sep 2004 10:33:02 -0700, Tom Eastep <teastep@shorewall.net> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Remco Barendse wrote: > > | > | > |> Thanks! Weird that the ''upgrade'' to the latest stable release of > |> shorewall didn''t solve the problem either. Guess that rpm doesn''t touch > |> any of the init stuff when updating.... > | > > Defining Shorewall to init is only done during an install (rpm -i) and > not during an upgrade (rpm -U). > > - -Tom > - -- > Tom Eastep \ Nothing is foolproof to a sufficiently talented fool > Shoreline, \ http://shorewall.net > Washington USA \ teastep@shorewall.net > PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFBPfDOO/MAbZfjDLIRAgo4AJwJxQXA1xKT8r2JJ14nlcGHTDdZZgCeNoxL > CD+xtK3XgIFehPgmrqNMQRY> =/0qA > > > -----END PGP SIGNATURE----- > _______________________________________________ > Shorewall-users mailing list > Post: Shorewall-users@lists.shorewall.net > Subscribe/Unsubscribe: https://lists.shorewall.net/mailman/listinfo/shorewall-users > Support: http://www.shorewall.net/support.htm > FAQ: http://www.shorewall.net/FAQ.htm >