My random thoughts...
On 07/05/2007 02:09:20 PM, Jeff Santos wrote:
This firewall runs "route -s" because there is a need
to publish RIPv1 routes for these networks.
(You mean routed.)
I'm always suspicious of RIP. It's so easy for
a rouge device to mess up the whole network.
You might examine RIP logs. Just a thought.
Now, every once in while I get errors like:
PING 200.132.120.2 (200.132.120.2): 56 data bytes
ping: sendto: No route to host
ping: wrote 200.132.120.2 64 chars, ret=-1
64 bytes from 200.132.120.2: icmp_seq=1 ttl=64 time=0.231 ms
64 bytes from 200.132.120.2: icmp_seq=2 ttl=64 time=0.238 ms
--- 200.132.120.2 ping statistics ---
3 packets transmitted, 2 packets received, 33.3% packet loss
round-trip min/avg/max/std-dev = 0.231/0.234/0.238/0.015 ms
I know there is an arp entry for the IP address above.
You could prove it by manually locking an entry in the arp
table and seeing if that makes the problem go away.
I would be really thankful to anyone that can suggest some
possible reason, test, insight.
Bad port on a switch?
Karl <[EMAIL PROTECTED]>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
