From owner-freebsd-questions Sat Jan 11 14:53:52 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F9CF37B401 for ; Sat, 11 Jan 2003 14:53:49 -0800 (PST) Received: from shockwave.systems.pipex.net (shockwave.systems.pipex.net [62.241.160.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 925E543ED8 for ; Sat, 11 Jan 2003 14:53:48 -0800 (PST) (envelope-from stacey@vickiandstacey.com) Received: from [192.168.1.8] (81-86-129-77.dsl.pipex.com [81.86.129.77]) by shockwave.systems.pipex.net (Postfix) with ESMTP id C40111600198A; Sat, 11 Jan 2003 22:53:45 +0000 (GMT) Subject: Re: Problems w NIC From: Stacey Roberts Reply-To: stacey@vickiandstacey.com To: Nikolaj Farrell Cc: FreeBSD Questions In-Reply-To: <002b01c2b9c3$56722e40$0100a8c0@athlon> References: <001701c2b987$9fdf72e0$0100a8c0@athlon> <1042300066.51041.227.camel@localhost> <002a01c2b989$f2099e90$1200a8c0@gsicomp.on.ca> <000b01c2b98a$df9981c0$0100a8c0@athlon> <1042301568.51041.233.camel@localhost> <001201c2b98e$063311e0$0100a8c0@athlon> <1042303096.51041.237.camel@localhost> <000301c2b993$55e70610$0100a8c0@athlon> <20030111171152.GH25529@sub21-156.member.dsl-only.net> <001b01c2b995$0dbf6d30$0100a8c0@athlon> <1042305860.51041.240.camel@localhost> <001801c2b999$95567000$0100a8c0@athlon> <1042310110.51041.250.camel@localhost> <002b01c2b9c3$56722e40$0100a8c0@athlon> Content-Type: text/plain Organization: Message-Id: <1042325630.51041.257.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 11 Jan 2003 22:53:50 +0000 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG HI, On Sat, 2003-01-11 at 22:46, Nikolaj Farrell wrote: > Hello again everyone, I will try to clearify below; > > > Thanks for getting back with the funky art:-) > > > > Question on the network though, you mentioned: > > > > "but the idea is that all machines except .0.2 have one NIC connected to > > the hub" > More appropriate description would be "All machines except 192.168.0.2 have > one NIC. 192.168.0.2 has two NICs, where one NIC is connected to hub and the > other to DSL modem." I am sorry if this caused confusion. > > > > > So according to your diagram, the FreeBSD box has two nics - 1 to > > Internet (?) and the other connected to ...., what? > > > > Which interface on the FreeBSD box has the IP address of 192.168.0.2? If > > of all the machines, ".0.2" connect to the hub, how do the others then > > see the FreeBSD box? > > Actually all my computers are FreeBSD. The gateway with two NICs has one NIC > connected to the hub. Me writing "0.2" was simple laziness and meant > 192.168.0.2. I was not trying to indicate an ip-range or anything similar. > > > > > > > You also mention: > > > > "0.2 has two NICs and is gateway/firewall" > > > > What packet filter do you have? For whichever you are using, please post > > the fw logs. > > > 192.168.0.2 is running natd/ipfw. The only thing forwarded aimed > specifically at one machine is pop and smtp which both redirect to my > mailserver. Otherwise the following rule is all I have; (apart from > firewalling on external NIC and there are no rules for the internal network) > > 00100 divert 8668 ip from any to any via xl0 > > These rules work perfectly for all other fbsd-boxes on my LAN. > > > Looking forward to hearing more on the information I asked for here. > > > > Regards, > > > > Stacey > > > > I hope this makes things a little more clear. I can also add that I, in all > frustration, did a complete reinstall. I repartioned/sliced the disk and > then installed again from cd-rom. (The installer wouldn't allow ftp, since > it couldn't find any servers responding... ;) ). This did, naturally, not > help at all. Thanks for clarifying things. I think I understand now. Here's what I (and others as well) believe is the root of the problem - its ipfw. By default its got a rule that reads DENY EVERYTHING. If you run "ipfw show" then it'll be right at the bottom. Unless you expressly allow traffic with ipfw statements, then you'll get packets not being forwarded onto respective destinations. Also if you've not actually configured the rule-set (E.G. for logging) then that explains why nothing appears in the logs. You mentioned that you've not configured any rules for the internal network, so you've answered you own questions here. Post the output from the above ipfw cmd, and I'm sure there'll be lots of assistance for you. Regards, Stacey > > regards > /Nikolaj -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message