Subject: routing table entries after estab. a ppp connection
To: None <current-users@NetBSD.ORG>
From: Markus Kilbinger <kilbi@rad.rwth-aachen.de>
List: current-users
Date: 04/14/1997 16:10:35
Hi!
I noticed the following strange behaviour of a -current kernel and
binary set (about April 11th) on a pentium machine:
First I have a routing table like (netstat -rn) for our local net:
Routing tables
Internet:
Destination Gateway Flags Refs Use Mtu Interface
default 192.11.100.1 UGS 1 124852 - ed0
127.0.0.1 127.0.0.1 UH 26 13937 - lo0
192.11.100 link#1 UC 0 0 - ed0
192.11.100.1 aa:00:04:00:33:cc UHL 10 379499 - ed0
192.11.100.129 00:00:1b:4b:0c:41 UHL 3 17 - ed0
192.11.100.143 00:00:c0:17:1e:aa UHL 7 1472 - lo0
192.11.100.153 00:00:c0:79:5d:c4 UHL 1 483 - ed0
192.11.100.154 00:00:c0:e2:75:b1 UHL 1 5925 - ed0
192.11.100.155 00:00:c0:f1:5e:c8 UHL 0 534 - ed0
192.11.100.156 00:00:c0:a9:c9:d3 UHL 2 38672 - ed0
192.11.100.157 00:40:95:e1:a5:3f UHL 0 4 - ed0
192.11.100.161 00:05:02:64:12:d5 UHL 2 0 - ed0
192.11.100.255 link#1 UHL 1 3698 - ed0
After establishing a PPP connection (192.11.100.143 <-->
192.11.100.124, including PPP proxyarp option) the
routing table looks like:
Routing tables
Internet:
Destination Gateway Flags Refs Use Mtu Interface
default 192.11.100.1 UGS 1 124852 - ed0
127.0.0.1 127.0.0.1 UH 26 13937 - lo0
192.11.100 link#1 UC 0 0 - ed0
192.11.100.1 aa:00:04:00:33:cc UHL 10 379499 - ed0
192.11.100.124 192.11.100.143 UGS 1 0 - ppp0
192.11.100.124 ................ UGS 1 0 - ppp0
192.11.100.129 00:00:1b:4b:0c:41 UHL 3 17 - ed0
192.11.100.143 00:00:c0:17:1e:aa UHL 7 1472 - lo0
192.11.100.153 00:00:c0:79:5d:c4 UHL 1 483 - ed0
192.11.100.154 00:00:c0:e2:75:b1 UHL 1 5925 - ed0
192.11.100.155 00:00:c0:f1:5e:c8 UHL 0 534 - ed0
192.11.100.156 00:00:c0:a9:c9:d3 UHL 2 38672 - ed0
192.11.100.157 00:40:95:e1:a5:3f UHL 0 4 - ed0
192.11.100.161 00:05:02:64:12:d5 UHL 2 0 - ed0
192.11.100.255 link#1 UHL 1 3698 - ed0
Looks good and works: The PPP connected machine is reachable in both
directions.
The interesting thing happens if I try to add another route under this
circumstance, no matter if by hand ('route add -net ...') or via
'routed':
E. g.: `route add -net 192.168.2 192.11.100.161' yields following
routing table:
Routing tables
Internet:
Destination Gateway Flags Refs Use Mtu Interface
default 192.11.100.1 UGS 1 124851 - ed0
127.0.0.1 127.0.0.1 UH 26 13929 - lo0
192.11.100 link#1 UC 0 0 - ed0
192.11.100.1 aa:00:04:00:33:cc UHL 10 379177 - ed0
192.11.100.124 192.11.100.143 UGS 1 0 - ppp0
192.11.100.124 ................ UGS 1 0 - ppp0
192.11.100.129 00:00:1b:4b:0c:41 UHL 3 17 - ed0
192.11.100.143 00:00:c0:17:1e:aa UHL 7 1456 - lo0
192.11.100.153 00:00:c0:79:5d:c4 UHL 1 483 - ed0
192.11.100.154 00:00:c0:e2:75:b1 UHL 1 5925 - ed0
192.11.100.155 00:00:c0:f1:5e:c8 UHL 0 534 - ed0
192.11.100.156 00:00:c0:a9:c9:d3 UHL 2 38661 - ed0
192.11.100.157 00:40:95:e1:a5:3f UHL 0 4 - ed0
192.11.100.161 00:05:02:64:12:d5 UHL 1 0 - ed0
192.11.100.255 link#1 UHL 1 3697 - ed0
192.168.2 192.11.100.161 UGS 0 24 - ppp0
^^^^
Why is this route to 192.168.2 connected to device 'ppp0'? It doesn't
work, of course ;-)...
Any idea on that?
Markus.