[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Routing Problems (link#2 ??)
From:       Mark Mayo <mark () quickweb ! com>
Date:       1996-08-01 0:18:28
[Download RAW message or body]


I have a problem... I'm on a network with a netmask of 255.255.255.240,
and my machine is 199.212.134.8 - so it's in the 'base' logical network.
Any machine on the same logical net as me (.8-.15) can get to me fine
(arp takes care of it..), the weird thing is that the portmaster dial-in
servers can't get to me (they're on a different subnet, but the same
physical net).

The thing that puzzles me are the result from netstat -nr:

default          199.212.134.5      UGc        12    46314       ep0
127              127.0.0.1          URc         0        0       lo0
127.0.0.1        127.0.0.1          UH          6     1025       lo0
199.212.134      link#2             UC          0        0
199.212.134      link#2             UC          0        0
199.212.134.1    0:0:c0:eb:9b:8e    UHLW        3     7912       ep0
284
199.212.134.3    0:0:a2:6:90:e8     UHLS        0       18       ep0
199.212.134.4    0:0:c0:0:2e:87     UHLW        3    25728       ep0
678
199.212.134.5    0:0:93:b8:34:98    UHLW       11      232       ep0
1178
199.212.134.6    0:c0:5:1:4a:4b     UHLW        0        0       ep0
1112
199.212.134.8    0:20:af:15:38:df   UHLW        3   133118       lo0
199.212.134.10   0:c0:5:1:3a:46     UHLW        0        4       ep0
686
199.212.134.11   0:c0:5:1:19:ed     UHLW        0        3       ep0
887
199.212.134.12   0:c0:5:1:1d:44     UHLW        0        2       ep0
1157
199.212.134.13   0:c0:5:1:28:3c     UHLW        0        2       ep0
1159
199.212.134.14   0:40:ff:0:2a:8     UHLW        0        2       ep0
1194
199.212.134.15   link#2             UHLW        1    11842
199.212.134.80   199.212.134.4      UGc         1    71278       ep0
206.248.60       link#2             UC          0        0
206.248.60.11    0:0:c0:eb:9b:8e    UHLW        0        0       ep0
594
206.248.60.80    0:20:af:15:38:df   UHLW        0       12       lo0
206.248.60.81    0:20:af:15:38:df   UHLW        0       14       lo0
224              link#2             UCS         0        0


What the hell are the link#2's????????????? Why are the 'network'
addresses (the .15's) going to link#2, as well as 199.212.134 (the entire
class C) going through there..

I can't seem to get rid of them... I can kill gated, route flush, and when
gated fires up again, they appear...

Rather annoying.


In case it's useful, here are the results of netstat -an and netstat -in:

mark:{58}/home/mark % netstat -in
Name  Mtu   Network     Address            Ipkts Ierrs    Opkts Oerrs
Coll
lp0*  1500  <Link>                             0     0        0     0
0
ep0   1500  <Link>00.20.af.15.38.df      7651375    37  2570921    81
0
ep0   1500  199.212.134 199.212.134.8    7651375    37  2570921    81
0
ep0   1500  199.212.134 199.212.134.81   7651375    37  2570921    81
0
ep0   1500  199.212.134 199.212.134.87   7651375    37  2570921    81
0
ep0   1500  199.212.134 199.212.134.88   7651375    37  2570921    81
0
ep0   1500  199.212.134 199.212.134.90   7651375    37  2570921    81
0
ep0   1500  199.212.134 199.212.134.91   7651375    37  2570921    81
0
ep0   1500  199.212.134 199.212.134.84   7651375    37  2570921    81
0
ep0   1500  206.248.60  206.248.60.81    7651375    37  2570921    81
0
ep0   1500  206.248.60  206.248.60.82    7651375    37  2570921    81
0
ep0   1500  206.248.60  206.248.60.83    7651375    37  2570921    81
0
ep0   1500  206.248.60  206.248.60.84    7651375    37  2570921    81
0
ep0   1500  206.248.60  206.248.60.85    7651375    37  2570921    81
0
ep0   1500  206.248.60  206.248.60.86    7651375    37  2570921    81
0
ep0   1500  206.248.60  206.248.60.87    7651375    37  2570921    81
0
ep0   1500  206.248.60  206.248.60.88    7651375    37  2570921    81
0
ep0   1500  206.248.60  206.248.60.89    7651375    37  2570921    81
0
lo0   16384 <Link>                        138300     0   138300     0
0
lo0   16384 127         127.0.0.1         138300     0   138300     0
0


forget the netstat -a.... too much crap..

Here's a ripquery though:
scooter# ripquery -r scooter
44 bytes from scooter.quickweb.com(199.212.134.8) to 199.212.134.8 version
2:
         199.212.134.80/255.255.255.240  router 199.212.134.4    metric  1
tag
0000
                0.0.0.0/0.0.0.0          router 199.212.134.5    metric  1
tag
0000


So I'm not broadcasting anything that would cause hell to break loose..

The other odd thing is that traffic coming in from the internet through
199.212.134.5 (a proteon router on a T1) has no problems getting to the
box - it's just things that are (here goes) on the same physical network
but on a different logical net.....

I'm mostly curious about the link#2 thing, if I could get rid of that, I
think I can boss around the routing tables enough to convince it where the
class C should be routed through :-)

TIA,
-mark

-------------------------------------------
| Mark Mayo		mark@quickweb.com |
| C-Soft  	        www.quickweb.com  |
-------------------------------------------
"To iterate is human, to recurse divine."
		- L. Peter Deutsch

[prev in list] [next in list] [prev in thread] [next in thread]