From owner-freebsd-questions Sat May 20 19: 0: 0 2000 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 779F337B81D for ; Sat, 20 May 2000 18:59:55 -0700 (PDT) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id VAA95052; Sat, 20 May 2000 21:59:22 -0400 (EDT) (envelope-from cjc) Date: Sat, 20 May 2000 21:59:22 -0400 From: "Crist J. Clark" To: Khairuddin Abdul Ghani Cc: freebsd-questions@FreeBSD.ORG Subject: Re: talkd error: [Error on write to talk daemon : Permission denied (13)] Message-ID: <20000520215922.F93357@cc942873-a.ewndsr1.nj.home.com> Reply-To: cjclark@home.com References: <003b01bfc2c4$4f094790$6f1f7d80@phoenix> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <003b01bfc2c4$4f094790$6f1f7d80@phoenix>; from abdulgha@usc.edu on Sat, May 20, 2000 at 06:31:38PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 20, 2000 at 06:31:38PM -0700, Khairuddin Abdul Ghani wrote: > Hi everyone! > > There seems to be an error with my ntalkd recently. Whenever someone would > want to 'talk' to someone on localhost, he/she gets the message > > [No connection yet] > [Error on write to talk daemon : Permission denied (13)] > > and the talk program quits. I checked, and it seems that the following ipfw > rule was causing it: > > 00200 deny ip from any to 127.0.0.0/8 Any legit traffic being blocked by this should be accepted in your rule 100. > which is weird since that rule is a default from within /etc/rc.firewall. > When I remove this rule, I would instead get the following: > > [No connection yet] > [Checking for invitation on caller's machine] > [Checking for invitation on caller's machine] > . > . > > The thing is, talkd seemed to work fine before. But lately, many other weird > things have been happening. An increase in incoming traffic would sometimes > cause the box to shutdown most vital internet daemons, plus delete certain > lib files like mm (for apache) and tcl. Looks to me like the box has been > breached, but I've checked all the advisories and all seem to have been > taken care off. Anyhow, I'll paste some of the configuration that might be > causing these below, and hopefully there's someone out there who can help! > Thanks all. :) > > Regards, Rudy. > > ipfw rules: > 00100 allow ip from any to any via lo0 > 00200 deny ip from any to 127.0.0.0/8 > 00500 pipe 1 udp from any to any > 02000 allow tcp from any to 127.0.0.0/8 3306 > 02100 deny tcp from any to any 3306 <-- deny remote sql requests. > 65000 allow ip from any to any > 65535 allow ip from any to any What the heck is 2000? > netstat -nr: > Internet: > Destination Gateway Flags Netif Expire > default 216.65.57.1 UGSc fxp0 > xxx.25.134 link#1 UC fxp0 => > xxx.25.134.1 0:a0:c9:e8:c3:1f UHLW fxp0 1114 > xxx.25.134.2 0:90:27:ad:45:5d UHLS lo0 > xxx.25.134.3 0:90:27:ad:45:5d UHLS fxp0 > . > . > yyy.65.57 link#1 UC fxp0 => > yyy.65.57.1 0:a0:c9:e8:c3:1f UHLW fxp0 1186 > yyy.65.57.2 0:90:27:ad:45:5d UHLW lo0 > yyy.65.57.3 0:90:27:ad:45:5d UHLS fxp0 > . > . > yyy.65.57.255 ff:ff:ff:ff:ff:ff UHLWb fxp0 Where is the loopback configuration in this? There should be a line like, 127.0.0.1 127.0.0.1 UH lo0 What does, $ ifconfig lo0 Return? -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message