autostart firewall i konfiguracja pod suse 10,0

[tom123]

log z wpisanym poprawnie bledem



Mar  3 13:02:16 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  3 13:02:17 linux SuSEfirewall2: batch committing...
Mar  3 13:02:18 linux SuSEfirewall2: Firewall rules set to CLOSE.
Mar  3 13:02:18 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  3 13:02:18 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Mar  3 13:02:18 linux SuSEfirewall2: Warning: no interface active
Mar  3 13:02:19 linux SuSEfirewall2: batch committing...
Mar  3 13:02:19 linux SuSEfirewall2: Firewall rules successfully set
Mar  3 21:53:40 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  3 21:53:40 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  3 21:54:06 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  3 21:54:06 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  3 21:54:21 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  3 21:54:21 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  3 21:55:03 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  3 21:55:03 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  3 21:55:19 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  3 21:55:19 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  4 19:56:20 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  4 19:56:21 linux SuSEfirewall2: batch committing...
Mar  4 19:56:21 linux SuSEfirewall2: Firewall rules set to CLOSE.
Mar  4 19:56:21 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  4 19:56:21 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Mar  4 19:56:21 linux SuSEfirewall2: Warning: no interface active
Mar  4 19:56:22 linux SuSEfirewall2: batch committing...
Mar  4 19:56:22 linux SuSEfirewall2: Firewall rules successfully set
Mar  4 19:56:27 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  4 19:56:27 linux SuSEfirewall2: batch committing...
Mar  4 19:56:27 linux SuSEfirewall2: Firewall rules unloaded.
Mar  4 19:56:28 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  4 19:56:28 linux SuSEfirewall2: batch committing...
Mar  4 19:56:28 linux SuSEfirewall2: Firewall rules set to CLOSE.
Mar  4 19:56:28 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  4 19:56:28 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Mar  4 19:56:28 linux SuSEfirewall2: Warning: no interface active
Mar  4 19:56:29 linux SuSEfirewall2: batch committing...
Mar  4 19:56:29 linux SuSEfirewall2: Firewall rules successfully set
Mar  4 20:00:11 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  4 20:00:12 linux SuSEfirewall2: batch committing...
Mar  4 20:00:12 linux SuSEfirewall2: Firewall rules unloaded.
Mar  4 20:00:12 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  4 20:00:12 linux SuSEfirewall2: batch committing...
Mar  4 20:00:12 linux SuSEfirewall2: Firewall rules set to CLOSE.
Mar  4 20:00:12 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  4 20:00:12 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Mar  4 20:00:12 linux SuSEfirewall2: Warning: no interface active
Mar  4 20:00:13 linux SuSEfirewall2: batch committing...
Mar  4 20:00:14 linux SuSEfirewall2: Firewall rules successfully set
Mar  5 09:17:37 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 09:17:37 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  5 09:17:38 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 09:17:38 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  5 09:17:38 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 09:17:38 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Mar  5 09:17:38 linux SuSEfirewall2: Warning: no interface active
Mar  5 09:17:38 linux SuSEfirewall2: batch committing...
Mar  5 09:17:39 linux SuSEfirewall2: Firewall rules successfully set
Mar  5 09:17:43 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 09:17:43 linux SuSEfirewall2: batch committing...
Mar  5 09:17:43 linux SuSEfirewall2: Firewall rules unloaded.
Mar  5 09:17:44 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 09:17:44 linux SuSEfirewall2: batch committing...
Mar  5 09:17:44 linux SuSEfirewall2: Firewall rules set to CLOSE.
Mar  5 09:17:44 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 09:17:44 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Mar  5 09:17:44 linux SuSEfirewall2: Warning: no interface active
Mar  5 09:17:45 linux SuSEfirewall2: batch committing...
Mar  5 09:17:45 linux SuSEfirewall2: Firewall rules successfully set
Mar  5 09:27:49 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 09:27:49 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  5 09:27:50 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 09:27:50 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  5 09:27:50 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 09:27:50 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Mar  5 09:27:50 linux SuSEfirewall2: Warning: no interface active
Mar  5 09:27:50 linux SuSEfirewall2: batch committing...
Mar  5 09:27:51 linux SuSEfirewall2: Firewall rules successfully set
Mar  5 17:02:04 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 17:02:04 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  5 17:02:04 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 17:02:05 linux SuSEfirewall2: /var/lock/SuSEfirewall2.booting exists which means system boot in progress, exit.
Mar  5 17:02:05 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
Mar  5 17:02:05 linux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Mar  5 17:02:05 linux SuSEfirewall2: Warning: no interface active
Mar  5 17:02:05 linux SuSEfirewall2: batch committing...
Mar  5 17:02:05 linux SuSEfirewall2: Firewall rules successfully set

