search

SynoCommunity / spksrc

Cross compilation framework to create native packages for the Synology's NAS
https://synocommunity.com
Other
3.04k stars 1.24k forks source link

Can't connect ipv6 tracker #707

Closed Hero2006 closed 7 years ago

Hero2006 commented 11 years ago

I have Nas Synogy DS713+ DSM 4.3-3810 and using Transmission (get from http://packages.synocommunity.com) 2.82-5. My problem that transmission can't connect wia http ipv6 tracker address. send1 Ipv6 i get from router by 6in4 (Hurricane Electric Free IPv6 Tunnel Broker). Here is my configuration:

ifconfig bond0 Link encap:Ethernet HWaddr 00:11:32:1B:79:81
inet addr:192.168.1.124 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: 2001:470:1f1b:22:211:32ff:fe1b:7981/64 Scope:Global inet6 addr: fe80::211:32ff:fe1b:7981/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:12127862 errors:0 dropped:0 overruns:0 frame:0 TX packets:14282407 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9974862995 (9.2 GiB) TX bytes:15005807111 (13.9 GiB) eth0 Link encap:Ethernet HWaddr 00:11:32:1B:79:81
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:12122226 errors:0 dropped:0 overruns:0 frame:0 TX packets:14282407 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9974433649 (9.2 GiB) TX bytes:15005807111 (13.9 GiB) Interrupt:16 Memory:40300000-40320000 eth1 Link encap:Ethernet HWaddr 00:11:32:1B:79:81
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:5636 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:429346 (419.2 KiB) TX bytes:0 (0.0 B) Interrupt:17 Memory:40200000-40220000 lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4556 errors:0 dropped:0 overruns:0 frame:0 TX packets:4556 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:423150 (413.2 KiB) TX bytes:423150 (413.2 KiB)

ping ipv6.google.com PING ipv6.google.com (2607:f8b0:4008:803::1013): 56 data bytes 64 bytes from 2607:f8b0:4008:803::1013: seq=0 ttl=51 time=334.637 ms 64 bytes from 2607:f8b0:4008:803::1013: seq=1 ttl=51 time=337.000 ms 64 bytes from 2607:f8b0:4008:803::1013: seq=2 ttl=51 time=334.446 ms 64 bytes from 2607:f8b0:4008:803::1013: seq=3 ttl=51 time=334.558 ms 64 bytes from 2607:f8b0:4008:803::1013: seq=4 ttl=51 time=334.928 ms

ping -4 ipv6.google.com PING www.google.com (212.122.6.234): 56 data bytes 64 bytes from 212.122.6.234: seq=0 ttl=61 time=3.659 ms 64 bytes from 212.122.6.234: seq=1 ttl=61 time=3.480 ms 64 bytes from 212.122.6.234: seq=2 ttl=61 time=4.298 ms 64 bytes from 212.122.6.234: seq=3 ttl=61 time=3.665 ms 64 bytes from 212.122.6.234: seq=4 ttl=61 time=3.427 ms

ping bt.nnm-club.info PING bt.nnm-club.info (37.1.207.72): 56 data bytes 64 bytes from 37.1.207.72: seq=0 ttl=55 time=179.274 ms 64 bytes from 37.1.207.72: seq=1 ttl=55 time=178.971 ms 64 bytes from 37.1.207.72: seq=2 ttl=55 time=179.614 ms 64 bytes from 37.1.207.72: seq=3 ttl=55 time=178.974 ms

ping bt.ipv6.nnm-club.info PING bt.ipv6.nnm-club.info (2001:470:25:482::2): 56 data bytes 64 bytes from 2001:470:25:482::2: seq=0 ttl=57 time=238.668 ms 64 bytes from 2001:470:25:482::2: seq=1 ttl=57 time=243.632 ms 64 bytes from 2001:470:25:482::2: seq=2 ttl=57 time=239.895 ms 64 bytes from 2001:470:25:482::2: seq=3 ttl=57 time=239.606 ms

telnet bt.nnm-club.info 2710 sdf sHTTP/1.0 302 Found

Location: http://nnm-club.me/forum/

telnet bt.ipv6.nnm-club.info 2710 df sHTTP/1.0 302 Found

Location: http://nnm-club.me/forum/

ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP800> mtu 1500 qdisc pfifo_fast master bond0 qlen 1000 link/ether 00:11:32:1b:79:81 brd ff:ff:ff:ff:ff:ff 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP800> mtu 1500 qdisc pfifo_fast master bond0 qlen 1000 link/ether 00:11:32:1b:79:81 brd ff:ff:ff:ff:ff:ff 4: bond0: <BROADCAST,MULTICAST,UP,LOWER_UP420> mtu 1500 qdisc noqueue link/ether 00:11:32:1b:79:81 brd ff:ff:ff:ff:ff:ff inet 192.168.1.124/24 brd 192.168.1.255 scope global bond0 inet6 2001:470:1f1b:22:211:32ff:fe1b:7981/64 scope global dynamic valid_lft 86035sec preferred_lft 14035sec inet6 fe80::211:32ff:fe1b:7981/64 scope link valid_lft forever preferred_lft forever

transmission setting file (settings.json) .. "bind-address-ipv6": "::"

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Diaoul commented 11 years ago

Does it work with Download Station?

Hero2006 commented 11 years ago

dm Yes it is. Like uTorrent on PC utor My network: Router(+Wi-Fi, OpenWRT 12.9) Gigab. Switch (Not managed) PC | NAS (Link aggregation: Network Fault Tolerance only)

Diaoul commented 11 years ago

I don't know much about IPV6, maybe there are some configure options to set.

Hero2006 commented 11 years ago

Could be. But at the moment I'm at a dead end = ( The only option in the Transmission settings if the "bind-address-ipv6", but I have it set up correctly.

Diaoul commented 11 years ago

I mean compile time options at configure step: https://github.com/SynoCommunity/spksrc/blob/develop/cross/transmission/Makefile#L15

Hero2006 commented 11 years ago

Maybe that's the case. I'll try a little later.

moneytoo commented 11 years ago

Generally IPv6 in Transmission works. I tried downloading from Ubuntu tracker using IPv6 only. I'm using DHCPv6 with prefix delegation on my router though...

transmission

Hero2006 commented 11 years ago

radvd ubuntu I know that transmission realy works with ipv6. But i don't know how to solve my problem =( Tried download ubuntu. All the same. Ping works (from nas and pc), dm works, uTorrent works (pc), telnet to traker port works (from nas and pc), but transmitission don't. I use only radvd now. Later try use wide-dhcp6 on my router. Maybe this will help.

Diaoul commented 11 years ago

@moneytoo: if you have IPV6 can you try to see what's the problem with transmission? Maybe a compile-time option to enable ipv6? Maybe in a dependency?

moneytoo commented 11 years ago

@Diaoul I'm not sure what to check right now as I tried the current release on Synology and it worked from the start.

Diaoul commented 11 years ago

Right, sorry I misread.

Hero2006 commented 11 years ago

Upd: I tried reinstall Transmission - it did not solve the problem. Now I start backup data and will try reinstall DSM and Transmisiion on clean system. If that don't help, with a probability of 90%, my problem is a network.

Diaoul commented 11 years ago

I don't think it will solve your issue. Don't do that.

Hero2006 commented 11 years ago

Yes, it didn't help. Now I try to find a problem with my network settings. Upd: About compile time options. I read How to build Transmission wiki and were no any options about ipv6. My problem is very strange, i tried this configuration:

  1. Create tunnel Anon to gogo6 tunnel
  2. Disable lan ipv6 (to clean from ipv6 of my router) and reboot. disipv6
  3. ifconfig after reboot: ipv6
  4. And all the same =( Now I preparing to create my own Transmission package and try it.
  5. ... and it don't help, againt =(
moneytoo commented 11 years ago

Actually the way I verified IPv6 working with Transmission was to disable IPv4 in Transmission setting. Maybe you could try that as well, maybe it just preferred faster connections which was IPv4. I did that by setting bind-address-ipv4 to localhost.

Hero2006 commented 11 years ago

I'll try to check. It seems to me that for some reason Transmission in my configuration does not see the presence of ipv6 network, and at the moment does not even really matter how I configured ipv6. My configuration DSM now:

  1. In the settings of the network (lan) I am completely turned off ipv6.
  2. Enabled a tunnel to the service gogo6
  3. Checked the work with my tracker (and the Ubuntu tracker too) using DM Synology. It works perfectly, both addresses are given the status of Success. In the list of peers is ipv6-address. Everything work well. Transmission does not see the presence of ipv6 at all. Upd: I tried to disable ipv4 in the file settings.json Transmission stopped working with trackers at all. No matter what was the address of the tracker, the status of all was "Could not connect .."