1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>Firewalling and packets accounting: When everything goes wrong!</TITLE>
<LINK HREF="firewall-8.html" REL=next>
<LINK HREF="firewall-6.html" REL=previous>
<LINK HREF="firewall.html#toc7" REL=contents>
</HEAD>
<BODY>
<A HREF="firewall-8.html">Next</A>
<A HREF="firewall-6.html">Previous</A>
<A HREF="firewall.html#toc7">Contents</A>
<HR>
<H2><A NAME="s7">7. When everything goes wrong!</A></H2>
<P>Firewalling in <EM>Linux</EM> may be deadly. An improper
configuration can bring the network to its knees. One
command that may save your day is
<P>
<BLOCKQUOTE><CODE>
<PRE>
netconf --resetfw
</PRE>
</CODE></BLOCKQUOTE>
<P>This command deactivates all firewalling rules. It does
not affect the configuration -- it affects only the working set.
<P>
<BLOCKQUOTE><CODE>
<PRE>
netconf --update
</PRE>
</CODE></BLOCKQUOTE>
<P>will reactivate the rules. You may need to use those
two commands to check out if a network malfunction is caused
by your firewalling rules or not.
<P>
<P>
<HR>
<A HREF="firewall-8.html">Next</A>
<A HREF="firewall-6.html">Previous</A>
<A HREF="firewall.html#toc7">Contents</A>
</BODY>
</HTML>
|
