On Thu, Jul 05, 2012 at 10:28:43PM +0800, lina wrote: > Hi, > > What is the best way to turn off the iptables? # iptables --flush will clear out all your iptables rules. > > or come back to its default settings. Flush my current one. > > Since I tried to configure the iptables, I have encountered the > following problems: > [cut] > > 2] The shutdown process in decades long. I mean it used to be fast to > shutdown, now need wait ~3 mins > > BTW, how to check the time of booting and shutting down? I'm not sure about shutting down, but try the bootchart2 package. That'll profile your booting and tell you all you need to know. > > 3] My syslog is flooding with similar information (kernel: [ > 436.954509] --log-prefixIN=eth0 OUT= > MAC=ff:ff:ff:ff:ff:ff:00:30:67:08:28:b3:08:00 SRC=172.21.50.212 > DST=172.21.51.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=58729 PROTO=UDP > SPT=137 DPT=137 LEN=58 ). Ah, glad to see it's not just me seeing "--log-prefix" in the logs. This is bug #678499, I believe. > > google showed me it's possible to put the log not in syslog. > > 4] Are there someone willing to sharing some iptables template, a bit > mature one with explaination. > > Thanks with best regards, > > P.S. The current one I used ( mainly adopted from > http://wiki.debian.org/iptables ), Here it is: [cut] Ah, looking at your firewall, I might see what your problem is with CUPS. You probably access CUPS one of two ways: either at 127.0.0.1 or at some other address. If you're using 127.0.0.1, then you still want line 5 enabled; the traffic should be using the loopback device or otherwise your routing is a bit odd. If you're NOT using 127.0.0.1, then you need to allow access to port 631 in the same way that you have allowed access to ports 80, 443 and 22. Enjoy
Attachment:
signature.asc
Description: Digital signature