Subject: icmp redirects
To: None <firstname.lastname@example.org>
From: Andrew Brown <email@example.com>
Date: 04/17/2000 17:34:31
i see routes in my routing table like this:
184.108.40.206 220.127.116.11 UGHD 0 46447 - ne0
which looks like
% route -nv get 18.104.22.168
u: inet 22.214.171.124; u: link ; RTM_GET: Report Metrics: len 112, pid: 0, seq 1, errno 0, flags:<UP,GATEWAY,HOST,STATIC>
route to: 126.96.36.199
recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire
0 0 0 2172 219 0 0 0
188.8.131.52 184.108.40.206 ne0:0.40.f6.34.3e.bd 220.127.116.11
which are obviously a result of my machine sending packets to the
default gateway and then being told that a better gateway exists.
the problem is that the expire field is set to 0.
when i changed this, so that the gateway to 18.104.22.168/24 was another
machine, the netbsd box doesn't pick up the change until i actually
physically remove the route. which i guess makes sense, since there's
no way for it to discover the new route, and no way for the route to
but i thought it should time out. i breezed through all the rfcs i
could find on icmp and host requirements and anything else that seemed
related, but i couldn't find anything anywhere that said it should
time out. so i guess it's right that it doesn't.
but why? dynamic routes like that seem like the kind of thing that
should time out, simply because they're called "dynamic routes".
|-----< "CODE WARRIOR" >-----|
firstname.lastname@example.org * "ah! i see you have the internet
email@example.com (Andrew Brown) that goes *ping*!"
firstname.lastname@example.org * "information is power -- share the wealth."