mirror of
https://github.com/freebsd/freebsd-src
synced 2024-10-19 14:54:24 +00:00
43405724ec
The bugfix (ipfw2.c) makes the handling of port numbers with
a dash in the name, e.g. ftp-data, consistent with old ipfw:
use \\ before the - to consider it as part of the name and not
a range separator.
The new feature (all this description will go in the manpage):
each rule now belongs to one of 32 different sets, which can
be optionally specified in the following form:
ipfw add 100 set 23 allow ip from any to any
If "set N" is not specified, the rule belongs to set 0.
Individual sets can be disabled, enabled, and deleted with the commands:
ipfw disable set N
ipfw enable set N
ipfw delete set N
Enabling/disabling of a set is atomic. Rules belonging to a disabled
set are skipped during packet matching, and they are not listed
unless you use the '-S' flag in the show/list commands.
Note that dynamic rules, once created, are always active until
they expire or their parent rule is deleted.
Set 31 is reserved for the default rule and cannot be disabled.
All sets are enabled by default. The enable/disable status of the sets
can be shown with the command
ipfw show sets
Hopefully, this feature will make life easier to those who want to
have atomic ruleset addition/deletion/tests. Examples:
To add a set of rules atomically:
ipfw disable set 18
ipfw add ... set 18 ... # repeat as needed
ipfw enable set 18
To delete a set of rules atomically
ipfw disable set 18
ipfw delete set 18
ipfw enable set 18
To test a ruleset and disable it and regain control if something
goes wrong:
ipfw disable set 18
ipfw add ... set 18 ... # repeat as needed
ipfw enable set 18 ; echo "done "; sleep 30 && ipfw disable set 18
here if everything goes well, you press control-C before
the "sleep" terminates, and your ruleset will be left
active. Otherwise, e.g. if you cannot access your box,
the ruleset will be disabled after the sleep terminates.
I think there is only one more thing that one might want, namely
a command to assign all rules in set X to set Y, so one can
test a ruleset using the above mechanisms, and once it is
considered acceptable, make it part of an existing ruleset.
|
||
|---|---|---|
| .. | ||
| libalias | ||
| accf_data.c | ||
| accf_http.c | ||
| icmp6.h | ||
| icmp_var.h | ||
| if_atm.c | ||
| if_atm.h | ||
| if_ether.c | ||
| if_ether.h | ||
| igmp.c | ||
| igmp.h | ||
| igmp_var.h | ||
| in.c | ||
| in.h | ||
| in_cksum.c | ||
| in_gif.c | ||
| in_gif.h | ||
| in_pcb.c | ||
| in_pcb.h | ||
| in_proto.c | ||
| in_rmx.c | ||
| in_systm.h | ||
| in_var.h | ||
| ip.h | ||
| ip6.h | ||
| ip_divert.c | ||
| ip_dummynet.c | ||
| ip_dummynet.h | ||
| ip_ecn.c | ||
| ip_ecn.h | ||
| ip_encap.c | ||
| ip_encap.h | ||
| ip_flow.c | ||
| ip_flow.h | ||
| ip_fw.c | ||
| ip_fw.h | ||
| ip_fw2.c | ||
| ip_icmp.c | ||
| ip_icmp.h | ||
| ip_id.c | ||
| ip_input.c | ||
| ip_mroute.c | ||
| ip_mroute.h | ||
| ip_output.c | ||
| ip_var.h | ||
| ipprotosw.h | ||
| raw_ip.c | ||
| tcp.h | ||
| tcp_debug.c | ||
| tcp_debug.h | ||
| tcp_fsm.h | ||
| tcp_input.c | ||
| tcp_output.c | ||
| tcp_reass.c | ||
| tcp_seq.h | ||
| tcp_subr.c | ||
| tcp_syncache.c | ||
| tcp_timer.c | ||
| tcp_timer.h | ||
| tcp_timewait.c | ||
| tcp_usrreq.c | ||
| tcp_var.h | ||
| tcpip.h | ||
| udp.h | ||
| udp_usrreq.c | ||
| udp_var.h | ||