This traffic is Novell's SLP <service locator
protocol> and is perfectly normal if you are running
NDS on your network.
--- David <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> i have tried traceroute, and i see nothing wrong
> there; all packets make
> it, with no loss, and good latency...
>
> I'm also looking at trafshow on one of the server,
> and i have difficulty
> seeing what could be relevent in there... One thing
> i dont understand,
> is connections from svrloc.mcast.net, lots of them,
> all udp on port 427;
> but when i do a traceroute on it, i get no
> response....
>
> here is some of the trafshow output... none of these
> address are my
> server's address, so i dont really understand why it
> would show up as
> traffic on my computer, unless it was relaying info
> in some way..??
>
> udp SVRLOC.MCAST.NET 427 132.206.46.30*
> 1051
> udp SVRLOC.MCAST.NET 427 132.216.80.142*
> 1027
> udp SVRLOC.MCAST.NET 427 132.206.46.170*
> 1044
> udp SVRLOC.MCAST.NET 427 132.206.46.109*
> 1052
> udp SVRLOC.MCAST.NET 427 132.206.46.188*
> 1058
> udp 132.206.141.234 427 SVRLOC.MCAST.NET
> 427
> udp 132.206.137.178* 427 SVRLOC.MCAST.NET
> 427
> udp FACL67.FACL.McGill. 427 SVRLOC.MCAST.NET
> 427
> udp SVRLOC.MCAST.NET 427 arts848.ARTS.McGill
> 1027
> udp FACL26.FACL.McGill. 427 SVRLOC.MCAST.NET
> 427
> udp SVRLOC.MCAST.NET 427 eval4.CC.McGill.CA
> 1028
> udp SVRLOC.MCAST.NET 427 132.206.46.191
> 1054
> udp 132.206.161.18* 427 SVRLOC.MCAST.NET
> 427
> unkn 132.206.154.190* SVRLOC.MCAST.NET
> unkn 132.206.154.1 ALL-SYSTEMS.MCAST.N
> udp 132.206.156.71 427 SVRLOC.MCAST.NET
> 427
>
> 4071K total, 0K bad, 1762K nonip 627K tcp,
> 1587K udp, 17K icmp,
> 76K unkn
>
>
> this could be a legit thing... i have no idea;
> surely someone knows :)
>
>
> Daniel Brandt wrote:
> >
> > traceroute.
> >
> > Run a couple of traceroutes from other locations
> to your hosts and vice
> > verca.. that should show you where along the line
> the problem is.
> >
> > I found a bad TP-cable with traceroute once =)
> >
> > // Daniel
> >
> > That which is overdesigned, too highly specific,
> anticipates outcome;
> > the anticipation of outcome guarantees, if not
> failure, the abcense
> > of grace. - Willam Gibson
> >
> > -----Original Message-----
> > From: David [mailto:[EMAIL PROTECTED]]
> > Sent: den 26 september 2001 16:00
> > To: [EMAIL PROTECTED]
> > Subject: Packet loss
> >
> > Need a little help here, as i don't know where to
> look next....
> >
> > Question: what tools can i use to investigate
> packet loss problems?
> >
> > I have 3 servers running on two machines, set up
> on the lan at work, but
> > open to the net. and all servers are getting bad
> packet loss troubles.
> > This problem started suddenly, after over 8 months
> of everything fine
> > (prob started before the new patch, so i don't
> believe it's related).
> > and since both machines have the problem, i'm
> guessing its a local
> > network problem... Pings are still fine for
> everyone, but the connection
> > time as increased (often times out), and the
> packet loss is way high. I
> > have tried running the servers clean, without
> metamod & all, but the
> > problem is the same. I have no other service on
> the machines other than
> > hlds_l, and i'm the only user...
> >
> > anyone have an idea what could be causing these
> problems? and how could
> > i investigate farther?
> >
> > thx
>
>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger.
http://im.yahoo.com
