*BSD News Article 65865


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!vic.news.telstra.net!act.news.telstra.net!psgrain!newsfeed.internetmci.com!iol!tank.news.pipex.net!pipex!news.mathworks.com!fu-berlin.de!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: routing problem ...
Date: 12 Apr 1996 23:56:33 GMT
Organization: Private BSD site, Dresden
Lines: 75
Message-ID: <4kmqjh$f8c@uriah.heep.sax.de>
References: <4j98t3$3hb@helios.cto.us.edu.pl> <4k1goi$krb@uriah.heep.sax.de> <4kghmr$1e@helios.cto.us.edu.pl>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.3

swierzy@gate.math2.us.edu.pl (Witek Swierzy) writes:

>                 -----       -----                       ----
>                |DOS  |     |DOS  |                     | ka9
>                 -----       -----                       ----
> 155.158.21.11 ->  |  . . . .  |<-155.158.21.2               
> --------------------------------------\  /------------------
>                                       |  |                  
>                        155.158.21.1 ->|  | <-  155.158.3.13 
>                                  --------------             
>        gate.math2.us.edu.pl ->  |    FBSD      |            
>                                 |   2.1.0-R    |            
>                                  --------------             
>                                        /\                   
>                 -----       -----      ||                   
>                |DOS  |     |DOS  |   they sees themselves   
>                 -----       -----      ||                   
> 155.158.20.11 ->  |  . . . .  |<-155.158.20.2               
> --------------------------------------\\//------------------
>                                       |  |                  
>                        155.158.20.1 ->|  | <-  155.158.3.12 
>                                  --------------             
>                                 |    FBSD      |            
>         gate.math1.us.edu.pl -> |   2.0.5      |            
>                                  --------------             

Sorry for duplicating so much.  Anyway:

> Routing tables                                              
> Internet:                                                   
> Destination      Gateway            Flags     Refs     Use     Netif Expire
> default          155.158.3.1        UGSc       10        3       ed0

> 155.158.3        link#1             UC          1        0 
> 155.158.3.1      0:0:c:15:57:93     UHLW       46        0       ed0   1038
> 155.158.3.3      0:0:c0:c6:6a:65    UHLW        1        0       ed0   1159
> 155.158.3.5      0:0:c0:8b:64:62    UHLW        1        0       ed0    739
> 155.158.3.11     link#1             UHLW        3        0 
> 155.158.3.12     link#1             UHLW        1       81 
                   ^^^^^^ (1 *)
> 155.158.3.13     127.0.0.1          UGHS        0      774       lo0
..
> 155.158.20       155.158.3.12       UGc         0       94       ed0
> 155.158.21       link#3             UC          1        0 
> 155.158.21.1     0:60:8c:b3:bb:b2   UHLW        0        1       lo0
> 155.158.21.10    link#3             UHLW        1       98 

Something's really weird here.

(1 *) -- two of the hosts on the .3 subnet have been attempted to be
	resolved via ARP, but failed, one of them is the other FreeBSD
	machine

     -- i can't seem to find any mention of a second ethernet interface
	in this routing table; are the secondary networks, however,
	the .21 subnet is mentioned as link#3 -- what's the interface
	for link#3 ?

The routing table seems to be somewhat confusing.  Did you try to kill
routed, and enter all routing table entries manually, just for
testing?

If this works, i'd suggest you getting GateD, and constructing a gated
configuration that avoids to import `bogus' routing entries.  I can't
figure the reason exactly from the above, but it looks like your
routing table somehow gets confused by some imported routing
information.  (I assume your Cisco announces the routing tables via
RIP.)

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)