Brad and I have also started seeing icmp problems to LSU today. lots of dropped packets, etc... weird thing is it only happens from SLU, works fine from home on i-55 (perhaps an internet2 issue...). Also only seems to affect their 130.39.184.0/24 subnet... the few other subnets i picked worked fine. I have not noticed any other problems, only icmp. Weird...
Also had some interesting results using ping -R (record route) a quick search turned up this tcp ping... looks like it just sends a SYN to port 1884 and measures round trip. unfortunately it doesn't say anything about dropped packets. YMMV... let me know if you find something better. http://www.eecs.umich.edu/~azeitoun/tools.html later! Ray -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ray DeJean http://www.r-a-y.org Systems Engineer Southeastern Louisiana University IBM Certified Specialist AIX Administration, AIX Support =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= On 5 Feb 2003, Shannon Roddy wrote: > Does anyone know of a good utility to test for dropped/lost packets via > non-icmp methods? LSU has a cap on the amount of icmp traffic that they > allow through. I am having network problems via LSU's network and I get > the standard response most of the time that it is the traffic shaping > software. I need to be able to prove that I am getting lost packets via > another method. > > Thanks, > Shannon > > > > _______________________________________________ > General mailing list > [email protected] > http://oxygen.nocdirect.com/mailman/listinfo/general_brlug.net >
