Date: Fri, 3 Aug 2001 12:26:41 -0700 From: "Scott Reese" <sreese@codysbooks.com> To: <freebsd-questions@FreeBSD.ORG>, "Matthew Hagerty" <mhagerty@voyager.net> Subject: Re: natd[135]:failed to write packet back Message-ID: <015801c11c52$394c1cf0$1800a8c0@borges> References: <5.0.2.1.2.20010803150112.02841d30@pop.voyager.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Hagerty wrote: > It usually means that the external interface went down. That is the > message I get when my cable modem service goes out for some reason (loss of > power, bad weather, farmer with a back-hoe, etc.) It could also mean that > your configuration is wrong or you have the cable modem plugged into the > wrong interface (assuming a cable modem set-up.) But that usually gives a > slightly different error. It's close to a cable modem set up. I'm using Sprint Broadbrand and the external interface occasionally blinks in and out (receives/sends no signal for a second and then resumes). I wonder if that could be what this means? Hmmmm...They're always late at night, so I wonder if that's when Sprint chooses to do maintenance...? > NATd is pretty simple to set-up and the man page is very complete. I also > posted a complete step-by-step procedure for configuring NATd, about 2 days > ago. Check the archive. Yes, it was pretty simple to set up and I should add that it's working beautifully. I was just wondering what the message meant and if there was any way to fix it (if it, in fact, was a problem). BTW, I browsed the archive, but I can't seem to find your tutorial posting... Thank you! -Scott 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?015801c11c52$394c1cf0$1800a8c0>