Date: Fri, 1 Jun 2001 10:38:48 -0400 (EDT) From: John <papalia@UDel.Edu> To: Nick Rogness <nick@rogness.net> Cc: Eric Rosenberry <ericr@dsl-only.net>, <freebsd-questions@FreeBSD.ORG> Subject: RE: Gateway oddness Message-ID: <Pine.SOL.4.31.0106011035460.14041-100000@copland.udel.edu> In-Reply-To: <Pine.BSF.4.21.0106011034540.65888-100000@cody.jharris.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Unfortunately, I had already tried that... I came up with nothing but > > hits in my backup files. In terms of filters, nothing in > > /etc/hosts.allow appears to be a potential cause of the blockage, and > > my entire firewall scheme is as follows: > > > > > divert 8668 ip from any to any via fxp0 > > allow ip from any to any via lo0 > > allow ip from any to any via fxp0 > > allow ip from 128.175.171.125 to 127.0.0.0/8 > > deny log logamount 100 ip from any to 127.0.0.0/8 > > allow ip from any to any > > deny ip from any to any > > > > > I've not much more luck, really... I'm open to all suggestions though > > =) > > natd is hosed up in some way (I'll bet). What are the > options you are giving to natd when started? NATD is starting out from /etc/rc.conf via the following: natd_enable="YES" natd_interface="fxp0" natd_flags="-f /etc/natd.conf" where fxp0 is my internal NIC. The contents of /etc/natd.conf are: dynamic yes redirect_port tcp 192.168.1.2:51210 51210 redirect_port udp 192.168.1.2:51200 51200 redirect_port udp 192.168.1.2:51201 51201 The most confounding part of it all is that this worked just fine at the beginning of the week while on my old IP... none of those things have changed. I just killed and restarted NATD manually to see if that might burp it, and there was no change. Thanks again!!! --John 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?Pine.SOL.4.31.0106011035460.14041-100000>