Mailinglist Archive: opensuse (3442 mails)
| < Previous | Next > |
Re: [SLE] Installing SuSE Firewall 2
- From: David <dg@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 5 Dec 2001 00:47:35 +0000
- Message-id: <E16BQIL-000130-00.2001-12-05-00-52-17@xxxxxxxxxxxxxxxxxxxxx>
Hi Togan
On Wed, 5 Dec 2001 02:07:33 +0200, Togan Muftuoglu wrote:
>>>
>>That gives iptables-1.2.1a-37
>
>Well there is iptables-1.2.1a-53 on my box for the kernel upgrade use SuSE
>kernel rpms to avoid problems and it is fairly simple
>
>get the kernel from the ftp mirrors of SuSE in the update directory for your
>SuSE version
>
>as root rpm -Uhv k_deflt.rpm (assuming you are using the default one to be
>sure rpm -q k_deflt should give you the installed version)
>
>After that type
>
>mk_initrd and type lilo Reboot and enjoy your new kernel
Ok I'll have a look at that.
>
>
>>>
>>>/etc/init.d/SuSEfirewall2 test
>
>my mistake it shoud be
>
>/sbin/rcSuSEfirewall2 test or just rcSuSEfirewall2 test
Ok that works. Results below
linux:/ # rcSuSEfirewall2 test
Usage: /sbin/rcSuSEfirewall2 {start|stop|status|restart|reload|force-reload}
Now with the options
linux:/ # rcSuSEfirewall2 start
Starting Firewall Initialization: (phase 2 of 3) failed
linux:/ # rcSuSEfirewall2 status
Checking the status of the Firewall:
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
linux:/ # rcSuSEfirewall2 restart
Starting Firewall Initialization: (phase 2 of 3) failed
linux:/ # rcSuSEfirewall2 reload
Starting Firewall Initialization: (phase 2 of 3) failed
linux:/ # rcSuSEfirewall2 force-reload
Starting Firewall Initialization: (phase 2 of 3) failed
linux:/ #
Any type of start brings up a failure.
>
>try the firewall part before upgrading the kernel if it is going to make you
>happier and next time before you hit the reply button check that my email is
>not listed in _To:_ or _CC:_ parts as being a list member I normaly get the
>mails very fast :-)
>
Sorry if that is annoying you, but the instructions from the Suse faq are to
reply to all, which is contrary to other lists I use. I have removed your
address from this one, so I hope you get it.
Regards,
David
On Wed, 5 Dec 2001 02:07:33 +0200, Togan Muftuoglu wrote:
>>>
>>That gives iptables-1.2.1a-37
>
>Well there is iptables-1.2.1a-53 on my box for the kernel upgrade use SuSE
>kernel rpms to avoid problems and it is fairly simple
>
>get the kernel from the ftp mirrors of SuSE in the update directory for your
>SuSE version
>
>as root rpm -Uhv k_deflt.rpm (assuming you are using the default one to be
>sure rpm -q k_deflt should give you the installed version)
>
>After that type
>
>mk_initrd and type lilo Reboot and enjoy your new kernel
Ok I'll have a look at that.
>
>
>>>
>>>/etc/init.d/SuSEfirewall2 test
>
>my mistake it shoud be
>
>/sbin/rcSuSEfirewall2 test or just rcSuSEfirewall2 test
Ok that works. Results below
linux:/ # rcSuSEfirewall2 test
Usage: /sbin/rcSuSEfirewall2 {start|stop|status|restart|reload|force-reload}
Now with the options
linux:/ # rcSuSEfirewall2 start
Starting Firewall Initialization: (phase 2 of 3) failed
linux:/ # rcSuSEfirewall2 status
Checking the status of the Firewall:
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
linux:/ # rcSuSEfirewall2 restart
Starting Firewall Initialization: (phase 2 of 3) failed
linux:/ # rcSuSEfirewall2 reload
Starting Firewall Initialization: (phase 2 of 3) failed
linux:/ # rcSuSEfirewall2 force-reload
Starting Firewall Initialization: (phase 2 of 3) failed
linux:/ #
Any type of start brings up a failure.
>
>try the firewall part before upgrading the kernel if it is going to make you
>happier and next time before you hit the reply button check that my email is
>not listed in _To:_ or _CC:_ parts as being a list member I normaly get the
>mails very fast :-)
>
Sorry if that is annoying you, but the instructions from the Suse faq are to
reply to all, which is contrary to other lists I use. I have removed your
address from this one, so I hope you get it.
Regards,
David
| < Previous | Next > |