1.TH IPFS 8
2.SH NAME
3ipfs \- saves and restores information for NAT and state tables.
4.SH SYNOPSIS
5.B ipfs
6[-nv] -l
7.PP
8.B ipfs
9[-nv] -u
10.PP
11.B ipfs
12[-nv] [
13.B \-d
14<\fIdirname\fP>
15] -R
16.PP
17.B ipfs
18[-nv] [
19.B \-d
20<\fIdirname\fP>
21] -W
22.PP
23.B ipfs
24[-nNSv] [
25.B \-f
26<\fIfilename\fP>
27] -r
28.PP
29.B ipfs
30[-nNSv] [
31.B \-f
32<\fIfilename\fP>
33] -w
34.PP
35.B ipfs
36[-nNSv]
37.B \-f
38<\fIfilename\fP>
39.B \-i
40<if1>,<if2>
41.SH DESCRIPTION
42.PP
43\fBipfs\fP allows state information created for NAT entries and rules using
44\fIkeep state\fP to be locked (modification prevented) and then saved to disk,
45allowing for the system to experience a reboot, followed by the restoration
46of that information, resulting in connections not being interrupted.
47.SH OPTIONS
48.TP
49.B \-d
50Change the default directory used with
51.B \-R
52and
53.B \-W
54options for saving state information.
55.B \-n
56Don't actually take any action that would effect information stored in
57the kernel or on disk.
58.TP
59.B \-v
60Provides a verbose description of what's being done.
61.TP
62.B \-N
63Operate on NAT information.
64.TP
65.B \-S
66Operate on filtering state information.
67.TP
68.B \-u
69Unlock state tables in the kernel.
70.TP
71.B \-l
72Unlock state tables in the kernel.
73.TP
74.B \-r
75Read information in from the specified file and load it into the
76kernel. This requires the state tables to have already been locked
77and does not change the lock once comlete.
78.TP
79.B \-w
80Write information out to the specified file and from the kernel.
81This requires the state tables to have already been locked
82and does not change the lock once comlete.
83.TP
84.B \-R
85Restores all saved state information, if any, from two files,
86\fIipstate.ipf\fP and \fIipnat.ipf\fP, stored in the \fI/var/db/ipf\fP
87directory unless otherwise specified the
88.B \-d
89option is used. The state tables are locked at the beginning of this
90operation and unlocked once complete.
91.TP
92.B \-W
93Saves in-kernel state information, if any, out to two files,
94\fIipstate.ipf\fP and \fIipnat.ipf\fP, stored in the \fI/var/db/ipf\fP
95directory unless otherwise specified the
96.B \-d
97option is used. The state tables are locked at the beginning of this
98operation and unlocked once complete.
99.DT
100.SH FILES
101/var/db/ipf/ipstate.ipf
102.br
103/var/db/ipf/ipnat.ipf
104.br
105/dev/ipl
106.br
107/dev/ipstate
108.br
109/dev/ipnat
110.SH SEE ALSO
111ipf(8), ipl(4), ipmon(8), ipnat(8)
112.SH DIAGNOSTICS
113.PP
114Perhaps the -W and -R operations should set the locking but rather than
115undo it, restore it to what it was previously. Fragment table information
116is currently not saved.
117.SH BUGS
118.PP
119If you find any, please send email to me at darrenr@pobox.com
2.SH NAME
3ipfs \- saves and restores information for NAT and state tables.
4.SH SYNOPSIS
5.B ipfs
6[-nv] -l
7.PP
8.B ipfs
9[-nv] -u
10.PP
11.B ipfs
12[-nv] [
13.B \-d
14<\fIdirname\fP>
15] -R
16.PP
17.B ipfs
18[-nv] [
19.B \-d
20<\fIdirname\fP>
21] -W
22.PP
23.B ipfs
24[-nNSv] [
25.B \-f
26<\fIfilename\fP>
27] -r
28.PP
29.B ipfs
30[-nNSv] [
31.B \-f
32<\fIfilename\fP>
33] -w
34.PP
35.B ipfs
36[-nNSv]
37.B \-f
38<\fIfilename\fP>
39.B \-i
40<if1>,<if2>
41.SH DESCRIPTION
42.PP
43\fBipfs\fP allows state information created for NAT entries and rules using
44\fIkeep state\fP to be locked (modification prevented) and then saved to disk,
45allowing for the system to experience a reboot, followed by the restoration
46of that information, resulting in connections not being interrupted.
47.SH OPTIONS
48.TP
49.B \-d
50Change the default directory used with
51.B \-R
52and
53.B \-W
54options for saving state information.
55.B \-n
56Don't actually take any action that would effect information stored in
57the kernel or on disk.
58.TP
59.B \-v
60Provides a verbose description of what's being done.
61.TP
62.B \-N
63Operate on NAT information.
64.TP
65.B \-S
66Operate on filtering state information.
67.TP
68.B \-u
69Unlock state tables in the kernel.
70.TP
71.B \-l
72Unlock state tables in the kernel.
73.TP
74.B \-r
75Read information in from the specified file and load it into the
76kernel. This requires the state tables to have already been locked
77and does not change the lock once comlete.
78.TP
79.B \-w
80Write information out to the specified file and from the kernel.
81This requires the state tables to have already been locked
82and does not change the lock once comlete.
83.TP
84.B \-R
85Restores all saved state information, if any, from two files,
86\fIipstate.ipf\fP and \fIipnat.ipf\fP, stored in the \fI/var/db/ipf\fP
87directory unless otherwise specified the
88.B \-d
89option is used. The state tables are locked at the beginning of this
90operation and unlocked once complete.
91.TP
92.B \-W
93Saves in-kernel state information, if any, out to two files,
94\fIipstate.ipf\fP and \fIipnat.ipf\fP, stored in the \fI/var/db/ipf\fP
95directory unless otherwise specified the
96.B \-d
97option is used. The state tables are locked at the beginning of this
98operation and unlocked once complete.
99.DT
100.SH FILES
101/var/db/ipf/ipstate.ipf
102.br
103/var/db/ipf/ipnat.ipf
104.br
105/dev/ipl
106.br
107/dev/ipstate
108.br
109/dev/ipnat
110.SH SEE ALSO
111ipf(8), ipl(4), ipmon(8), ipnat(8)
112.SH DIAGNOSTICS
113.PP
114Perhaps the -W and -R operations should set the locking but rather than
115undo it, restore it to what it was previously. Fragment table information
116is currently not saved.
117.SH BUGS
118.PP
119If you find any, please send email to me at darrenr@pobox.com