From: Edmund Green <confusedmund@yahoo.co.uk>
To: snodx@hotmail.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: IP ADDRESS OF MACHINE
Date: Thu, 28 Feb 2002 03:55:00 -0000 [thread overview]
Message-ID: <3C7E1351.2080804@yahoo.co.uk> (raw)
In-Reply-To: <-1315982412.1014892412831.JavaMail.root@naini.zyberway.com>
> In short I am looking for a program like /bin/netstat --route only this program is to be
> much much much simpler. It just needs to retrieve the TCP/IP Address 192.168.0.2 and display
> it.
Well unfortunately I don't think that you can do this so simply, because the machine itself doesn't have an IP
address, it is the interfaces that have the IP addresses and you will be using different interfaces depending upon where
you are connecting to (for example consider the common situation of a computer which is acting as a firewall / router
between the internet and an home network, it will have one external IP address on the interface talking to the internet,
a different IP address on the interface on the home network, and a third IP address (127.0.0.1) for talking to itself)
If you open a socket connection to somewhere, _then_ you can ask what the IP address of the interface on your end of
the socket was, but until you do that (or manually read through your routing tables and network card configurations)
then you don't know which IP address you're interested in (for example in your case being surprised that you were given
the localhost address)
Alternativly going the get host by name route as a previous poster demonstrated will work, but you might have to try
setting up your /etc/hosts file as:
127.0.0.1 localhost.localdomain localhost
192.168.0.2 mymachine.mydomain mymachine
if you've also got your /etc/host.conf set up to use "hosts, bind", otherwise if you put the name of your machine on
the 127.0.0.1 line then it will still (correctly) return the address 127.0.0.1, because that is the IP address you are
interested in if you want to open a socket to yourself.
Edmund.
ps, is there a more appropriate newsgroup for this kind of question than gcc-help?
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
next prev parent reply other threads:[~2002-02-28 11:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 3:25 snodx
2002-02-28 3:55 ` Edmund Green [this message]
[not found] <616BE6A276E3714788D2AC35C40CD18D53345D@whale.softwire.co.uk>
2002-03-05 1:18 ` Rupert Wood
[not found] <616BE6A276E3714788D2AC35C40CD18D47C245@whale.softwire.co.uk>
2002-02-28 5:39 ` Rupert Wood
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 4:04 snodx
2002-02-28 4:30 ` Michal Lipták
2002-02-28 3:56 snodx
[not found] <616BE6A276E3714788D2AC35C40CD18D47C203@whale.softwire.co.uk>
2002-02-28 2:43 ` Rupert Wood
2002-02-28 1:38 snodx
2002-02-27 9:17 snodx
2002-02-27 19:32 ` Andrea 'Fyre Wyzard' Bocci
2002-02-28 6:03 ` Nelson Guedes Paulo Junior
2002-02-28 6:49 ` John Love-Jensen
2002-02-28 10:15 ` Nelson Guedes Paulo Junior
2002-03-01 6:34 ` John Love-Jensen
2002-03-05 1:07 ` Bharathi S
2002-02-27 5:13 snodx
2002-02-26 18:29 Robert Lopez
2002-02-26 4:18 snodx
2002-02-26 5:46 ` Stephano Mariani
2002-02-28 14:02 ` Florian Weimer
2002-02-26 0:35 snodx
2002-02-26 1:29 ` Frank Schafer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C7E1351.2080804@yahoo.co.uk \
--to=confusedmund@yahoo.co.uk \
--cc=gcc-help@gcc.gnu.org \
--cc=snodx@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).