Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!brutus.cs.uiuc.edu!unix.cis.pitt.edu!obie.cis.pitt.edu!cmf
From: cmf@obie.cis.pitt.edu (Carl M. Fongheiser)
Newsgroups: comp.unix.wizards
Subject: Re: Determining one's own IP address.
Message-ID: <21146@unix.cis.pitt.edu>
Date: 13 Dec 89 19:13:21 GMT
References: <601@bmers58.UUCP> <4429@ur-cc.UUCP>
Sender: news@unix.cis.pitt.edu
Reply-To: cmf@obie.cis.pitt.edu (Carl M. Fongheiser)
Organization: University of Pittsburgh, Computing and Information Services
Lines: 16

In article <4429@ur-cc.UUCP> leadley@uhura.cc.rochester.edu (Scott Leadley) writes:
>If you don't know what interfaces are connected to the machine try:
>
>	% netstat -i
>	Name  Mtu   Network     Address      Ipkts   Ierrs Opkts   O...
>	de0   1500  x-net       x-machine    15890511 4     14812969...
>	lo0   1536  127         localhost    134349  0     134349  0...

Yep, and if you do "netstat -in", you won't even need to run ifconfig,
since netstat will print out the address without turning it into a name.

				Carl Fongheiser
				cmf@unix.cis.pitt.edu
				cmf@pittunix.BITNET
>-- 
>					Scott Leadley - leadley@cc.rochester.edu