CRASHWRITE(1) CrashMail CRASHWRITE(1)NAME
crashwrite - Creates PKT file from text file
SYNOPSIS
crashwrite DIR directory [FROMNAME string] [FROMADDR node] [TONAME string] [TOADDR node] [SUBJECT string] [AREA area] [ORIGIN origin] [TEXT
filename] [NOMSGID] [FILEATTACH] [PKTFROMADDR node] [PKTTOADDR node] PASSWORD [string]
DESCRIPTION
CrashWrite reads a text file and creates a .pkt file that can be processed by CrashMail. This can be used to post announcements and other
messages in areas. The best way to use CrashWrite is to let it generate packets in a separate directory and then toss them with TOSSDIR
NOSECURITY.
There are many keywords for CrashWrite. All keywords are optional except for DIRECTORY. If you do not enter a keyword, a default value will
be used.
OPTIONS
FROMNAME string
FROMADDR node
TONAME string
TOADDR node
SUBJECT string
Use these keywords to set the header of the message. You only need to enter TONAME and TOADDR for netmails.
PKTFROMADDR node
PKTTOADDR node
Use these if you want to set the origin and destination address of the packet to something other than the origin and destination
address of the message inside the packet. If you do not specify these keywords, FROMADDR and TOADDR will be used for the packet as
well.
PASSWORD string
You can use this keyword to set a password for the packet. The maximum length of the password is eight characters.
AREA area
The area the message should be posted in. If you do not enter an area, the message will be sent as a netmail.
ORIGIN origin
The origin line for the message. This keyword has no effect for netmail messages.
DIR directory
The directory where the packet should be placed.
TEXT filename
The name of a text file that should be included as the message text.
NOMSGID
Prevents CrashWrite from adding a MSGID line.
FILEATTACH
Sets the file-attach flag for netmails. The filename should be put in the subject line.
SEE ALSO crashmail(1)AUTHOR
CrashMail is written by Johan Billing <billing@df.lth.se>
This manual page was written by Peter Karlsson <peter@softwolves.pp.se>
Johan Billing 1999-08-01 CRASHWRITE(1)
Check Out this Related Man Page
NG_IPFW(4) BSD Kernel Interfaces Manual NG_IPFW(4)NAME
ng_ipfw -- interface between netgraph and IP firewall
SYNOPSIS
#include <netgraph/ng_ipfw.h>
DESCRIPTION
The ipfw node implements interface between ipfw(4) and netgraph(4) subsystems.
HOOKS
The ipfw node supports an arbitrary number of hooks, which must be named using only numeric characters.
OPERATION
Once the ng_ipfw module is loaded into the kernel, a single node named ipfw is automatically created. No more ipfw nodes can be created.
Once destroyed, the only way to recreate the node is to reload the ng_ipfw module.
Packets can be injected into netgraph(4) using either the netgraph or ngtee commands of the ipfw(8) utility. These commands require a
numeric cookie to be supplied as an argument. Packets are sent out of the hook whose name equals the cookie value. If no hook matches,
packets are discarded. Packets injected via the netgraph command are tagged with struct ng_ipfw_tag. This tag contains information that
helps the packet to re-enter ipfw(4) processing, should the packet come back from netgraph(4) to ipfw(4).
struct ng_ipfw_tag {
struct m_tag mt; /* tag header */
struct ip_fw *rule; /* matching rule */
uint32_t rule_id; /* matching rule id */
uint32_t chain_id; /* ruleset id */
struct ifnet *ifp; /* interface, for ip_output */
int dir; /* packet direction */
#define NG_IPFW_OUT 0
#define NG_IPFW_IN 1
};
Packets received by a node from netgraph(4) must be tagged with struct ng_ipfw_tag tag. Packets re-enter IP firewall processing at the next
rule. If no tag is supplied, packets are discarded.
CONTROL MESSAGES
This node type supports only the generic control messages.
SHUTDOWN
This node shuts down upon receipt of a NGM_SHUTDOWN control message. Do not do this, since the new ipfw node can only be created by reload-
ing the ng_ipfw module.
SEE ALSO ipfw(4), netgraph(4), ipfw(8), mbuf_tags(9)HISTORY
The ipfw node type was implemented in FreeBSD 6.0.
AUTHORS
The ipfw node was written by Gleb Smirnoff <glebius@FreeBSD.org>.
BSD June 10, 2009 BSD