From: Eric Saxby (esaxby_at_uclink.berkeley.edu)
Date: Mon Aug 25 2003 - 15:06:41 PDT
Hi Lucas,
I did a tcp dump from one of the effected computers. I didn't see
anything particularly odd while the network was working. A lot of
traffic came through from addresses elsewhere on campus, calling for
239.255.255.253.svrloc: udp 49. From a google search, that seemed like
something pretty normal to see.
When the network went down, a tcpdump picked up less than 50 packets
tcpdump: listening on en0
^C
47 packets received by filter
0 packets dropped by kernel
the dumpfile was then one line, with only a time stamp. There wasn't
even a dns name or ip address associated with the packet.
I'd initially assumed that this was a welcome week issue, but I just
want to double check to make sure it's not something more complicated.
I'll try more tracerouting in a bit, since my first few didn't pick up
anything out of the ordinary (when the net went down it couldn't even
get to the first switch, of course).
Thanks for the responses!
Eric
On Monday, August 25, 2003, at 12:49 PM, Lucas Rockwell wrote:
> When traffic on the network seems to slow down or even stop, use
> tcpdump
> if you have an OS X machine.
-- Eric Saxby Berkeley Art Museum/Pacific Film Archive Computer Resource Specialist Digital Media Department esaxby_at_uclink.berkeley.edu 510-642-9623 ------------------------------------------------------------------------ The following was automatically added to this message by the list server: For information about Micronet, including subscribing to or unsubscribing from its mailing list and finding out about upcoming meetings, please visit the Micronet Web site: <http://micronet.berkeley.edu/>.
This archive was generated by hypermail 2.1.5 : Mon Aug 25 2003 - 16:32:29 PDT