shorewall6-accounting(5)
accounting – Shorewall6 Accounting file
Synopsis
/etc/shorewall6/accounting
Description
shorewall6 show accounting command. Beginning with Shorewall 4.4.18, the accounting structure can be created with three root chains:- •
accountin: Rules that are valid in theINPUTchain (may not specify an output interface).
- •
accountout: Rules that are valid in the OUTPUT chain (may not specify an input interface or a MAC address).
- •
accounting: Other rules.
The new structure is enabled by sectioning the accounting file in a manner similar to the m[blue]rules filem[][1]. The sections are INPUT, OUTPUT and FORWARD and must appear in that order (although any of them may be omitted). The first non-commentary record in the accounting file must be a section header when sectioning is used.
Warning
If sections are not used, the Shorewall rules compiler cannot detect certain violations of netfilter restrictions. These violations can result in run-time errors such as the following:ip6tables-restore v1.4.13: Can’t use -o with INPUTBeginning with Shorewall 4.4.20, the ACCOUNTING_TABLE setting was added to shorewall.conf and shorewall6.conf. That setting determines the Netfilter table (filter or mangle) where the accounting rules are added. When ACCOUNTING_TABLE=mangle is specified, the available sections arePREROUTING,INPUT,OUTPUT,FORWARDandPOSTROUTING. Section headers have the form:[?]SECTIONsection-name The optional "?" was added in Shorewalll 4.6.0 and is preferred. Existing configurations may be converted to use this form using theshorewall6 updatecommand. When sections are enabled:- • A jump to a user-defined accounting chain must appear before entries that add rules to that chain. This eliminates loops and unreferenced chains.
- • An output interface may not be specified in the
PREROUTINGandINPUTsections. - • In the
OUTPUTandPOSTROUTINGsections: - • An input interface may not be specified
- • Jumps to a chain defined in the
INPUTorPREROUTINGsections that specifies an input interface are prohibited - • MAC addresses may not be used
- • Jump to a chain defined in the
INPUTorPREROUTINGsection that specifies a MAC address are prohibited. - • The default value of the CHAIN column is:
- •
accountinin theINPUTsection - •
accountoutin theOUTPUTsection - •
accountfwdin theFORWARDsection - •
accountprein thePREROUTINGsection - •
accountpostin thePOSTROUTINGsection - • Traffic addressed to the firewall goes through the rules defined in the INPUT section.
- • Traffic originating on the firewall goes through the rules defined in the OUTPUT section.
- • Traffic being forwarded through the firewall goes through the rules from the FORWARD sections.
- What to do when a matching packet is found.
COUNT - Simply count the match and continue with the next rule
- Count the match and don’t attempt to match any other accounting rules in the chain specified in the
CHAINcolumn. - Where chain is the name of a chain; shorewall6 will create the chain automatically if it doesn’t already exist. If a second chain is mentioned in the CHAIN column, then a jump from this second chain to chain is created. If no chain is named in the CHAIN column, then a jump from the default chain to chain is created. If
:COUNTis included, a counting rule matching this entry will be added to chain. The chain may not exceed 29 characters in length and may be composed of letters, digits, dash (‘-‘) and underscore (‘_’). - Like the previous option without the
:COUNTpart. - Added in Shorewall 4.5.16. Allows free form ip6tables matches to be specified following a ‘;’. In the generated ip6tables rule(s), the free form matches will follow any matches that are generated by the column contents.
- Added in Shorewall 4.5.7. Provides a form of accounting that survives
shorewall stop/shorewallstart andshorewall restart. Requires the NFaccnt Match capability in your kernel and iptables. object names an nfacct object (see man nfaccnt(8)). Multiple rules can specify the same object; all packets that match any of the rules increment the packet and bytes count of the object. Prior to Shorewall 4.5.16, only one object could be specified. Beginning with Shorewall 4.5.16, an arbitrary number of objects may be given. With Shorewall 4.5.16 or later, an nfacct object in the list may optionally be followed by!to indicate that the nfacct object will be incremented unconditionally for each packet. When!is omitted, the object will be incremented only if all of the matches in the rule succeed. - Causes each matching packet to be sent via the currently loaded logging back end (usually nfnetlink_log) where it is available to accounting daemons through a netlink socket.
- The remainder of the line is treated as a comment which is attached to subsequent rules until another ?COMMENT line is found or until the end of the file is reached. To stop adding comments to rules, use a line with only the word ?COMMENT.
- The name of a chain. If specified as
–theaccountingchain is assumed when the file is un-sectioned. When the file is sectioned, the default is one of accountin, accountout, etc. depending on the section. This is the chain where the accounting rule is added. The chain will be created if it doesn’t already exist. The chain may not exceed 29 characters in length. - Packet Source. The name of an interface, an address (host or net) or an interface name followed by ":" and a host or net address. An ipset name is also accepted as an address.
- Packet Destination. Format same as
SOURCEcolumn. This column was formerly labelled DESTINATION. - A protocol-name (from protocols(5)), a protocol-number,
ipp2p,ipp2p:udporipp2p:allBeginning with Shorewall 4.5.12, this column can accept a comma-separated list of protocols. This column was formerly labelled PROTOCOL. - Destination Port number. Service name from services(5) or port number. May only be specified if the protocol is TCP (6), UDP (17), DCCP (33), SCTP (132) or UDPLITE (136). You may place a comma-separated list of port names or numbers in this column if your kernel and ip6tables include multi-port match support. If the PROTOCOL is
ipp2pthen this column must contain an ipp2p-option ("ip6tables -m ipp2p –help") without the leading "–". If no option is given in this column,ipp2pis assumed. This column was formerly labelled DEST PORT(S). - Service name from services(5) or port number. May only be specified if the protocol is TCP (6), UDP (17), DCCP (33), SCTP (132) or UDPLITE (136). You may place a comma-separated list of port numbers in this column if your kernel and ip6tables include multi-port match support. Beginning with Shorewall 4.5.15, you may place ‘=’ in this column, provided that the DPORT column is non-empty. This causes the rule to match when either the source port or the destination port in a packet matches one of the ports specified in DPORT. Use of ‘=’ requires multi-port match in your iptables and kernel. This column was formerly labelled SOURCE PORT(S).
- This column may only be non-empty if the
CHAINisOUTPUT. When this column is non-empty, the rule applies only if the program generating the output is running under the effective user and/or group specified (or is NOT running under that id if "!" is given). Examples: joe - program must be run by joe
- program must be run by a member of the ‘kids’ group
- program must not be run by a member of the ‘kids’ group
- #program named upnpd
Important
The ability to specify a program name was removed from Netfilter in kernel version 2.6.14. This column was formerly labelled USER/GROUP.- Defines a test on the existing packet or connection mark. The rule will match only if the test returns true. If you don’t want to define a test but need to specify anything in the following columns, place a "-" in this field. !
- Inverts the test (not equal)
- Value of the packet or connection mark.
- A mask to be applied to the mark before testing.
- Designates a connection mark. If omitted, the packet mark’s value is tested.
- The option-list consists of a comma-separated list of options from the following list. Only packets that will be encrypted or have been decrypted via an SA that matches these options will have their source address changed. May only be specified when sections are used.
reqid=number - where number is specified using setkey(8) using the ‘unique:number option for the SPD level.
- where number is the SPI of the SA used to encrypt/decrypt packets.
- IPSEC Encapsulation Protocol
- sets the MSS field in TCP packets
- IPSEC mode
- only available with mode=tunnel
- only available with mode=tunnel
- Means that packets must match all rules.
- Separates rules; can only be used with strict
- When used by itself, causes all traffic that will be encrypted/encapsulated or has been decrypted/un-encapsulated to match the rule.
- When used by itself, causes all traffic that will not be encrypted/encapsulated or has been decrypted/un-encapsulated to match the rule.
- May only be used in the FORWARD section and must be the first or the only item the list. Indicates that matching packets have been decrypted in input.
- May only be used in the FORWARD section and must be the first or the only item in the list. Indicates that matching packets will be encrypted on output.
- • A chain NAME appearing in the ACTION column must be a chain branched either directly or indirectly from the
accipsecinoraccipsecoutchain. - • The CHAIN column must contain either
accipsecinoraccipsecoutor a chain branched either directly or indirectly from those chains. - • These rules will NOT appear in the
accountingchain. - The header-list consists of a comma-separated list of headers from the following list.
auth,ah, or51 - Authentication Headers extension header.
- Encrypted Security Payload extension header.
- Hop-by-hop options extension header.
- IPv6 Route extension header.
- IPv6 fragmentation extension header.
- No next header
- Any protocol header.
- 1.
- rules file
- http://www.shorewall.net/manpages6/shorewall6-rules.html
- 2.
- http://www.shorewall.net/Accounting.html
- http://www.shorewall.net/Accounting.html
- 3.
- http://www.shorewall.net/shorewall_logging.html
- http://www.shorewall.net/shorewall_logging.html
- 4.
- http://www.shorewall.net/configuration_file_basics.htm#Pairs
- http://www.shorewall.net/configuration_file_basics.htm#Pairs
The columns in the file are as follows (where the column name is followed by a different name in parentheses, the different name is used in the alternate specification syntax). ACTION – {COUNT|DONE|chain[:{COUNT|JUMP}]|[?]COMMENT comment}
DONE
chain[:COUNT]
chain:JUMP
INLINE
NFACCT({object[!]}[,…])
NFLOG[(nflog-parameters)] – Added in Shorewall-4.4.20.
?COMMENT
CHAIN – {–|chain}
SOURCE – {–|any|all|interface|interface:[address]|address}
DEST – {–|any|all|interface|interface:[address]|address}
PROTO – {–|any|all|protocol-name|protocol-number|ipp2p[:{udp|all}]}
DPORT – {–|any|all|ipp2p-option|port-name-or-number[,port-name-or-number]…}
SPORT – {–|any|all|port-name-or-number[,port-name-or-number]…}
USER – [!][user-name-or-number][:group-name-or-number][+program-name]
:kids
!:kids
+upnpd
MARK – [!]value[/mask][:C]
value
mask
:C
IPSEC – option-list (Optional – Added in Shorewall 4.4.13 but broken until 4.5.4.1 )
spi=<number>
proto=ah|esp|ipcomp
mss=number
mode=transport|tunnel
tunnel-src=address[/mask]
tunnel-dst=address[/mask]
strict
next
yes or ipsec
no or none
in
out
If this column is non-empty and sections are not used, then:
HEADERS – [!][any:|exactly:]header-list (Optional – Added in Shorewall 4.4.15)
esp, or 50
hop, hop-by-hop or 0
route, ipv6-route or 41
frag, ipv6-frag or 44
none, ipv6-nonxt or 59
proto, protocol or 255
If any: is specified, the rule will match if any of the listed headers are present. If exactly: is specified, the will match packets that exactly include all specified headers. If neither is given, any: is assumed. If ! is entered, the rule will match those packets which would not be matched when ! is omitted.
In all of the above columns except ACTION and CHAIN, the values –, any and all may be used as wildcards. Omitted trailing columns are also treated as wildcards.
Files
/etc/shorewall6/accounting
See Also
m[blue]http://www.shorewall.net/Accounting.htmlm[][2]
m[blue]http://www.shorewall.net/shorewall_logging.htmlm[][3]
m[blue]http://www.shorewall.net/configuration_file_basics.htm#Pairsm[][4]
shorewall6(8), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5), shorewall6-maclist(5), shorewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-providers(5), shorewall6-rtrules(5), shorewall6-routestopped(5), shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5), shorewall6-mangle(5), shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5)