From owner-freebsd-security Sat Nov 27 14:26:58 1999 Delivered-To: freebsd-security@freebsd.org Received: from quasar.pucrs.br (quasar.pucrs.br [200.132.10.5]) by hub.freebsd.org (Postfix) with ESMTP id 3A96D14BDC for ; Sat, 27 Nov 1999 14:26:45 -0800 (PST) (envelope-from mwp@pucrs.br) Received: from pucrs.br (clapton.pucrs.br [200.132.13.11]) by quasar.pucrs.br (8.9.1a/8.9.1) with ESMTP id UAA37970 for ; Sat, 27 Nov 1999 20:25:04 -0300 Message-ID: <38405B15.64786825@pucrs.br> Date: Sat, 27 Nov 1999 20:28:38 -0200 From: Mauricio Westendorff Pegoraro X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.7 sun4m) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-security@FreeBSD.ORG Subject: Question about lo0 References: <14400.17989.189233.907961@anarcat.dyndns.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I had some problems when I installed and started squid. It was starting okay but after a few seconds it's gone, crashed, with a message that it could not bind a process to localhost when starting '(dns server)'. With help of this freebsd-security list (thanks Oleg Y. Ivanov) and some 'research', I found the problem was the misconfigured lo0 interface. In other words: Before I solve the problem my 'ifconfig lo0' was: lo0: flags=8049 mtu 16384 Then my localhost was pointing to the machine that was serving dns to my local server. So, I've 'ifconfig lo0 127.0.0.1' and all worked correctly, I mean squid started okay without crashing a few seconds later. Now, when I, 'ifconfig lo0' it shows: lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 And, as you can see, lo0 is pointing to its proper adress and not somewhere else. My question is: why the lo0 interface wasn't configured when the system started? It was a problem (bug) when freebsd tryied to configure lo0? Or, by default, freebsd doesn't 'autoconfigure' lo0? There are some mails in the list about problems with localhost. Wouldn't they be someway related with this lo0 misconfiguration problem? Please, don't get me wrong. It's only thoughts. It was a long time since I last worked with FreeBSD, so there are many new things (good things and 'problem' things) in release 3.3 I'm not aware yet, which I'd like to know/understand (in last couple years I've been working only with Solaris, AIX and Linux). Regards, MauricioWP. ----------------------------- Mauricio Westendorff Pegoraro PUCRS - Brazil Unix Team To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message