From owner-freebsd-questions Sun Apr 26 23:52:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00313 for freebsd-questions-outgoing; Sun, 26 Apr 1998 23:52:44 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00261 for ; Sun, 26 Apr 1998 23:52:32 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id BAA00601; Mon, 27 Apr 1998 01:51:42 -0400 (EDT) Date: Mon, 27 Apr 1998 01:51:42 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: Brian Somers cc: FreeBSD-questions@FreeBSD.ORG Subject: Re: Network stuff In-Reply-To: <199804270617.HAA10712@awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Apr 1998, Brian Somers wrote: > > I tried wrapping that in truss to see what's failing, and it's the > > connect call, with EACCESS. That's only supposed to happen to unix > [.....] > > Sounds like a firewall to me :-] I've gotten several comments like that, and while I hadn't thought of that myself, I think the reason is that I've never had any IPFIREWALL stuff in any of my kernels. I think it has to do with my odd assortment of network numbers, matched so they don't work well with netmasks. I'll go back to reading network stuff again. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message