Bitcoin client with I2P patch - page 2.

matthewh3

legendary

Activity: 1372

Merit: 1003

Quote from: giv on September 15, 2013, 04:40:04 AM

This update does not influence to connections. But last few days I has only 1-2 connections. I don't know what happened with other nodes, but my nodes are working fine.
Try to rerun you client. If it doesn't help, try to manually add nodes by the 'addnode' command with the following addresses:

Code:

bhqfvosghsfdbi3qubnk3ro6juklz5w7b6l3x6mibkxzzk3mob5a.b32.i2p
z5pg37axylu7wuncppbzvwxawb5mo3euxuwbyi2s2um7bhnl3caa.b32.i2p
ofa7kfuqewnxyqiadnsj6ibcwtj6ndcabwcfabljmuyol2pussaa.b32.i2p
mzvsw6bwae6ul33b5zege5xie2cevno6vgik6nrb6lw74cn3wmdq.b32.i2p

After the update manger on Xubuntu downloaded the official updates then I ran your exe's it works OK. Just got three I2p peers within five minutes.

Edit: Soon up to four peers.

justusranvier

legendary

Activity: 1400

Merit: 1009

I'm seeing this problem with listen=1 and maxconnections=256 set in bitcoin.conf

My node will end up with 3-4 peers, none of them I2P, and it will drop the SAM connection so that the I2P node no longer creates the tunnels, which prevents incoming I2P connections.

The only way I can get any native I2P connections at all is to run the node with onlynet=native_i2p

giv

sr. member

Activity: 254

Merit: 251

Quote from: justusranvier on September 16, 2013, 03:20:45 AM

I've noticed that I frequently check my peer list and find no i2p peers unless I use -onlynet-native_i2p, but I'd like to also use other peer types.

Quote from: giv on August 18, 2013, 11:57:55 AM

If you run the patched client in mixed mode, most probably it will use only ip-addresses for outgoing connections. That's why. The bitcoin-client has a pool of known addresses. Selecting of address is a pseudorandom process. At now there are hundreds (at first start) and thousands (after syncing with other clients) known ip-addresses and only several I2P-addresses in the pool. By default only 8 outgoing connections are allowed. So probability of selecting an i2p-address is less than 1%.
If you want to run the program in mixed mode, but want to connect with some i2p-nodes (for tests or other purposes) you have to add an i2p-node manually with "-addnode=" option. Also you may publish your i2p-address or PM me and others can connect to your client. In such case you will see his connections as incoming.

Of course, if your i2p-address changes you should publish the new address again. Obviously, it's inconveniently, so I suggest to use a static i2p-address in this case.
Also if you use the '-tor'/'proxy' options (or appropriate settings in gui) you should use the '-listen' option if you want to accept incoming i2p-connections, because the '-tor'/'proxy' options disable the '-listen' option by default.

justusranvier

legendary

Activity: 1400

Merit: 1009

I've noticed that I frequently check my peer list and find no i2p peers unless I use -onlynet-native_i2p, but I'd like to also use other peer types.

giv

sr. member

Activity: 254

Merit: 251

If you get one of these messages:
"... coin database inconsistencies found"
and/or
"Do you want to rebuild the block database now?",
please DO NOT redownload/reindex the blocks (it will just waste your time, especially via i2p).
It is known issue and it's resolved in the 0.8.5 release. So just update your wallet to 0.8.5, if you still didn't do that
More info here:
https://bitcointalksearch.org/topic/bitcoin-qt-bitcoind-version-085-released-293307
https://bitcointalksearch.org/topic/all-bitcoind-bitcoin-qt-nodes-failing-to-come-up-workaround-inside-290922

giv

sr. member

Activity: 254

Merit: 251

This update does not influence to connections. But last few days I has only 1-2 connections. I don't know what happened with other nodes, but my nodes are working fine.
Try to rerun you client. If it doesn't help, try to manually add nodes by the 'addnode' command with the following addresses:

