public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Bastiaan van den Berg <buzz@spacedout.nl>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] AT&T/ISPs making Bitcoin Core near impossible to use as a full node via hidden private dynamic IPs, not by specifically blocking 8333 or Bitcoin as stated in original email
Date: Fri, 4 Sep 2015 15:47:41 +0200	[thread overview]
Message-ID: <CACLj26JFHNV5c-N-BVSL==hO5tEtF6K29iaWpSz1aKe+ouCCEQ@mail.gmail.com> (raw)
In-Reply-To: <14f97c85622-1774-173a8@webprd-a78.mail.aol.com>

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

On Fri, Sep 4, 2015 at 11:55 AM, Zach G via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> It's not so simple though, AT&T will not let you have a public static IP
> without paying.


Not sure, but, what part of bitcoin development are you addressing in this
email?

--
buZz

[-- Attachment #2: Type: text/html, Size: 731 bytes --]

      reply	other threads:[~2015-09-04 13:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1954364.4gG0cHmrlB@crushinator>
2015-09-02 13:44 ` [bitcoin-dev] AT&T has effectively banned Bitcoin nodes via utilizing private subnets hurricanewarn1
2015-09-02 19:21   ` Matt Whitlock
2015-09-02 20:31     ` hurricanewarn1
2015-09-04  9:55     ` [bitcoin-dev] AT&T/ISPs making Bitcoin Core near impossible to use as a full node via hidden private dynamic IPs, not by specifically blocking 8333 or Bitcoin as stated in original email hurricanewarn1
2015-09-04 13:47       ` Bastiaan van den Berg [this message]

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='CACLj26JFHNV5c-N-BVSL==hO5tEtF6K29iaWpSz1aKe+ouCCEQ@mail.gmail.com' \
    --to=buzz@spacedout.nl \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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