From owner-freebsd-hackers Sat Aug 30 18:11:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA10785 for hackers-outgoing; Sat, 30 Aug 1997 18:11:58 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA10734 for ; Sat, 30 Aug 1997 18:11:44 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id BAA24050; Sun, 31 Aug 1997 01:33:26 +0100 (BST) Message-Id: <199708310033.BAA24050@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Kyle Mestery cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: Sig 12's with user PPP In-reply-to: Your message of "Thu, 28 Aug 1997 22:37:06 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Aug 1997 01:33:25 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Fri, 29 Aug 1997, Brian Somers wrote: > > > Sounds *really* like an installation thing. Can you remove the UID > > bit on ppp and run it as root. You should get a core with the sig 12 > > - it would be interesting to know what the syscall problem is. > > > Sure, I can try this, but this happens regardless of whether or not I run > ppp as root or as another user. As "Snob Art" pointed out, you don't get a core if the UID bit is set. > > The routing table thing also sounds like something's out of step. > > Perhaps a "make world" followed by a kernel install then a reboot is > > in order ? What sort of "screwing up" does your routing table > > experience ? > > > My impression is that it would not be solved by a make world, because as I > said this problem has followed me through make world build since early > june or so. As far as the routing tables being messed up, normally ppp > just adds a default route. But, when it gets "screwed up" it appears taht > ppp is trying to add a separate route to every host it can, in other words > this is what my routing table looks like: > > hope.winternet.com$ netstat -rn > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif > Expire > default 204.246.71.1 UGSc 1 6 tun0 > 10.0.2/24 link#1 UC 0 0 > 10.0.2.18 0:0:c0:f2:16:9c UHLW 0 20 lo0 > 10.0.2.255 ff:ff:ff:ff:ff:ff UHLWb 1 326 ed0 > 127.0.0.1 127.0.0.1 UH 1 26 lo0 > 192.129.84 204.246.71.1 UGc 0 0 tun0 > 198.137.142 204.246.71.1 UGc 0 0 tun0 > 198.174.169 204.246.71.1 UGc 2 0 tun0 [.....] > 204.246.71.1 204.246.64.128 UH 39 0 tun0 > 204.246.76 204.246.71.1 UGc 0 0 tun0 > 204.246.78 204.246.71.1 UGc 0 0 tun0 [.....] > This seems rather large to me. I am running routed with -q. I am now > thinking of trying gated. I am just wondering if anyone else is seeing > these sig12s, and if not, then why I am the only one seeing them. Why are you running routed ? Are you getting any RIP packets from anywhere ? Try disabling routed altogether. If this doesn't help, can you post your config files ? The only time I've seen this sort of thing is when you've got a default route to a router that keeps sending back redirects for everything you want to talk to - but your default route above is correct. There's no reason for the extra routes. > Kyle Mestery > StorageTek's Network Systems Group > 7600 Boone Ave. N., Brooklyn Park, MN 55428 > mesteka@anubis.network.com, mestery@winternet.com > -- Brian , Don't _EVER_ lose your sense of humour....