From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WP8DC-0005K8-32 for bitcoin-development@lists.sourceforge.net; Sun, 16 Mar 2014 10:22:34 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.173 as permitted sender) client-ip=209.85.223.173; envelope-from=laanwj@gmail.com; helo=mail-ie0-f173.google.com; Received: from mail-ie0-f173.google.com ([209.85.223.173]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WP8D8-0001cp-Ol for bitcoin-development@lists.sourceforge.net; Sun, 16 Mar 2014 10:22:34 +0000 Received: by mail-ie0-f173.google.com with SMTP id rl12so4356389iec.4 for ; Sun, 16 Mar 2014 03:22:25 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.43.170 with SMTP id x10mr7115860igl.20.1394965345460; Sun, 16 Mar 2014 03:22:25 -0700 (PDT) Received: by 10.64.27.34 with HTTP; Sun, 16 Mar 2014 03:22:25 -0700 (PDT) In-Reply-To: References: Date: Sun, 16 Mar 2014 11:22:25 +0100 Message-ID: From: Wladimir To: Sam Michaels Content-Type: multipart/alternative; boundary=089e01176cade3eb5d04f4b6ade3 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WP8D8-0001cp-Ol Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] External IP Address X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Mar 2014 10:22:34 -0000 --089e01176cade3eb5d04f4b6ade3 Content-Type: text/plain; charset=UTF-8 Sam, On Sun, Mar 16, 2014 at 8:04 AM, Sam Michaels wrote: > You can look for X-Client-Update to see if the check in was logged. Other > information can be passed in the header, too. > > Errors are trapped so that it will always display the IP address and any > error information is contained in the headers. > > Hope you find this useful. > Thanks for your effort. However the current idea is to phase out reliance on centralized external services completely in favor of peer-based address detection. See https://github.com/bitcoin/bitcoin/pull/3461 Wladimir --089e01176cade3eb5d04f4b6ade3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sam,

On Sun, Mar 16, 2014 at 8:04 AM, S= am Michaels <sam@samtheham.org> wrote:
You can look for X-Client-Update to see if the check = in was logged. =C2=A0Other information can be passed in the header, too.

Errors are trapped so that it will always display the I= P address and any error information is contained in the headers.
=
Hope you find this useful.

Thanks for your effort.

However the= current idea is to phase out reliance on centralized external services com= pletely in favor of peer-based address detection.


Wladimir


--089e01176cade3eb5d04f4b6ade3--