Code:

bhqfvosghsfdbi3qubnk3ro6juklz5w7b6l3x6mibkxzzk3mob5a.b32.i2p
z5pg37axylu7wuncppbzvwxawb5mo3euxuwbyi2s2um7bhnl3caa.b32.i2p
ofa7kfuqewnxyqiadnsj6ibcwtj6ndcabwcfabljmuyol2pussaa.b32.i2p
mzvsw6bwae6ul33b5zege5xie2cevno6vgik6nrb6lw74cn3wmdq.b32.i2p

matthewh3

legendary

Activity: 1372

Merit: 1003

Quote from: giv on September 13, 2013, 09:12:32 AM

Update 13 Sep 2013
Migrated to 0.8.5.

I downloaded your two new (linux) executables and ran them but I can't seem to get any peers any more. Is there a method to updating?

giv

sr. member

Activity: 254

Merit: 251

Update 13 Sep 2013
Migrated to 0.8.5.

giv

sr. member

Activity: 254

Merit: 251

Four nodes it is ok. Today I have only 4-5 nodes too. Of course the more peers the better, but 3-5 peers are enough to send/receive a transaction to the rest net with admissible speed.
Judging by I2P stats your ports are still closed. If you open the ports you'll see smth like this:

Code:

Peers
Active:	1329 / 3850

But if you can't open them it's nothing. Probably in this case your i2p-connection will be a little bit slower or less stable, but nothing serious.

If your wallet is always running with a static i2p-address you can send your public i2p-address to me and I'll add it as seed-node in my code if you want.

matthewh3

legendary

Activity: 1372

Merit: 1003

All day yesterday and so far today I've been connected to four peers in I2p only mode. Here are my I2p stats

Code:

Peers
Active:	26 / 205
Fast:	19
High capacity:	89
Integrated:	445
Known:	507

Bandwidth in/out
3 sec:	2.93 / 2.95 KBps
5 min:	2.30 / 3.80 KBps
Total:	3.83 / 3.38 KBps
Used:	19.57 MB / 17.54 MB

Tunnels
Exploratory:	6
Client:	6
Participating:	0
Share ratio:	0.00

Congestion
Job lag:	0
Message delay:	99 ms
Backlog:	0

Is four connections right or are my I2p stats low. I mostly use a VPN to connect to the internet so not sure if I can forward any ports?

Edit: Its gone to and stayed at three peers now. Here are my I2p connection stats -

Code:

Peers
Active:	12 / 202
Fast:	18
High capacity:	45
Integrated:	453
Known:	517

Bandwidth in/out
3 sec:	1.73 / 2.04 KBps
5 min:	2.94 / 2.98 KBps
Total:	3.52 / 3.27 KBps
Used:	43.06 MB / 40.38 MB

Tunnels
Exploratory:	7
Client:	8
Participating:	1
Share ratio:	0.03

Congestion
Job lag:	0
Message delay:	560 ms
Backlog:

2nd edit: Four nodes now.

giv

sr. member

Activity: 254

Merit: 251

For auto-starting the patched client try to delete the ~/.config/autostart/bitcoin.desktop file or open it in any text editor and fix a path to your client. If you will run the vanilla client after that it will rewrite this file again.
I need output of bitcoind/bitcoin-qt to determine why you have only one connection. I have 4-6 peers for today in my wallet. Even if you connect to one node it should give addresses of other nodes to you.
Oh, I see you have a few i2p-peers (Active: 14 / 113). Most probably your ports are closed. In this case I2P works very slow and unstable. You can see the port number at http://127.0.0.1:7657/confignet. Try to open the i2p-port in your firewall or router.

matthewh3

legendary

Activity: 1372

Merit: 1003

Quote from: giv on August 19, 2013, 12:07:19 PM

What do you mean "the wrong version"?

