Also, you might verify the problem by using both ping (as provided by OS) and fping (as provided by http://www.fping.com/). It seems that one relied on the kernel's cache and one didn't.
You're getting into some murky areas here--areas that a networking class would likely not help too much (assuming you know the basics about how ping/ICMP work...) Shane O> On 1/10/06, Ron Joffe <[EMAIL PROTECTED]> wrote: > On Tuesday 10 January 2006 12:38, Brian Henning wrote: > > Hi Folks, > > Just wondering if someone could shed some light on why it seems that > > some tcp utilities seem to ignore the kernel routing table. For > > example: (Sorry about the wrapping..) > > Could the problem be on the remote end. The packets might be getting there, > but might not know how to route back to your box. > > Is this a vpn or tunnel that you have set up with forwarding from 1.124 to the > 192.168.10.0 network? > > Ron > > -- > TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug > TriLUG Organizational FAQ : http://trilug.org/faq/ > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ > -- Shane O. ======== Shane O'Donnell [EMAIL PROTECTED] ==================== -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
