Bug #1172
closedroute(8) bugs
0%
Description
$ sudo route add -net 172.16.10.1/32 192.168.1.1
add net 172.16.10.1: gateway 192.168.1.1
$ sudo route add -net 172.16.11.1/255.255.255.255 192.168.1.2
add net 172.16.11.1: gateway 192.168.1.2
$ sudo route add -net 172.16.12.1 192.168.1.3 255.255.255.255
add net 172.16.12.1: gateway 192.168.1.3
$ netstat -rn | grep 172.16
172.16.0.0/32      192.168.1.3        UGSc        0        0   ath0
172.16.10.1/32     192.168.1.1        UGSc        0        0   ath0
172.16.11.0/31     192.168.1.2        UGSc        0        0   ath0
$
It's not funny actually :).
      
      Updated by hasso almost 17 years ago
      
    
    Add to it with "default only" setup:
$ sudo route add -net 0.0.0.0/1 192.168.1.1
route: writing to routing socket: File exists
add net 0.0.0.0: gateway 192.168.1.129: File exists
$
      
      Updated by hasso almost 17 years ago
      
    
    Should be fixed by c5502c43e9daddebcfe75a0b81b28c6dfa3e2d07 (the cases in 
msg5606) and a80e869f444616b15f5685b343928be09b3b43bc (the case in msg5608). 
Note that sudo "route add -net 172.16.11.1/255.255.255.255 192.168.1.2" 
doesn't work anyway.