Date: Fri, 27 Jun 2003 09:06:28 -0700 From: Jeremy Bingham <jeremy@satanosphere.com> To: Han Hwei Woo <hhwoo@argosy.ca> Cc: freebsd-questions@freebsd.org Subject: Re: NAT Dropping Internal Connection Message-ID: <20030627160628.GA80468@lagash.satanosphere.com> In-Reply-To: <009101c33cb2$1514b630$0200a8c0@a7n8x> References: <MIEPLLIBMLEEABPDBIEGIEDEEAAA.FBSD_User@a1poweruser.com> <20030625191607.GD69633@lagash.satanosphere.com> <009101c33cb2$1514b630$0200a8c0@a7n8x>
next in thread | previous in thread | raw e-mail | index | archive | help
--FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 27/06/03 10:43 -0300, Han Hwei Woo wrote: > Is there any reason you are running both ipfw + ipfilter? Although they > probably should play nice together, it might be best not to tempt fate, > especially when you're experiencing problems. Also, are you using ipnat or > natd to perform NAT? I tried taking IPDIVERT out of my kernel, but that killed NAT, so I had to revert to the old kernel. I'm still playing with it. I had been told that running both IPFIREWALL and IPDIVERT was unecessary. I am running natd to perform NAT (with the -dynamic flag). -j >=20 > ----- Original Message -----=20 > From: "Jeremy Bingham" <jeremy@satanosphere.com> > To: <freebsd-questions@freebsd.org> > Sent: Wednesday, June 25, 2003 4:16 PM > Subject: Re: NAT Dropping Internal Connection >=20 > On 25/06/03 14:39 -0400, FBSD_User wrote: > > Sounds like hardware problem with the switch or hub on your LAN. >=20 > Rebooting the machine makes the NAT stuff work again. Could the hub > still be a problem in that case? >=20 > -j >=20 > > > > -----Original Message----- > > From: owner-freebsd-questions@freebsd.org > > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Jeremy > > Bingham > > Sent: Wednesday, June 25, 2003 2:25 PM > > To: freebsd-questions@freebsd.org > > Subject: NAT Dropping Internal Connection > > > > I have a P-200 running 4.8-STABLE running as a NAT box at home. It > > runs > > well, except that periodically it will drop it's connection on the > > internal side of the network. The external interface still works, > > but the > > internal machines can't ping the NAT box at all and the NAT box > > can't > > ping the internal machines. > > > > I've looked through the mailing lists and google for hints why this > > might be happening, but I can't find anything. /var/log/messages > > also > > reveals nothing. Here are the relevant kernel options: > > > > options IPFIREWALL > > options IPFIREWALL_FORWARD > > options IPFIREWALL_DEFAULT_TO_ACCEPT > > options IPDIVERT > > options IPFILTER > > options IPSTEALTH > > options RANDOM_IP_ID > > options TCP_DROP_SYNFIN > > > > Would any of those cause the problem, or is there a kernel option > > that > > I'm accidentally leaving off? > > > > Thanks, > > > > -Jeremy Bingham > > > > > > ---------------------------------------------- > > /* You are not expected to understand this. */ > > > > Captain_Tenille > > http://www.satanosphere.com/ > > jeremy@satanosphere.com > > >=20 > --=20 >=20 > ---------------------------------------------- > /* You are not expected to understand this. */ >=20 > Captain_Tenille > http://www.satanosphere.com/ > jeremy@satanosphere.com >=20 --=20 ---------------------------------------------- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ jeremy@satanosphere.com --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE+/GuDz9BfgBOfXn0RArVKAKDJh2H9UMVSjDpxbczH+xz2cAeZXwCglMAo jXsDXzSYlZxjEAjXDCU79Gc= =21ei -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030627160628.GA80468>