Why does a ping to a remote resource only appear after a reload of the interface on Debian?

Question

bash

Already question 6 is probably on this damn storage system lenovo px4-300r =(
This miracle works on debian 5.0. There is a remote network that transparently works through a raised cisco vpn tunnel. my network is 99.x, remote 20.x
root @yellow :/usr /local# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default black.yupshara.0.0.0.0 UG 0 0 0 bond0
172.16.112.0 192.168.99.19 255.255.255.0 UG 0 0 0 bond0
172.16.112.1 192.168.952 .255.255 UGH 0 0 0 bond0
172.16.222.0 192.168.99.19 255.255.255.252 UG 0 0 0 bond0
172.16.222.2 192.168.99.19 255.255.255.255 UGH 0 0 0 0
Bond0 172.16.223.0 192.168.99.19 255.255.255.252 Ug 0 0 0
Bond0 172.16.224.0 192.168.99.19 255.255.255.252 UG 0 0 0
Bond0 172.16.226.0 192.168.99.19 255.255. 255.252 UG 0 0 0 0 Bond0
192.168.20.0 192.168.99.19 255.255.255.0 UG 0 0 0 Bond0
192.168.98.0 192.168.99.19 255.255.255.0 UG 0 0 0 Bond0
192.168.99.0 192.168.99.19 255.255.25.0 UG 0 0 0
Bond0 192.168. 99.0 * 255.255.255.0 U 0 0 0 bond0
172* - tunnels
99.19 is cisco
2nd day customers call every morning that they do not have this resource available on Lenovo. It is solved in this way - I launch ping from the client host in 20th.x to lenovo in 99th.x and restart the interface on lenovo (routes are written in script in if-up.d) and ONLY THEN both ping and connection appear on the storage. what can be problem?
if-up.d/route
#!/bin/bash
route add -net 192.168.20.0 gw 192.168.99.19 netmask 255.255.255.0
route add -net 192.168.98.0 gw 192.168.99.19 netmask 255.255.2595.0
route add -net 192.06 192.168.99.19 netmask
255.255.255.0
ROUTE ADD -NET 172.16.224.0 GW 192.168.99.19 Netmask 255.255.255.252 Route
Add -net 172.16.112.0 GW 192.168.99.19 Netmask 255.255.25.0 Route
Add -net 172.16.226.0 GW 192.168.99.19 Netmask 255.255.255.252 Route
Add -net 192.168 20.5 gw 192.168.99.19 netmask 255.255.255.255
route
add -net 172.16.112.1 gw 192.168.99.19 netmask 255.255.255.255

Answer 1

It is logical to assume that you need to compare ifconfig/route/iptables before and after restarting the interface) It is also possible that there is something unusual in if-down.d

Answer 2

The meaning of this line is not entirely clear.

route add -net 192.168.99.0 gw 192.168.99.19 netmask 255.255.255.0

You already have a network 192.168.99.0/24 hung up on the bond0 interface and accessible through it:

192.168.99.0 * 255.255.255.0 U 0 0 0 bond0

I don’t understand something and is it some kind of Linux crutch? What is the function of this line?
And the second moment. When re-observing the problem, instead of extinguishing / raising the interface, try to start a ping to 192.168.99.19 from the storage system. There is a suspicion of fluctuations in the ARP table on the router.