24 Apr
2017
24 Apr
'17
12:32 p.m.
Because of concern that the rip sender might be
sending
the pseudo-RIP packets to gateways faster than they can
receive them, I have changed the sending order.
...
This has the effect of inserting a few milliseconds
delay
between consecutive packets being sent to any one gateway,
which should give the receiving process more time to handle
the transmission.
My main concern was not the receiving process, but the routers
in front of the gateway system that (in my case) appeared to
drop the tail end of the transmission, probably because of
rate limiting or a queue overflow.
Now, I get the 26 packets in about 150ms, which should solve
that problem for anything but the slowest connections. Thanks!
Unfortunately there is still no 44.0.0.1 route. I did a trace
and confirm that the last packet received has the lowest addresses,
but it ends with:
IP Address: 44.2.7.0, Metric: 1
Address Family: IP (2)
Route Tag: 4
IP Address: 44.2.7.0 (44.2.7.0)
Netmask: 255.255.255.252 (255.255.255.252)
Next Hop: 73.185.12.233 (73.185.12.233)
Metric: 1
IP Address: 44.2.2.0, Metric: 1
Address Family: IP (2)
Route Tag: 4
IP Address: 44.2.2.0 (44.2.2.0)
Netmask: 255.255.255.0 (255.255.255.0)
Next Hop: 24.52.189.1 (24.52.189.1)
Metric: 1
Still some mystery somewhere :-)
Rob