-
DNS name resolution from weave is failing from docker host in new version of docker `v1.10.1` and weave `1.4.4`.
Probably related to these two issues https://github.com/docker/docker/issues/20026 & h…
-
Hi EthereumJ team,
I have 3 servers running and connected. All servers have port 30303, but when I check peers on each server I see strange info. On some servers I see duplicated remote server peer wi…
-
3 node cluster - 2 on gce, one on a vagrant VM on my laptop.
the two on gce were created with the scope/experimental/demo/gce.sh script - go1.4, docker 1.7, master build of weave (d79ac3c12)
the one…
-
Here's weave report:
```
{
"Version": "1.2.0",
"Router": {
"Protocol": "weave",
"ProtocolMinVersion": 1,
"ProtocolMaxVersion": 2,
"Encryption": false,
…
-
Originally reported on Google Code with ID 302
```
Currently, if you add multiple discoveries, bitcoinj just adds addresses of the first.
Any second or third discoveries are ignored.
I need multiple…
-
Originally reported on Google Code with ID 17
```
There is no network timeout parameter when trying to connect to peers.
I'm not sure what the java default is but its long. Over a minute as far as I …
-
```
Currently, if you add multiple discoveries, bitcoinj just adds addresses of the
first. Any second or third discoveries are ignored.
I need multiple discoveries for connecting a trusted peer AND …
-
```
There is no network timeout parameter when trying to connect to peers.
I'm not sure what the java default is but its long. Over a minute as far as I
can tell.
Not an issue when you are only con…
-
```
I'd like to be able to completely purge the list of peers and supply a new
PeerDiscovery. All peers not discovered by the new discovery should be
disconnected.
Currently, I need to tear down Pe…
-
```
There is no network timeout parameter when trying to connect to peers.
I'm not sure what the java default is but its long. Over a minute as far as I
can tell.
Not an issue when you are only con…