From owner-freebsd-questions Mon Sep 30 10: 0: 0 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D82ED37B401 for ; Mon, 30 Sep 2002 09:59:58 -0700 (PDT) Received: from vectors.cx (manifold.vectors.cx [64.163.147.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B6D743E6E for ; Mon, 30 Sep 2002 09:59:58 -0700 (PDT) (envelope-from monkey@vectors.cx) Received: from vectors.cx (310e9b796329db5e7189aef87a3ce8da@localhost [127.0.0.1]) by vectors.cx (8.12.6/8.12.4) with ESMTP id g8UH0jho037572; Mon, 30 Sep 2002 10:00:45 -0700 (PDT) (envelope-from monkey@vectors.cx) Received: (from monkey@localhost) by vectors.cx (8.12.6/8.12.6/Submit) id g8UH0jW2037571; Mon, 30 Sep 2002 10:00:45 -0700 (PDT) (envelope-from monkey) Date: Mon, 30 Sep 2002 10:00:45 -0700 From: Adam Weinberger To: Derrick Ryalls Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 4.7 RC problem Message-ID: <20020930170045.GZ77771@vectors.cx> References: <000501c2684f$eb276d90$0200a8c0@bartxp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000501c2684f$eb276d90$0200a8c0@bartxp> X-Editor: Vim 6.1 http://www.vim.org X-Mailer: Mutt 1.5 http://www.mutt.org X-URL: http://www.vectors.cx http://www.crackula.com User-Agent: Mutt/1.5.1i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG did you remove the bpf device from the kernel? have him boot into kernel.GENERIC and see if it's happy from within there. -Adam >> (09.30.2002 @ 0006 PST): Derrick Ryalls said, in 1.3K: << > First time posting here, and I didn't see the topic before, so here it > goes... > > I agree to help my brother set up a new bsd box six hours away, doing > everything remotely once there is network access to the box. After some > hardware issues were resolved, I did a cvsup to get everything up to > date and ready for a kernel compile. The o/s will eventually be used as > a router, but for now it has just one nic. > > cvsup goes fine, and I start the buildworld. No errors through the > whole process, so I reboot to switch to the new kernel. The machine is > now dead to me, it won't respond to pings/ssh/begging. On site, the box > is running, and my brother can log in fine (directly, not via ssh). > When I ask him to ping around or even ping localhost, it comes up with > "ping: sendto: permission denied". He also can't even ssh out. This > looks like a permissions/firewall issue, but he is logging in as root, > and there is no firewall active. The kernel does have settings for > routing, but nothing is activated in rc.conf. Has anyone heard of this > sort of error? At this point, we can't even hope for a fix later and > just cvsup it when it comes out, the only other option is to toast the > machine completely and go with an earlier revision and not cvsup. > > -Derrick > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > >> end of "4.7 RC problem" from Derrick Ryalls << -- "Oh good, my dog found the chainsaw." -Lilo, "Lilo & Stitch" Adam Weinberger adam@vectors.cx http://vectors.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message