[jezior]

2006-03-05 17:17:58 tom123 napisał:

 > Mar  5 17:02:05 linux SuSEfirewall2: Warning: no interface active
 > Mar  5 17:02:05 linux SuSEfirewall2: batch committing...
 > Mar  5 17:02:05 linux SuSEfirewall2: Firewall rules successfully set
 >

iptables -nL

[tom123]

2006-03-05 17:23:22 jezior napisał:

> 2006-03-05 17:17:58 tom123 napisał:
 >
 >  > Mar  5 17:02:05 linux SuSEfirewall2: Warning: no interface active
 >  > Mar  5 17:02:05 linux SuSEfirewall2: batch committing...
 >  > Mar  5 17:02:05 linux SuSEfirewall2: Firewall rules successfully set
 >  >
 >
 > iptables -nL

nie rozumiem??

[jezior]

2006-03-05 17:25:10 tom123 napisał:
 
 >  > iptables -nL
 >
 > nie rozumiem??
 >

konsola a w niej:
su
haslo
iptables -nL

[tom123]

 >  > iptables -nL
 >
 
 Wpisalem jako root ta komende i oto log

 
Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
input_ext  all  --  0.0.0.0/0            0.0.0.0/0
LOG        all  --  0.0.0.0/0            0.0.0.0/0           limit: avg 3/min burst 5 LOG flags 6 level 4 prefix `SFW2-IN-ILL-TARGET '
DROP       all  --  0.0.0.0/0            0.0.0.0/0

Chain FORWARD (policy DROP)
target     prot opt source               destination
LOG        all  --  0.0.0.0/0            0.0.0.0/0           limit: avg 3/min burst 5 LOG flags 6 level 4 prefix `SFW2-FWD-ILL-ROUTING '

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state NEW,RELATED,ESTABLISHED
LOG        all  --  0.0.0.0/0            0.0.0.0/0           limit: avg 3/min burst 5 LOG flags 6 level 4 prefix `SFW2-OUT-ERROR '

Chain forward_ext (0 references)
target     prot opt source               destination

Chain input_ext (1 references)
target     prot opt source               destination
DROP       all  --  0.0.0.0/0            0.0.0.0/0           PKTTYPE = broadcast
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           icmp type 4
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           icmp type 8
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED icmp type 0
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED icmp type 3
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED icmp type 11
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED icmp type 12
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED icmp type 14
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED icmp type 18
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED icmp type 3 code 2
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED icmp type 5
reject_func  tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:113 state NEW
LOG        tcp  --  0.0.0.0/0            0.0.0.0/0           limit: avg 3/min burst 5 tcp flags:0x17/0x02 LOG flags 6 level 4 prefix `SFW2-INext-DROP-DEFLT '
LOG        icmp --  0.0.0.0/0            0.0.0.0/0           limit: avg 3/min burst 5 LOG flags 6 level 4 prefix `SFW2-INext-DROP-DEFLT '
LOG        udp  --  0.0.0.0/0            0.0.0.0/0           limit: avg 3/min burst 5 LOG flags 6 level 4 prefix `SFW2-INext-DROP-DEFLT '
LOG        all  --  0.0.0.0/0            0.0.0.0/0           limit: avg 3/min burst 5 state INVALID LOG flags 6 level 4 prefix `SFW2-INext-DROP-DEFLT-INV '
DROP       all  --  0.0.0.0/0            0.0.0.0/0

Chain reject_func (1 references)
target     prot opt source               destination
REJECT     tcp  --  0.0.0.0/0            0.0.0.0/0           reject-with tcp-reset
REJECT     udp  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-port-unreachable
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-proto-unreachable

[jezior]

2006-03-05 17:30:04 tom123 napisał:

 >  Wpisalem jako root ta komende i oto log

 > DROP       all  --  0.0.0.0/0            0.0.0.0/0
 >
 > Chain reject_func (1 references)
 > target     prot opt source               destination
 > REJECT     tcp  --  0.0.0.0/0            0.0.0.0/0           reject-with tcp-reset
 > REJECT     udp  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-port-unreachable
 > REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with
 > icmp-proto-unreachable
 >

Brawo ;-)
Nie wiem na ile funkcjonalny bo nie chce mi sie analizowac regulek ale jest. A zakladajac ze suse wielkiej kaszany nie odwala to wniosek jest jeden.

Masz dzialajacego firewall'a.

[tom123]

 > Masz dzialajacego firewall'a.

to extra!!!
WIELKIE DZIEKI ZA CIERPLIWOSC

ps.reraz to tylko odpowiednia go skonfigurowac

Ale dlaczego ten komunikat.WYast mam manual wlaczone a nie ze startem systemu

[jezior]

2006-03-05 17:40:59 tom123 napisał:

>
 >  > Masz dzialajacego firewall'a.
 >
 > to extra!!!
 > WIELKIE DZIEKI ZA CIERPLIWOSC

ufff... Ciezko bylo...

 > Ale dlaczego ten komunikat.WYast mam manual wlaczone a nie ze startem systemu

Bo masz neostrade, ktora dziala na interfejsie dynamicznym ppp0

> 2006-03-05 17:17:58 tom123 napisał:
>
> > Mar 5 17:02:05 linux SuSEfirewall2: Warning: no interface active

A ten Twoj firewall doszukuje sie interfejsu statycznego. Jesli masz mozliwosc, (ja suse na oczy nie widzialem, wiec nie wiem co i jak) to przesun uruchamianie firewalla tak aby sie uruchamial po neo (malo bezpieczne) albo w ustawieniach tego Susefirewall czy jak mu tam ustaw ze masz interfejs dynamiczny

[tom123]

2006-03-05 17:47:24 jezior napisał:

> 2006-03-05 17:40:59 tom123 napisał:
 >
 > >
 >  >  > Masz dzialajacego firewall'a.
 >  >
 >  > to extra!!!
 >  > WIELKIE DZIEKI ZA CIERPLIWOSC
 >
 > ufff... Ciezko bylo...
 >
 >  > Ale dlaczego ten komunikat.WYast mam manual wlaczone a nie ze startem systemu
 >
 > Bo masz neostrade, ktora dziala na interfejsie dynamicznym ppp0
 >
 > > 2006-03-05 17:17:58 tom123 napisał:
 > >
 > > > Mar 5 17:02:05 linux SuSEfirewall2: Warning: no interface active
 >
 > A ten Twoj firewall doszukuje sie interfejsu statycznego. Jesli masz mozliwosc, (ja suse na
 > oczy nie widzialem, wiec nie wiem co i jak) to przesun uruchamianie firewalla tak aby sie
 > uruchamial po neo (malo bezpieczne) albo w ustawieniach tego Susefirewall czy jak mu tam ustaw
 > ze masz interfejs dynamiczny

mam tez mandrive,ona wydaje mi sie ladniejsza niz suse,moze zainstalowac ja.CO polecasz?
Jeszcze raz dzieki

coraz bardziej podoba mi linix,jednak cos w nim jest.Moze to ze jest inny,wiem ze napewno jest wart uwagi i kazdy kto go kiedys ma zamiar negowac powinien choc troszke sie z nim zapoznac!!!

[jezior]

2006-03-05 17:53:12 tom123 napisał:
 
 > mam tez mandrive,ona wydaje mi sie ladniejsza niz suse,moze zainstalowac ja.CO polecasz?

Odradzam, to straszny gniot. Zreszta to widac po ilosci nienaprawialnych w mandrivie problemow jakie sie pojawiaja na forum.
Nie rozumiem co to znaczy ladniejsza... To nie windows, jak  chcesz cos zmienic to zmieniasz
http://www.kde-look.org
http://www.gnome-look.org


 > coraz bardziej podoba mi linix,jednak cos w nim jest.Moze to ze jest inny,wiem ze napewno jest
 > wart uwagi i kazdy kto go kiedys ma zamiar negowac powinien choc troszke sie z nim zapoznac!!!
 >
Naprawde warto zostac z linuxem;-)
Tylko please bez obrazy:D zadnych literówek ;-) Gdybys dokladnie przepisal ten blad na poczatku, mielibysmy o 20 postów mniej ;-)

[tom123]

 > Naprawde warto zostac z linuxem;-)
 > Tylko please bez obrazy:D zadnych literówek ;-) Gdybys dokladnie przepisal ten blad na
 > poczatku, mielibysmy o 20 postów mniej ;-)

Spoko.Wszysko ok.Napewno jeszcze czesto zawitam na to forum:)