From owner-freebsd-questions Tue Nov 28 17:42:56 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp2.cybersurf.net (smtp2.cybersurf.net [209.197.145.112]) by hub.freebsd.org (Postfix) with ESMTP id 1B72237B400 for ; Tue, 28 Nov 2000 17:42:54 -0800 (PST) Received: from [209.197.159.38] ([209.197.159.38]) by smtp2.cybersurf.net (Netscape Messaging Server 4.15) with SMTP id G4RJFG00.GME for ; Tue, 28 Nov 2000 18:42:52 -0700 From: "Duke Normandin" <01031149@3web.net> To: freebsd-questions@freebsd.org Date: Tue, 28 Nov 2000 14:28:11 mst7mst MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: win95 "route" && FBSD box Reply-To: 01031149@3web.net X-mailer: Pegasus Mail v3.50 Message-Id: <20001129014254.1B72237B400@hub.freebsd.org> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Nov 00 at 9:07, Igor' Robul' wrote: >On Mon, Nov 27, 2000 at 09:43:01AM +0000, Duke Normandin wrote: >> So.....the output on my win95 box is: >This is "host only". I think. It can't forward packets between network >interfaces. I think, you can have two netcards in Win95 box. You can >even "be in two networks" as client workstation, but PC on 1st net >will not "see" PC on 2nd net. >With Unix or NT you can: > PC_with_Unix_or_NT >PC1--PC2<------->NC1 NC2<--------------->PC3----PC4 >you can use "ping" on PC1: ping PC4 and you'll get response (if you >have not setup firewall on "PC_with_Unix_or_NT") >But, in this configuration: > Windows_95_PC >PC1---PC2_with_UNIX<--->NC1 NC2<----->PC3-------PC4 > >you can use ping on Windows_95_PC: "ping PC1" or "ping PC4" >but on >PC2_with_UNIX or PC1 you can't: ping PC4 So in a nutshell, win95 can only "route" packets originating from itself. Bummer.... I was grasping at "Win-blown" straws I guess ;,) Thanks... -duke Calgary,Alberta, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message