From owner-freebsd-hackers Tue Dec 1 18:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24247 for freebsd-hackers-outgoing; Tue, 1 Dec 1998 18:46:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24242 for ; Tue, 1 Dec 1998 18:46:06 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id VAA06152; Tue, 1 Dec 1998 21:45:31 -0500 (EST) Date: Tue, 1 Dec 1998 21:45:31 -0500 (EST) From: Daniel Eischen Message-Id: <199812020245.VAA06152@pcnet1.pcnet.com> To: dillon@apollo.backplane.com, nate@mt.sri.com Subject: Re: TCP bug Cc: hackers@FreeBSD.ORG, luigi@labinfo.iet.unipi.it Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In trying to track down why some boxes in my network can't connect to > certain WWW hosts, I determined that my FreeBSD is not routing the > packets for some reason. It's receiving them, and the firewall code > *thinks* it's passing them on, but tcpdump doesn't see these packets go > out on the wire. I've got a router with 4 interfaces, both public and private, ipfw and NATD, 2.2.7-stable and no problems. I did have similar problems as you're describing, and it turned out that some of the systems on one network didn't have the correct netmasks set. They were being directed to the router, but the netmask was wrong and the router didn't know what to do with them. For instance, from network A I tried to ping a system on network B. Using tcpdump I could see the packets go through the router from the network A interface, out the network B interface, and then see the replies from the network B interface, and there they would stop without going back to network A. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message