--- Reply created Sunday, 30 September 2001, 06:56:46 --- James,
Thanks for the info... 1. This is the epiphany I recently had on the subject; works much better this way. 2. That is likely the cause of behavior I am noticing; if I'm lucky, I will be able to try a separate hub before I cable the T1 router directly to the NIC in the linux box. 3. This is good news; hopefully, I will be that "lucky". Thanks again, Clinton E. Troutman Sr. Support Technician AutoRealty Products, Inc. [EMAIL PROTECTED] http://www.autorealty.com/ ------- Begin Original Message -------- On Friday, 28 September 2001, 06:59, you wrote: JS> I've noticed simular problems when building a firewall and testing it JS> before going live. What I've noticed is that. JS> 1. I need to create 2 different subnets. Since my in house net is JS> 192.168.187.x I've use 10.0.1.x for the second. JS> 2. When both nics are connected to the same hub eth0 answers for both JS> nics no matter what I do. So I have to use a before and after hub. (one JS> hub for the 192 network and a second up for the 10 network.) JS> 3. Most of the time these problems disapear when it goes live without any JS> major changes other that using real IP's JS> James JS> On Tue, 25 Sep 2001 16:36:17 -0400 (EDT) JS> Jason Van Patten <[EMAIL PROTECTED]> wrote: >> At Tue Sep 25 16:06:38 2001, AutoRealty Technical Support wrote: >> > Currently, the mask for both is 255.255.255.254 >> > I have attempted 255.255.255.0 255.255.255.255 255.255.255.254 >> > without differing results. Always using the same subnet on both NIC's. >> >> My bet is, given your arp table, that you want a /24 subnet mask, ie, >> 255.255.255.0. So try this and tell me what happens: >> >> # ifconfig eth0 90.0.0.89 netmask 255.255.255.0 broadcast 90.0.0.255 >> # ifconfig eth1 90.0.0.88 netmask 255.255.255.0 broadcast 90.0.0.255 >> >> > At this time, the machine simply serves HTTP and FTP. The ultimate >> > goal is for this machine to serve as a firewall; receiving packets >> > from the router through eth0 and passing (some) packets to the LAN >> > through eth1. I have made no progress on the firewall setup as I can >> > not solve this problem (separate IP's on each NIC). >> >> Well, having both interfaces on the same /24 isn't going to get you what >> you're after. The idea of a firewall/router is to have one interface on >> a >> private subnet (say, 10.0.0.0/24) and another on a public subnet >> (your 90.0.0.0/24 for instance.) Then you "route" between them. >> >> jas >> -- >> Jason Van Patten >> AOL IM: Jason VP >> >> >> ------- End Original Message --------
BEGIN:VCARD VERSION:2.1 N:Support;AutoRealty;Technical FN:AutoRealty Technical Support EMAIL;PREF;INTERNET:[EMAIL PROTECTED] ORG:AutoRealty Products, Inc.;Research & Development TITLE:Senior Support Technician TEL;WORK;VOICE:817.589.1566 TEL;WORK;FAX:817.284.9877 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;1060 West Pipeline Road=0D=0ASuit= e 100;Hurst;Texas;76053.4732;USA LABEL;WORK;ENCODING=QUOTED-PRINTABLE:1060 West Pipeline Road=0D=0ASuit= e 100=0D=0AHurst=0D=0ATexas76053.4732=0D=0AUSA ADR;HOME:;;;Fort Worth;Texas;;USA LABEL;HOME;ENCODING=QUOTED-PRINTABLE:Fort Worth=0D=0ATexas=0D=0AUSA URL;WORK:http://www.autorealty.com/ REV:18991230T060000Z END:VCARD
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
