SHOREWALL6-TCFILTER(5) [FIXME: manual] SHOREWALL6-TCFILTER(5)NAME
tcfilters - shorewall6 u32 classifier rules file
SYNOPSIS
/etc/shorewall6/tcfilters
DESCRIPTION
Entries in this file cause packets to be classified for traffic shaping.
Beginning with Shorewall 4.4.15, the file may contain entries for both IPv4 and IPv6. By default, all rules apply to IPv6 but that can be
changed by inserting a line as follows:
IPV4
Following entries apply to IPv4.
IPV6
Following entries apply to IPv6
ALL
Following entries apply to both IPv4 and IPv6. Each entry is processed twice; once for IPv4 and once for IPv6.
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).
CLASS - interface:class
The name or number of an interface defined in shorewall6-tcdevices[1](5) followed by a class number defined for that interface in
shorewall6-tcclasses[2](5).
SOURCE - {-|address}
Source of the packet. May be a host or network address. DNS names are not allowed.
DEST - {-|address}}
Destination of the packet. May be a host or network address. DNS names are not allowed.
PROTO - {-|protocol-number|protocol-name|all}
Protocol.
DEST PORT (dport) - [-|port-name-or-number]
Optional destination Ports. A Port name (from services(5)) or a port number; if the protocol is icmp, this column is interpreted as the
destination icmp-type(s).
SOURCE PORT (sport) - [-|port-name-or-number]
Optional source port.
TOS - [-|tos]
Optional - specifies the value of the TOS field. The tos value can be any of the following:
o tos-minimize-delay
o tos-maximuze-throughput
o tos-maximize-reliability
o tos-minimize-cost
o tos-normal-service
o hex-number
o hex-number/hex-number
The hex-numbers must be exactly two digits (e.g., 0x04)x.
LENGTH - [-|number]
Optional. Must be a power of 2 between 32 and 8192 inclusive. Packets with a total length that is strictly less than the specified
number will match the rule.
EXAMPLE
Example 1:
Place all 'ping' traffic on interface 1 in class 10. Note that ALL cannot be used because IPv4 ICMP and IPv6 ICMP are two different
protocols.
#CLASS SOURCE DEST PROTO DEST
# PORT
IPV4
1:10 0.0.0.0/0 0.0.0.0/0 icmp echo-request
1:10 0.0.0.0/0 0.0.0.0/0 icmp echo-reply
IPV6
1:10 ::/0 ::/0 icmp6 echo-request
1:10 ::/0 ::/0 icmp6 echo-reply
FILES
/etc/shorewall6/tcfilters
SEE ALSO
http://shorewall.net/traffic_shaping.htm
http://shorewall.net/MultiISP.html
http://shorewall.net/PacketMarking.html
NOTES
1. shorewall6-tcdevices
http://www.shorewall.net/manpages6/shorewall6-tcdevices.html
2. shorewall6-tcclasses
http://www.shorewall.net/manpages6/shorewall6-tcclasses.html
[FIXME: source] 06/28/2012 SHOREWALL6-TCFILTER(5)
Check Out this Related Man Page
SHOREWALL6-PROXYNDP(5) [FIXME: manual] SHOREWALL6-PROXYNDP(5)NAME
proxyndp - Shorewall6 Proxy NDP file
SYNOPSIS
/etc/shorewall6/proxyndp
DESCRIPTION
This file was added in Shoreall 4.4.16 and is used to define Proxy NDP. There is one entry in this file for each IPv6 address to be
proxied.
The columns in the file are as follows.
ADDRESS - address
IPv6 Address.
INTERFACE - interface (Optional)
Local interface where system with the ip address in ADDRESS is connected. Only required when the HAVEROUTE column is left empty or is
set to no or No.
EXTERNAL - interface
External Interface to be used to access this system from the Internet.
HAVEROUTE - [-|Yes|No]
If there is already a route from the firewall to the host whose address is given, enter Yes or yes in this column. Otherwise, enter no
or No or leave the column empty and Shorewall will add the route for you. If Shorewall6 adds the route, its persistence depends on the
value of thePERSISTENT column contains Yes; otherwise, shorewall6 stop or shorewall clear6 will delete the route.
PERSISTENT - [-|Yes|No]
If HAVEROUTE is No or no, then the value of this column determines if the route added by Shorewall persists after a shorewall6 stop or
a shorewall6 clear. If this column contains Yes or yes then the route persists; If the column is empty or contains No or no then the
route is deleted by shorewall6 stop or shorewall6 clear.
EXAMPLE
Example 1:
Host with IPv6 2001:470:b:227::44 is connected to interface eth1 and we want hosts attached via eth0 to be able to access it using that
address.
#ADDRESS INTERFACE EXTERNAL
2001:470:b:227::44 eth1 eth0
FILES
/etc/shorewall6/proxyndp
SEE ALSO
http://shorewall.net/configuration_file_basics.htm#Pairs
shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-exclusion(5), shorewall6-hosts(5),
shorewall6-interfaces(5), shorewall6-maclist(5), shorewall6-nesting(5), shoewall6-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-tcrules(5), shorewall6-tos(5), shorewall6-tunnels(5),
shorewall6-zones(5)
[FIXME: source] 06/28/2012 SHOREWALL6-PROXYNDP(5)