Sergey Matveychuk wrote:
I've got some problem with route entries that was created after ICMP
redirect messages. They are never expired.
Our default gateway (it's a HP switch) send ICMP redirect messages if it
see a short path to destination. It's makes it not so overloaded. But
pathes
Uwe Doering wrote:
This has been fixed in CVS in MAIN (rev. 1.52) and MFC'ed to RELENG_4
(rev. 1.37.2.5) and RELENG_5 (rev. 1.51.4.2) a couple of weeks ago:
Oh, thank you!
And thanks to [EMAIL PROTECTED]
--
Sem.
___
freebsd-questions@freebsd.org mailing
I've got some problem with route entries that was created after ICMP
redirect messages. They are never expired.
Our default gateway (it's a HP switch) send ICMP redirect messages if it
see a short path to destination. It's makes it not so overloaded. But
pathes sometime changed. There is no
Sergey Matveychuk wrote:
I've got some problem with route entries that was created after ICMP
redirect messages. They are never expired.
Our default gateway (it's a HP switch) send ICMP redirect messages if it
see a short path to destination. It's makes it not so overloaded. But
pathes
At Sun, 10 Apr 2005 15:14:59 +0400,
Sergey Matveychuk wrote:
I've got some problem with route entries that was created after ICMP
redirect messages. They are never expired.
Our default gateway (it's a HP switch) send ICMP redirect messages if it
see a short path to destination. It's
[EMAIL PROTECTED] wrote:
If you want to handle this in a more clever way than a cron job you
could write a small daemon which reads routing messages and does the
right thing for whatever your situation is.
I've explore a code and found I can do quite easy addition for dynamic
routes - fill an
