From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] upnp isnt working
Date: Fri, 30 Dec 2011 01:02:22 -0800 [thread overview]
Message-ID: <1325235742.2976.0.camel@BMThinkPad.lan.bluematt.me> (raw)
In-Reply-To: <1325235436.4059.YahooMailNeo@web121006.mail.ne1.yahoo.com>
On Fri, 2011-12-30 at 00:57 -0800, Amir Taaki wrote:
> hey,
>
> so sipa/gmaxwell proposed on irc that maybe upnp is not working anymore but there isnt any way to test.
>
> well i made an alternate chain, and ran the daemon on my vps.
>
> sometimes it accepts connections, sometimes not. It's all very patchy.
>
> anyway just putting this out there
I believe the issue isn't lack of working, but lack of re announcing to
the router that the port needs to remain open.
Matt
prev parent reply other threads:[~2011-12-30 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 8:57 Amir Taaki
2011-12-30 9:02 ` Matt Corallo [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=1325235742.2976.0.camel@BMThinkPad.lan.bluematt.me \
--to=bitcoin-list@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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