From owner-freebsd-questions Mon Dec 21 19:30:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12574 for freebsd-questions-outgoing; Mon, 21 Dec 1998 19:30:15 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12536 for ; Mon, 21 Dec 1998 19:30:08 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forresta (forrie.ne.mediaone.net [24.128.73.118]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id WAA02124 for ; Mon, 21 Dec 1998 22:29:25 -0500 (EST) Message-Id: <4.1.19981221222756.0093d840@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 21 Dec 1998 22:30:58 -0500 To: freebsd-questions@FreeBSD.ORG From: Forrest Aldrich Subject: Issues with if_xl.c and natd Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm tracking down what might be some bug in the interaction between if_xl.c and perhaps natd. Though I seem to be the only person using dual 3c905-TX cards in this fashion. I'm also running an internal RFC net (outside is assigned dynamically by cable modem ISP). Is there by chance anyone else using these cards in this configuration? The symptoms are that everything works correctly as long as the firewall rules are kept as OPEN. I've checked this with a known working configuration from someone else who is using different NICs. I've ordered a couple of Kingstons to test (hopefully tomorrow). Other war stories would be of interest in tracking down what the problem is. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message