From owner-freebsd-questions Mon Dec 9 11:08:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA22333 for questions-outgoing; Mon, 9 Dec 1996 11:08:49 -0800 (PST) Received: from mpeks.tomsk.su (mpeks.tomsk.su [193.124.185.19]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA22302 for ; Mon, 9 Dec 1996 11:08:18 -0800 (PST) Received: (from uucp@localhost) by mpeks.tomsk.su (8.6.11/8.6.9) with UUCP id CAA06418; Tue, 10 Dec 1996 02:07:17 +0700 Received: (from victor@localhost) by vas.tomsk.su (8.6.12/8.6.12) id XAA00310; Mon, 9 Dec 1996 23:11:02 +0700 To: freebsd-questions@freebsd.org, steve@edmweb.com References: Message-ID: Organization: Tomsk Region Education Department From: "Victor A. Sudakov" Date: Mon, 9 Dec 96 23:11:01 +0700 X-Mailer: BML [UNIX Beauty Mail v.1.39] Subject: Re: "talk" does not work. Please help. Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I do not think so. AFAIK localhost in FreeBSD cannot have an > > arbitrary address, only 127.0.0.1 > > It's a network interface, just like all the others. You can assign it an > alias or a completely new address. > > root@bitbucket:/root# ifconfig lo0 10.0.0.1 > root@bitbucket:/root# ping 10.0.0.1 > PING 10.0.0.1 (10.0.0.1): 56 data bytes > 64 bytes from 10.0.0.1: icmp_seq=0 ttl=255 time=2.152 ms Thank you very much for your advice. Now look what I have done. On my machine, at boot time the address 127.0.0.1 is associated with lo0, the address 10.0.0.1 is not associated with any interface. Therefore "ping 127.0.0.1" works while "ping 10.0.0.1" does not work. Then I say: vas# ifconfig lo0 inet 10.0.0.1 alias FreeBSD says: vas# ifconfig: ioctl (SIOCAIFADDR): File exists And after that both "ping 127.0.0.1" and "ping 10.0.0.1" begin to work!!!! "talk" also works!!! Great! I would be absolutely happy if I could get an answer to 2 more questions: 1. What does this "ifconfig: ioctl (SIOCAIFADDR): File exists" message mean? Is it an error? 2. How can I assign the 10.0.0.1 alias to lo0 automatically on startup? I do not like the idea of issuing this command manually after each reboot. Shall I put it into some kind of startup file? Any ideas? Thank you very much in advance. --- Victor A. Sudakov E-mail: victor@vas.tomsk.su Center of Information Technologies FidoNet: 2:5005/49 Tomsk Region Education Department Telephone: +7 3822 224916 Tomsk, Russian Federation Telefax: +7 3822 225912