Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Jan 2000 21:09:09 +0200
From:      Ruslan Ermilov <ru@ucb.crimea.ua>
To:        Bohdan Tashchuk <tashchuk@easystreet.com>
Cc:        Bill <ankzt@maine.60north.net>, Edirol <edirol@anime.ca>, questions@FreeBSD.org
Subject:   Re: natd - ping crash
Message-ID:  <20000110210909.A68327@relay.ucb.crimea.ua>
In-Reply-To: <37FEE832.EECB0B8C@easystreet.com>; from Bohdan Tashchuk on Sat, Oct 09, 1999 at 12:01:06AM -0700
References:  <Pine.BSF.4.05.9910081209580.85351-100000@maine.60north.net> <37FEE832.EECB0B8C@easystreet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi, guys!

I've just committed the patch into 4.0-CURRENT.
Please see http://www.freebsd.org/cgi/query-pr.cgi?8596 for details.
3.4-STABLE's commit will happen in a day or two.

On Sat, Oct 09, 1999 at 12:01:06AM -0700, Bohdan Tashchuk wrote:
> I have just confirmed this panic from a non-FreeBSD unix machine with a
> target of my FreeBSD machine running 3.3 release with natd (same Ethernet
> segment).
> 
> >From a non-FreeBSD Unix machine, as root, I did
> 
> 	 ping -f -R <freebsd-machine>
> 
> Instant causes panic (takes less than 1 second elapsed time)
> on FreeBSD machine:
> 
> 	Fatal trap 12: page fault while in kernel mode
> 
> I looked, and has already been reported as bug kern/11199. It really is a
> "panic", rather than a "simply reboot". The difference is that the kernel
> says it's syncing disks, etc. Then the kernel says 
> 
> 	automatic reboot in 15 seconds
> 
> So, unless you're right at the console and watching, the FreeBSD
> machine doesn't have any "sign of panic". But it really did panic.
> It just rebooted almost immediately and the panic message scrolled
> off the screen.
> 
> Needless to say, I immediately tried the suggested fix and added the
> following IPFW rule:
> 
> 	$fwcmd add deny log ip from any to any ipoptions rr
> 
> This fixed the problem. I let ping -f run for a few minutes and there
> was no panic even after 26,000 pings.
> 
> 
> 
> Bill wrote:
> > 
> > This is a very serious bug/security issue with natd, ping -r will simply
> > reboot freebsd if your running natd , ive seen no sign of pannic.
> >  A friend of mine discovered this in 2.6 release & it has since carried
> > over. Since I have been aware of it ive used IPFW deny ipopt rr since this
> > can be done over any networks to any fbsd machine using natd.
> > 
> > On Fri, 8 Oct 1999, Ruslan Ermilov wrote:
> > 
> > > On Fri, Oct 08, 1999 at 12:14:27AM -0400, Edirol wrote:
> > > > Hi,
> > > >
> > > > I'm running natd on a 3.3R system with the following command line
> > > > options -s -m -u
> > > >
> > > > When I ping -R my box from another computer, after a while the system
> > > > reboots itself.
> > > >
> > > Reboots or panics?
> > >
> > > --
> > > Ruslan Ermilov                Sysadmin and DBA of the
> > > ru@ucb.crimea.ua      United Commercial Bank,
> > > ru@FreeBSD.org                FreeBSD committer,
> > > +380.652.247.647      Simferopol, Ukraine

-- 
Ruslan Ermilov		Sysadmin and DBA of the
ru@ucb.crimea.ua	United Commercial Bank,
ru@FreeBSD.org		FreeBSD committer,
+380.652.247.647	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000110210909.A68327>