The default bitcoind you suggested I was running when I couldn't connect to any I2p peers. Also all today I've only been connected to one I2p peer?

giv

sr. member

Activity: 254

Merit: 251

What do you mean "the wrong version"?

matthewh3

legendary

Activity: 1372

Merit: 1003

When I set bitcoin-qt to auto-start in settings it starts the wrong version and I get no I2p connections but the I2p settings are there in the wallet like before? I have to start bitcoin-qt from your executable on each boot.

giv

sr. member

Activity: 254

Merit: 251

Usually there are 5-7 i2p-nodes. At least 3 of them are running in mixed mode (working as gateways).

matthewh3

legendary

Activity: 1372

Merit: 1003

Thanks now connected Grin

with five I2p nodes tho it was up to six before. How many I2p nodes are they in total on average and how many nodes acting as gateways?

giv

sr. member

Activity: 254

Merit: 251

ok, i2p is working. Run the patched bitcoin-qt/bitcoind in console and post output (to this thread or to PM).

Quote from: matthewh3 on August 18, 2013, 07:43:53 AM

I try running bitcoind from the command line but it says itys not installed even tho I've excuted bitcoind from your download and bitcoin-qt can connect to the normal network.

Seems like you trying to run default bitcoind. Try to run the patched bitcoind explicitly, smth like /path/to/the/patched/client/bitcond. It should work.

If you run the patched client in mixed mode, most probably it will use only ip-addresses for outgoing connections. That's why. The bitcoin-client has a pool of known addresses. Selecting of address is a pseudorandom process. At now there are hundreds (at first start) and thousands (after syncing with other clients) known ip-addresses and only several I2P-addresses in the pool. By default only 8 outgoing connections are allowed. So probability of selecting an i2p-address is less than 1%.
If you want to run the program in mixed mode, but want to connect with some i2p-nodes (for tests or other purposes) you have to add an i2p-node manually with "-addnode=" option. Also you may publish your i2p-address or PM me and others can connect to your client. In such case you will see his connections as incoming. The client can accept incoming connections even it already has maximum of outgoing connections. If you have a permanent i2p-address and your wallet is running most time I can add your i2p-address to a source code as seed-node in the next releases if you want.

matthewh3

legendary

Activity: 1372

Merit: 1003

Quote from: giv on August 17, 2013, 05:01:51 PM

First of all, check that i2p is working, try to open any i2p-site. Then check that SAM is enabled and running. If it is ok, check the log at ~/.bitcoin/debug.log and check the output of bitcoind/bitcoin-qt. Which mode (i2p-only or mixed) do you use? Do you use any command-line options?

I2p peers

Active:   14 / 113
Fast:   12
High capacity:   73
Integrated:   42
Known:   136

And can login to Susimail. Sam bridges are running and set to start on start up. There's loads of data in - ~/.bitcoin/debug.log.

Code:

