public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Rupert Wood" <me@rupey.net>
To: <snodx@hotmail.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: IP ADDRESS OF MACHINE
Date: Thu, 28 Feb 2002 05:39:00 -0000	[thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D03AA5F@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D47C245@whale.softwire.co.uk>

Snodx wrote:

> BUT the interface through which an internet browser like Netscape
> Navigator or Lynx interacts with the Internet HAS to be after all
> one.

No. It will ask the OS for a connection, and the OS will determine which
interface to use from its route table. If you access both an intranet
and an intranet link then NS/Lynx may well use two different local IPs
during one session.

> I am talking about THIS IP Address that the system is using to talk
> to the internet.

The interface which talks to the internet will have:

    * a gateway address configured (which is not also a local address;
      sometimes you'll see interfaces configured with gateway their
      own address or loopback)
    * an unrestrictive routing entry, usually destination address
      0.0.0.0, netmask 0.0.0.0.

I'm not sure if both are necessary (or even sufficient); certainly if
there's only one non-local gateway configured then you use that
interface but if there are multiple then you'll have to check the route
table. Again, I don't know which system calls you'd use to do this on
any platform or if they'd be portable.

There's also no guarantee that the IP on that interface will be exposed
to the internet at all, e.g. the gateway might be a local NAT/firewall.
A browser can even just be targeted at a local web proxy without  any
gateways configured at all.

Rup.

       reply	other threads:[~2002-02-28 13:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <616BE6A276E3714788D2AC35C40CD18D47C245@whale.softwire.co.uk>
2002-02-28  5:39 ` Rupert Wood [this message]
     [not found] <616BE6A276E3714788D2AC35C40CD18D53345D@whale.softwire.co.uk>
2002-03-05  1:18 ` Rupert Wood
2002-02-28  4:04 snodx
2002-02-28  4:30 ` Michal Lipták
  -- strict thread matches above, loose matches on Subject: below --
2002-02-28  3:56 snodx
2002-02-28  3:25 snodx
2002-02-28  3:55 ` Edmund Green
     [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=616BE6A276E3714788D2AC35C40CD18D03AA5F@whale.softwire.co.uk \
    --to=me@rupey.net \
    --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).