Date: Mon, 18 Oct 1999 20:05:18 -0700 From: bmah@CA.Sandia.GOV (Bruce A. Mah) To: douglas@artswire.org Cc: bmah@california.sandia.gov, freebsd-questions@FreeBSD.ORG Subject: Re: NATD - Console Message Question Message-ID: <199910190305.UAA23185@nimitz.ca.sandia.gov> In-Reply-To: Your message of "Mon, 18 Oct 1999 21:16:19 EDT." <000c01bf19cf$8d313440$0105a8c0@sterndog.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1490116832P Content-Type: text/plain; charset=us-ascii If memory serves me right, "Douglas Cohen" wrote: > So how do I figure out what packets natd is unable to write back? Arg...I knew that was next. :-) Hopefully someone will come up with a better answer than this, but I recommend checking the state of your ipfw rules to see which ones triggered (use "ipfw -at list", but you probably want to RTFM for some more details). I'm basing this on your "Permission denied" message, but I actually haven't experienced this problem. (Probably I will, if I start playing around with ipfw some more, like I should.) Hope this helps... Bruce. --==_Exmh_1490116832P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: Zhb0euk4FTGiQ8OMpMk1jzhYRLidFUa5 iQA/AwUBOAvf7djKMXFboFLDEQIv9QCgglRRk2G9kYd6Bx5GSaSThnEXjkAAoMr9 XSmQ33A6cgtDWI7gk7QArVOG =Tyvq -----END PGP SIGNATURE----- --==_Exmh_1490116832P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910190305.UAA23185>