CTxMemPool::accept() : accepted 0bc9997a50f94788fe9a410a1bba53f6c59c0a2f65f0db787956384cbb16d48d (poolsz 1704)
received getdata for: tx 0bc9997a50f94788fe9a410a1bba53f6c59c0a2f65f0db787956384cbb16d48d
CTxMemPool::accept() : accepted 46445598b5c66558043736038ee706d01ea093b69adf97bde50c4b36216dea3e (poolsz 1705)
received getdata for: tx 46445598b5c66558043736038ee706d01ea093b69adf97bde50c4b36216dea3e
CTxMemPool::accept() : accepted 8b1788ebd001456a67eb44040bbbf07a8e80dbafe902b6b89c085aed4b5c09e5 (poolsz 1706)
CTxMemPool::accept() : accepted 207c62c0cbd38a29b541a684339de0d073509559f6ce37375dfd037c95e30a3d (poolsz 1707)
Added 1 addresses from 216.228.163.130: 75 tried, 13534 new
CTxMemPool::accept() : accepted f99df6a709e60d22349eb3302ada59228c7b2d6d826bfbec64b41666153cbd38 (poolsz 1708)
CTxMemPool::accept() : accepted eeb80cfa0f35a952359ced22431a86529136025f727137021a98653cf980751a (poolsz 1709)
CTxMemPool::accept() : accepted 61531b804904c0311deb627557f1d4abdf0ebb7c07aec6846c9c4cca3c41821c (poolsz 1710)
CTxMemPool::accept() : accepted 623a36310e06570fa53b3b3b3a9b2ee42476750c05c606202ab4db18fc66fe92 (poolsz 1711)
CTxMemPool::accept() : accepted 413ca1836bbad36d8e9ef27b1079c79e5e94eeebb821d327880cbefbbf673ae7 (poolsz 1712)
CTxMemPool::accept() : accepted 951f037967e0959339415be85aff8b7f73b675d61736f058158493e122f3d0c3 (poolsz 1713)
CTxMemPool::accept() : accepted 6595510b852e0d2de6443f1996401783197b97760ac59e7bb6743277758e4e17 (poolsz 1714)
CTxMemPool::accept() : accepted 093e8be388afa3a039ec622d0f6aece029b5e581eebe91afce71f08d911c225b (poolsz 1715)
received getdata for: tx 093e8be388afa3a039ec622d0f6aece029b5e581eebe91afce71f08d911c225b
received getdata for: tx 093e8be388afa3a039ec622d0f6aece029b5e581eebe91afce71f08d911c225b
received getdata for: tx 093e8be388afa3a039ec622d0f6aece029b5e581eebe91afce71f08d911c225b
received getdata for: tx 093e8be388afa3a039ec622d0f6aece029b5e581eebe91afce71f08d911c225b
received getdata for: tx 093e8be388afa3a039ec622d0f6aece029b5e581eebe91afce71f08d911c225b
received getdata for: tx 093e8be388afa3a039ec622d0f6aece029b5e581eebe91afce71f08d911c225b
received getdata for: tx 093e8be388afa3a039ec622d0f6aece029b5e581eebe91afce71f08d911c225b
Added 1 addresses from 64.53.128.12: 75 tried, 13533 new
CTxMemPool::accept() : accepted bc7219f5453ebffe9b417b8fa2b26a13e0c00edd5bd9f29a4892f635b82570dc (poolsz 1716)
Added 1 addresses from 184.5.141.187: 75 tried, 13533 new
CTxMemPool::accept() : accepted cc0753e9503b285862b54138dc82e752f8b15325690388b631e190aaa4ac2787 (poolsz 1717)
CTxMemPool::accept() : accepted 904b28e4c9adf6f8836a3cbe1575c0c5763f3985095202a69cfbf4064e4029e9 (poolsz 1718)
CTxMemPool::accept() : accepted b229631eef5c2e44b9ecd7a91efc047636fdaf18db5cb67669fdcf32f2bb93c8 (poolsz 1719)
CTxMemPool::accept() : accepted f38937a941d2cf18247720c96243f38da8bf67dde181f364303f88b1d11939a6 (poolsz 1720)
received getdata for: tx f38937a941d2cf18247720c96243f38da8bf67dde181f364303f88b1d11939a6
CTxMemPool::accept() : accepted 467a70695d4898ce999bb0e6b1c5d624c6b4203eabbeb9d798fae5cee89de687 (poolsz 1721)
CTxMemPool::accept() : accepted ff31ba027f16d32477661ce8321cba58a3e9022eeb455b2092733e11f3e766c2 (poolsz 1722)
CTxMemPool::accept() : accepted da6da98d0f0ec2b4f9134e536d61228a5fae8a482be08b212588844c79e47d5a (poolsz 1723)
CTxMemPool::accept() : accepted 0c4cc357bda01e6be8d82691ff5df363f1336fd105db9ac4be2e80f047a7396c (poolsz 1724)
CTxMemPool::accept() : accepted 90d559f9f89838424fcf67108b0e1181f0b2a5c8325d01a4d30f9e7a9a94cccd (poolsz 1725)
received getdata for: tx 90d559f9f89838424fcf67108b0e1181f0b2a5c8325d01a4d30f9e7a9a94cccd
CTxMemPool::accept() : accepted 599f619825bd51e7f1a2097e2999896a5753cf471689a18ae4b61d83cee717d7 (poolsz 1726)
CTxMemPool::accept() : accepted 82ec6eed19482a1672133fbe3c8e3ba121a63b55b486b84184ce3fe907861aec (poolsz 1727)
Added 1 addresses from 216.228.163.130: 75 tried, 13534 new
stored orphan tx c4a23c658858718d8caf6ca06b08fc472a78fb500e7678f112d9aaa87fcf9b54 (mapsz 9973)
CTxMemPool::accept() : accepted 42b497cfad304cc466d2ca79c7299f31f230d603dc21ca6065ecb4e88ffc3356 (poolsz 1728)
CTxMemPool::accept() : accepted c4a23c658858718d8caf6ca06b08fc472a78fb500e7678f112d9aaa87fcf9b54 (poolsz 1729)
   accepted orphan tx c4a23c658858718d8caf6ca06b08fc472a78fb500e7678f112d9aaa87fcf9b54
