NetC.
HostFoo has a default route (only) to GW2 and can ping a host on NetC
because it gets an ICMP redirect from GW2 (FreeBSD) to GW3. However, if
HostFoo pings a a host on NetA it DOES NOT get a ICMP redirect from GW2.
Looking through the kernel code, which is where I need help, it seems
routes
On 25 mei 2005, at 17:55, Charles Swiger wrote:
On May 25, 2005, at 11:46 AM, FreeBSD questions mailing list wrote:
Lately i get a lot (really a lot) of these errors:
icmp redirect from 127.0.0.1: => 127.0.0.1
I have no idea where they come from and better how to get rid of
them...
On May 25, 2005, at 11:46 AM, FreeBSD questions mailing list wrote:
Lately i get a lot (really a lot) of these errors:
icmp redirect from 127.0.0.1: => 127.0.0.1
I have no idea where they come from and better how to get rid of
them...
Can anyone point me in a direction to solve t
Hello,
Lately i get a lot (really a lot) of these errors:
icmp redirect from 127.0.0.1: => 127.0.0.1
I have no idea where they come from and better how to get rid of them...
Can anyone point me in a direction to solve this problem?
Thanks in advance
Arno
my firewall rules:
#!/bin
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
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 overload
[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 ex
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
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 overload
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 chang
In the last episode (Jul 09), Bob Hall said:
> This isn't critical, but I'm wondering if someone can tell me what is
> going on here.
>
> I did
> traceroute 217.20.241.75
> and got several of the following on ttyv0, which displays kernel and
> other messa
This isn't critical, but I'm wondering if someone can tell me what
is going on here.
I did
traceroute 217.20.241.75
and got several of the following on ttyv0, which displays kernel and
other messages:
icmp redirect from 213.232.120.198: 217.20.241.75 => 213.232
12 matches
Mail list logo
