Arch Linux

nmiculinic

Member

Registered: 2015-12-25

Posts: 63

[Solved] P2P connectivity issues with transmission/Mist

I'm experiencing peer to peer network connectivity problems while running transmission or Mist (Etherium client) as my user.  On transmission-gtk it's stuck on "Downloading metadata from 0 peers (0% done)" while on Mist it's stuck on Looking for peers.

However, I also have transmission daemon running as special transmission user on port 9091 running perfectly happy. No connectivity issues, torrents are downloaded just fine, etc. Also, transmission-gtk used to work previously and then stopped working one day (I cannot connect it to something specific though). Overall my internet connection is working all right.

How can I further debug this problem?

ifconfig: (br-.. are I guess docker created stuff? not sure where veth got created too.)

br-11a47cc183b0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.20.0.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 02:42:0a:43:8f:cb  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-5bb74a495692: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.19.0.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 02:42:e9:cd:d4:a5  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-8ba1762fb133: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.21.0.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 02:42:e3:44:58:ae  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-8fd3cee01eeb: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 02:42:99:24:bf:e7  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 0.0.0.0
        inet6 fe80::42:24ff:fe05:1bf6  prefixlen 64  scopeid 0x20<link>
        ether 02:42:24:05:1b:f6  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 162  bytes 26072 (25.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp3s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 4c:cc:6a:63:82:2e  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 3887  bytes 988425 (965.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3887  bytes 988425 (965.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth2bc99c8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::6076:2cff:feb5:1835  prefixlen 64  scopeid 0x20<link>
        ether 62:76:2c:b5:18:35  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 199  bytes 29438 (28.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.12  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::c6d1:1277:b48d:7603  prefixlen 64  scopeid 0x20<link>
        ether 18:a6:f7:f1:79:7a  txqueuelen 1000  (Ethernet)
        RX packets 482312  bytes 556946003 (531.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 261261  bytes 113540956 (108.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Last edited by nmiculinic (2017-08-29 08:02:55)

Docbroke

Member

From: India

Registered: 2015-06-13

Posts: 1,433

Re: [Solved] P2P connectivity issues with transmission/Mist

If transmission-daemon is working fine, this may be issue with transmission-gtk configuration rather than network connectivity. You may need to add tracker-urls. I have no idea about mist.

---

Arch is home!
https://github.com/Docbroke

nmiculinic

Member

Registered: 2015-12-25

Posts: 63

Re: [Solved] P2P connectivity issues with transmission/Mist

Thank you, I fiddled with transmission setting and I turned on Port randomization and disabled blacklists, that solved the problem. After further exploring Mist was just sloooow to start up.