Hi, Thanks very much for your help.
> (You mean routed.) Exaclty. Thanks for the correction. > 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. I also suspect of routed. The output of "route monitor" shows a lot of activity with many RTM_ADD and RTM_LOSING. I would like to limit routed behaviour. I read through the man page but could not find a way of doing this: - keep some pre-established routes (including the default route) - publish routes to our subnets with RIPv1 so others can reach us - ignore all route related packets except for route redirection packtes from the default gateway > You could prove it by manually locking an entry in the arp > table and seeing if that makes the problem go away. I used the command below to prove it. I am not sure it is trustworth. It always showed an entry for the address I was trying to ping: arp -na | grep "200.132.120.2"; ping 200.132.120.2 > Bad port on a switch? When the problem occurs, I lose conectivity on all 3 interfaces. Could a hw problem (on one interface, or switch port, or cable, or connectors, or ...) result in this kind of situation? The reason I also suspect of me doing something stupid with my PF ruleset is that this firewall is replacing an old one running FreeBSD 5.3 & IPFW. Now, when I switch back to the old firewall using the very same cables, ports, etc, the problem goes away. Again, thanks in advance for any help. Regards, Jeff. -- We've Got Your Name at http://www.mail.com! Get a FREE E-mail Account Today - Choose From 100+ Domains
