If you have a problem and want to report it, please send mail about it to:

	Linux-IPSEC Mailing List <linux-ipsec@clinet.fi>

For a number of reasons, we prefer that problem reports and discussions
go to the list, not directly to us.  Normally we will respond to the list.
(Beware that the list goes worldwide; US citizens, read doc/exportlaws!)
If you're using this software, you really should be on the list; to get
onto it, send mail that looks about like this:

	To: Majordomo@clinet.fi

	help
	subscribe linux-ipsec
	end

If you do send private mail to us or want a private reply from us, please
make sure that the return address on your mail (From or Reply-To header)
is a valid one.  We lack time and energy to try to unravel addresses that
have been mangled in a futile attempt to confuse spammers. 

In your mail, please include:

+ a brief description of the problem

+ which release of Linux FreeS/WAN is having the problem (see README)

+ whether you have made any changes to the release

+ what distribution of Linux you've got (e.g. "Red Hat release 4.2")

+ what release of the Linux kernel you've got (a number like 2.0.33)

+ what your network setup is (subnets, gateway addresses, etc.)

+ what you were trying to do with Linux FreeS/WAN

+ detailed instructions for reproducing the problem

+ exactly what went wrong, in detail

+ if it's a compile problem, the actual output from make (preferably
	edited down to only the relevant part, but when in doubt, be
	as complete as you can) showing the problem

+ if it's a run-time problem, the output from "ipsec barf" on all
	machines involved

+ any other error messages, complaints, etc. that you saw (please send
	the complete text of the messages, not just a summary of them)

+ a fix, if you have one (but remember, you are sending mail to people
	all over the world; US residents and US citizens in particular,
	please read doc/exportlaws before sending code -- even small
	bug fixes -- to the list or to us)

When in doubt about whether to include some seemingly-trivial item of
information, include it.  It is rare for problem reports to have too
much information, and common for them to have too little.

This file is RCSID $Id: prob.report,v 1.6 1999/04/05 21:27:11 henry Exp $