Date: Mon, 09 Oct 2000 02:49:29 +0200 From: Palle Girgensohn <girgen@partitur.se> To: Raymond Wiker <Raymond.Wiker@fast.no> Cc: freebsd-net@FreeBSD.ORG Subject: Re: bridged vmnet make NIS go berzerk killing servers with icmp msgs Message-ID: <39E11619.4694F780@partitur.se> References: <87aeck14mk.fsf@palle.girgensohn.se> <39DC81E1.2C0F7315@quack.kfu.com> <14813.28763.410367.378304@raw.grenland.fast.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Raymond Wiker wrote: > > Nick Sayer writes: > > Palle Girgensohn wrote: > > > > > > Hi! > > > > > > Sorry for crossposting, but I'm not certain wheather this is -net or > > > -emulation; probably both... > > > > I see a similar failure every once in a while on FreeBSD machines that > > are NIS clients that are not running vmware, though it sounds to me like > > you are seeing it a lot more frequently. hmmm... not running vmware? are they running an IP bridge, or do you mean that this happens to vanilla fbsd systems? > > I can sometimes precipitate this by disconnecting an NIS client from the > > net briefly, using NIS, then reconnecting it. It ends up in the icmp > > supression state and the only way out is the history eraser button. Yes, that is usually a "good" way to trigger it, but I have seen it happen on occasion without disconnecting. Might be high network load at those times, though, I'm not sure. > You can achieve the same effect by putting wildly > inappropriate values in /var/yp/securenets... > > //Raymond. Maybe, I could deny all bridged IP's from NIS by putting only every allowed IP# in securenets, instead of the entire network as now? The odd thing is, it is not the bridged IP that sends the bad icmps, but the host's standard IP. /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39E11619.4694F780>