From owner-freebsd-questions Thu Jun 3 22:56:58 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 2DB6715156 for ; Thu, 3 Jun 1999 22:56:54 -0700 (PDT) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id BAA02090; Fri, 4 Jun 1999 01:57:12 -0400 (EDT) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199906040557.BAA02090@cc942873-a.ewndsr1.nj.home.com> Subject: Re: 2 ethernet cards (fwd) In-Reply-To: from Brad Tucker at "Jun 3, 99 10:22:11 pm" To: zvi@zvi.t-networking.com (Brad Tucker) Date: Fri, 4 Jun 1999 01:57:12 -0400 (EDT) Cc: cjclark@home.com, freebsd-questions@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Tucker wrote, > OK. the cisco router is 206.117.19.1. The _interface_ on your side of the router is 206.117.19.1. Interfaces have IP addresses, not hosts. Associating a machine with an IP will cause confusion once there are multiple interfaces on one. > It takes a class c and subnets it > into 2 subnets. this leaves me with 0-127 and 128-255. I get half the > class c. my half is 0-127. now strait from the router I plug into the > freebsdbox, into ed0 wich is 206.117.19.2. OK, got it. > The idea i had was to put two > ether net cards itno the freebsd box and make it a router. So i added the > appropriate ifconfig entries, and added another ethernet card ed1. Out of > ed1 goes to a hub, and out from the hub go all the macintoshes. This will work if configured correctly. > zvis ethernet card is ed0. You just said it had two. > What does NATd do and why would I need that. I You can tell NATd to listen on the ed0 interface and when it hears the router, 206.117.19.1, arp'ing for machines on 206.117.19.64/26, it will answer and it will forward the packets appropriately. But this is not the easiest way if you have access to the router's config. > tried routed, and that doesnt seem to work. It depends if the router will listen to ICMP directs from the FreeBSD box (and of course, the FreeBSD box needs to be configured correctly). > Is what im trying even possable. Sure is[0]. > The reason im doing this is to isolate the apple talk network running with > netaalk. Bet you did not think it would be this much work? :) You have the FreeBSD box done right from what I saw in your rc.conf. Those ifconfigs should set up the routing table correctly. Now for the router, this is what I think the easiest configuration is. All commands are how you would tell a FreeBSD system to do this. I don't have my Cisco books at home and haven't fiddled enough to know the syntax by heart. # ifconfig 206.117.19.1 netmask 0xffffffc0 # route add -net 206.117.19.64 -netmask 0xffffffc0 206.117.19.2 Now that I think of it, the netmask there is not needed, but the way to tell the Cisco will be different anyway. Hope this helps. [0] We used to have something more elaborate at the office... well, we still do actually. We have a whole C class net, but for hardware reasons (BNC cable) we had to break it up into pieces. Specifically, we have a bunch of 27 bit (32 address, 30 usable) nets. We too have a Cisco router. The router has the '1' address of our net[1] and talks locally to the lower 32 machines. All of the other 32 host nets are specified as static routes in the Cisco's routing table. All of the other subnets go to one address (30) where a NetWare box (yuck, it predates me at this job) routes 'em all appropriately. And it does work fine... well, when sunspots, moon phases, or tides are not causing the NetWare box to flake out. [1] Actually, we have two adjacent C class nets at work. The other C class is comes over the same Cisco on the same interface (the interface is aliased to the '1' address on both nets), and the entire net is on one wire (it goes to some hubs and a Cisco switch, actually). Right now, this whole C class and the lower 32 of the other C class are on the same wire really... makes for fun addressing. ;) Oh, and I suck up old machines no one wants (486s, 586s) and run a 192.168.0 net in my office behind a NAT box. So, there is another net too. The fun never ends. >:) -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message