CTxMemPool::accept() : accepted 5da90cbb8ebbd08c953653fda77165fc8261550839179fc9c2a971f47e35f9d0 (poolsz 1730)
received getdata for: tx c4a23c658858718d8caf6ca06b08fc472a78fb500e7678f112d9aaa87fcf9b54
CTxMemPool::accept() : accepted 35d59e84bdd4749f2431405d90b4e1c5e118136b67d5519bad33cccb5f67e9bf (poolsz 1731)
CTxMemPool::accept() : accepted 34a20bcd9c41ebe18b8785983199b8ff148b84d2eca9f6ef3682d8863fdc0033 (poolsz 1732)
CTxMemPool::accept() : accepted e4eeb421afca38dde3aa3b9a107d248c565aac4c2194e3d91a6ddaf879321791 (poolsz 1733)
CTxMemPool::accept() : accepted a6e2a1159cfdb7ba160a593f060a61aa8a9c814f53359de1a5a8f43edfd080f8 (poolsz 1734)
CTxMemPool::accept() : accepted 3a27f9240f234cda72cb218bc5d056857f29bddf2251e7c8ebc4fe03c3494492 (poolsz 1735)
CTxMemPool::accept() : accepted efcb663564f39f4204a6ac0b9c96ff6551d2f7b3f6e4744dcd6a887c45a36c75 (poolsz 1736)
CTxMemPool::accept() : accepted 30e3273b8c76d4a84fceb90fc13370dbc59e3774ce04bab71b3e303fb0c8dd1d (poolsz 1737)
CTxMemPool::accept() : accepted cdecb31400c21bdbdfe64149a05f665a5534f24c6b27b85246c90accb809f474 (poolsz 1738)

In mixed mode I can onnect to normal peers but not I2p ones. In I2p only mode can't connect to any nodes. I try running bitcoind from the command line but it says itys not installed even tho I've excuted bitcoind from your download and bitcoin-qt can connect to the normal network.

giv

sr. member

Activity: 254

Merit: 251

First of all, check that i2p is working, try to open any i2p-site. Then check that SAM is enabled and running. If it is ok, check the log at ~/.bitcoin/debug.log and check the output of bitcoind/bitcoin-qt. Which mode (i2p-only or mixed) do you use? Do you use any command-line options?

matthewh3

legendary

Activity: 1372

Merit: 1003

I followed your instructions for the (X)ubuntu install and I2p is running but I've had no I2p connections still after running it for over two hours now Huh

Topic: Bitcoin client with I2P patch - page 2. (Read 21461 times)