Date: Fri, 28 Jul 2006 22:00:03 +0200 From: Stefan Bethke <stb@lassitu.de> To: Adam Egan <adam.egan@gmail.com> Cc: freebsd-chat@freebsd.org Subject: Re: ipfw and natd routing problems Message-ID: <007D57CF-0D72-4579-8FC8-7E66C54ACEFD@lassitu.de> In-Reply-To: <28745bbf0607281005t77d676a5ge7e5e8fcf1ea280e@mail.gmail.com> References: <28745bbf0607270947i6d71369fg5c1403b2d6e36219@mail.gmail.com> <980FE9AA-8300-4019-BAEE-7B7C0708526D@lassitu.de> <28745bbf0607281005t77d676a5ge7e5e8fcf1ea280e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 28.07.2006 um 19:05 schrieb Adam Egan: >> natd needs to work on both incoming and ooutgoing connections. >> Dropping the "in" keyword should do the trick. > > Hi Stefan, as I said in my original email, outgoing connections work > fine, it is the incoming connections which natd is supposed to foward > to other computers which doesn't work. Sorry, I missed that. If you can post tcpdump traces from both the inside and the outside interface while trying to connect to port 80, there might be a chance to spot the problem. The natd config seems to be fine. Stefan -- Stefan Bethke <stb@lassitu.de> Fon +49 170 346 0140
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007D57CF-0D72-4579-8FC8-7E66C54ACEFD>