North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Tags

  • From: Tom Sanders
  • Date: Fri Aug 19 07:21:56 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=md8Azums1TzQvfg/HReI1eXzi9VJoGg/BOWaHR2XEpl37l+kTu68ZSTsSMiEMUY0fdAG+TX+DrRlx02VyIPxJrvKwM3x8mJdLMF7RUwtxyqb82eucg8fiZv2iFFqgVe2wPrmv+Lf8EFCXYC2ylJzV3RyHdE5P4FJeOtkw1eLTXM=
> 
> The other side is where your customers are living. There are living real
> system and network managers who know what they are doing. I dont think they
> let slip RIP into your network.

ok

> But there are also people who believe in windows, who believe it makes sense
> to use netbios packets in the internet. They dont even know their box is
> sending and receiving RIP.

I dont recollect any connection between Netbios and RIP. Am i missing
something? Even if some application is leaking the RIP packets, why
would they carry a tag in them?

I thought it was a field rarely used in the implementations.

> 
> I dont believe in blocking internet packets, but I am shure it is a good
> idea blocking those RIP packets. They are definitely ment to stay in the
> local network. RIP was never meant for the internet. Only missconfigured
> router allow it to pass through.
> 
> And I cannot imagine anybody using RIP packets for SSH or something like
> that :)
> 
> >
> > Thanks,
> > Tom
>