From owner-freebsd-hackers Thu Apr 13 19:53:33 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA06388 for hackers-outgoing; Thu, 13 Apr 1995 19:53:33 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA06381 for ; Thu, 13 Apr 1995 19:53:31 -0700 Received: by brasil.moneng.mei.com (4.1/SMI-4.1) id AA24481; Thu, 13 Apr 95 21:52:59 CDT From: Joe Greco Message-Id: <9504140252.AA24481@brasil.moneng.mei.com> Subject: Routing nightmares. To: hackers@FreeBSD.org Date: Thu, 13 Apr 1995 21:52:58 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2160 Sender: hackers-owner@FreeBSD.org Precedence: bulk Hi all, Does anybody have any networking wisdom to solve this problem? I work for a company with a Class B Internet address. Foolish DEC wisdom convinced folks a long time ago that bridges were their friends and they proceeded to build a nightmarish bridged topology. There are currently many thousands of nodes "out there." The bridges have overflowing tables, the ambient broadcast noise eats about 10% of the Ethernet, and it really, really sucks. We're in the process of subnetting. It was going fine until it was "given" to those same "DEC folks" who have essentially halted all work that was going into the subnetting. And it's been sitting this way for six months. My solution, as usual, is to take matters into my own hands. :-) I have a FreeBSD 2.0R box with dual WD8013's. I've configured one interface on a reasonable subnet, and one interface on the Big net: daneel# ifconfig ed0 ed0: flags=8863 mtu 1500 inet 151.186.28.254 netmask 0xffffff00 broadcast 151.186.28.255 daneel# ifconfig ed1 ed1: flags=8863 mtu 1500 inet 151.186.20.196 netmask 0xffff0000 broadcast 151.186.255.255 daneel# Now, I ran into a Problem. I cannot get gated or routed to propagate any usable routes onto the Big net (i.e. 151.186.28.0->151.186.20.196). The rest of it works (i.e. nodes on 28-net outbound). It seems to be because of routing optimization code SOMEWHERE, which notices that I am trying to propagate a route for "151.186.28.0" onto a net with subnet mask "255.255.0.0", and silently drops this route on outbound RIP packets. If I could just get those routes out there, I'd probably be okay... Okay, so maybe I could proxy ARP all the 28-net nodes on the Big net... except that the proxy ARP'ing happens on BOTH nets, which isn't the desired effect. Anybody got any bright ideas? ... Joe ------------------------------------------------------------------------------- Joe Greco - The Data Capture Fellow (and UNIX/Network Hacker) 414/362-3617 Marquette Electronics, Inc. - Milwaukee, WI jgreco@brasil.moneng.mei.com