From owner-freebsd-questions Mon Jan 22 4:40:19 2001 Delivered-To: freebsd-questions@freebsd.org Received: from rubicon.fernonorden.com (unknown [195.139.149.229]) by hub.freebsd.org (Postfix) with ESMTP id CD9B037B401 for ; Mon, 22 Jan 2001 04:39:57 -0800 (PST) Received: by RUBICON with Internet Mail Service (5.5.2653.19) id ; Mon, 22 Jan 2001 13:35:07 +0100 Message-ID: <25879E6A7E74D411B9370050043B7F3E09F8D6@RUBICON> From: Per Tore Larsen To: "'pgd@telehorizon.com'" , Per Tore Larsen Cc: questions@freebsd.org Subject: RE: NAT within a NAT Date: Mon, 22 Jan 2001 13:35:05 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem is that the when I give on PC3 "ifconfig fxp1" > (my second network card that gives to PC4) I get the > frustrating message "no > carrier". Ok.. now when you say "ifconfig fxp1" is that the hole line or is it more like 1) "ifconfig fxp1 inet 192.168.1.1 netmask 255.255.255.0" or in /etc/rc.conf 2) ifconfig_fxp1="inet 192.168.1.1 netmask 255.255.255.0" Also has the card more than 1 transiver? Depending on the network card this may the problem. Could you try the option 2) for /etc/rc.conf? Do you get the same error message? The 1) may be flawed since I can't test it and it's been a while since I used ifconfig that way. Have you tried a diffrent network card? Same result? The rest of the layout and intentions looks fine. PeTe > -----Original Message----- > From: pgd@telehorizon.com [mailto:pgd@telehorizon.com] > Sent: Monday, January 22, 2001 12:44 PM > To: Per Tore Larsen > Cc: questions@freebsd.org > Subject: RE: NAT within a NAT > > > Here's what i've tried so far: > > I have setup my NAT using the 10.0.0.0 range. > I set up the one of the NATed PCs to be a NAT server as well > (using the > 192.168.0.0 range). I've put a second network card in it and > on this second card > I have connected another PC (the new 192.168.0.0 sub-NAT-network). > > More or less the following situation (where you see a '#', it > is a network > card): > > 10.0.0.0 PC3 192.168.0.0 > +----+ +-PC1 +----+ > |1st | | |2nd | > world<---#NAT #----+--------#NAT #-----PC4 > |serv| | |serv| > +----+ +-PC2 +----+ > > > The problem is that the when I give on PC3 "ifconfig fxp1" > (my second network card that gives to PC4) I get the > frustrating message "no > carrier". > > And of course PC4 gets "no rout to host".. > > Any ideas?? > > thanks, > dimitri & paisios, > > PC. I use no DHCP .. > > > > Quoting Per Tore Larsen : > > > First of all, yes it's possible. > > Setup the second NAT server in the same way you did on > > first NAT server. > > > > The problem that might arise is when a machine on the > > second LAN wants for axess the "world". This can be > > solved for web by using a proxy but dunno how > > ftp/telnet/ssh will behave. > > > > Try it on a test benchfirst and you will get your answer. > > Also depending on you network, you could make FreeBSD answer > > both net 192.168.1 and 192.168.2 using alias in ifconfig. > > (If you use DHCP you might need to have two network adapters > > to physically separate the networks) > > > > PeTe > > > > > -----Original Message----- > > > From: pgd@telehorizon.com [mailto:pgd@telehorizon.com] > > > Sent: Monday, January 22, 2001 11:55 AM > > > To: Freebsd > > > Subject: NAT within a NAT > > > > > > > > > Hello there, > > > I have a LAN which is "hidden" from the world using NAT and i > > > want to setup a > > > sub-NAT-network within my LAN. That is: using another NAT > > > server to hide this > > > subnetwork from the rest of the LAN. > > > > > > Can anyone tell me if this is possible? > > > > > > bye, > > > paisios > > > > > > (I hope I gave a clear picture of this peculiar situation..) > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message