1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bitcoin-list@bluematt.me>) id 1RgYMC-0006TY-UN
for bitcoin-development@lists.sourceforge.net;
Fri, 30 Dec 2011 09:02:32 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bluematt.me
designates 173.246.101.161 as permitted sender)
client-ip=173.246.101.161;
envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me;
Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me)
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1RgYMB-0004tC-US for bitcoin-development@lists.sourceforge.net;
Fri, 30 Dec 2011 09:02:32 +0000
Received: from [10.0.1.14] (c-24-4-11-52.hsd1.ca.comcast.net [24.4.11.52])
by mail.bluematt.me (Postfix) with ESMTPSA id EC0143F8
for <bitcoin-development@lists.sourceforge.net>;
Fri, 30 Dec 2011 09:55:57 +0100 (CET)
From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
In-Reply-To: <1325235436.4059.YahooMailNeo@web121006.mail.ne1.yahoo.com>
References: <1325235436.4059.YahooMailNeo@web121006.mail.ne1.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 30 Dec 2011 01:02:22 -0800
Message-ID: <1325235742.2976.0.camel@BMThinkPad.lan.bluematt.me>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.8 (--)
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 SPF_PASS SPF: sender matches SPF record
-1.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1RgYMB-0004tC-US
Subject: Re: [Bitcoin-development] upnp isnt working
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 30 Dec 2011 09:02:33 -0000
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
|
