Skip site navigation (1)Skip section navigation (2)
Date:               Tue, 28 Nov 1995 15:00:44 +0000
From:      "Andrew Webster" <awebster@dataradio.com>
To:        freebsd-questions@freebsd.org
Cc:        "Garrett A. Wollman"wollman@lcs.mit.edu
Subject:         Routing Wierdness in FreeBSD 2.1.0 RELEASE
Message-ID:  <199511282000.PAA00232@vhf.dataradio.com>

next in thread | raw e-mail | index | archive | help
Strange routing problem...here are the symptoms:

Internet gateway box with ep0 network card configured as follows:
ifconfig ep0 inet 198.168.41.2 netmask 255.255.255.0
ifconfig ep0 alias 198.168.36.2 netmask 255.255.255.0
ifconfig ep0 alias 198.168.41.55 netmask 255.255.255.255
ifconfig ep0 alias 198.168.36.55 netmask 255.255.255.255

The 198.168.41 segment is visible to the world, the 198.168.36 
segment is only visible internally.

Interface tun0 is running iijppp on a ppp link to our provider.

When I attempt to traceroute to 198.168.54.8 (ns.rezonet.net) a host 
outside our domain.  One of two things will happend:

1. If routed -q is running, I get this result:
   55 [vhf:/home/andreww] : traceroute 198.168.54.8
   traceroute to 198.168.54.8 (198.168.54.8), 30 hops max, 40 byte packets
    1  fs (198.168.36.99)  2.483 ms !H  1.111 ms !H  0.964 ms !H

2. If routed is NOT running, I get this result:
   52 [vhf:/home/andreww] : traceroute ns.rezonet.net
   traceroute to ns.rezonet.net (198.168.54.8), 30 hops max, 40 byte packets
    1  S496.InterLink.NET (198.168.61.61)  226.432 ms  191.383 ms  198.247 ms
    2  MIX.NET (198.168.73.2)  197.366 ms  205.749 ms  168.272 ms
    3  ns.RezoNet.NET (198.168.54.8)  197.555 ms  205.701 ms  198.371 ms   

In the first case, netstat -rna does not have any entries for the 
198.168.54 network so however the routing information is changing it 
is happening quietly.  The default route is:
default          198.168.61.61      UGc        20        3      tun0  
          
In the second case, netstat -rna has this line in it:
198.168.54.8     198.168.61.61      UGHW        2       69      tun0  
     
I've put a protocol tracer on both the ppp link and our internal 
networks and there are no RIP packets with any information that could 
cause this erratic behaviour.

Anyone have any ideas what this could be all about?

-----------------------------------------------------------------------
  Andrew Webster   Network Manager / Special Projects
  Dataradio Inc.   200-5500 Royalmount Ave.      TEL: +1 514 737 0020
  Town of Mount Royal, QC, CANADA  H4P 1H7       FAX: +1 514 737 7883
  http://www.dataradio.com              Email: awebster@dataradio.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511282000.PAA00232>