Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#5787 closed Bug (invalid)

bind-address-ipv6 not keeping it settings

Reported by: ranpha Owned by:
Priority: Normal Milestone: None Set
Component: Daemon Version: 2.84
Severity: Normal Keywords: ipv6
Cc:

Description

From https://forum.transmissionbt.com/viewtopic.php?f=2&t=16432

I have a problem with bind-address-ipv6 not keeping its setting when the daemon is started. Every time I edit the said option in settings.json while the daemon is off, from the default "::" to something like "[2a00:dd80:fb80::200]" (example only), when I start the daemon again, the 'bind-address-ipv6' value will revert back to "::".

transmission version is the latest one (2.84), libevent is 2.0.21 and OS is CentOS 6.5 64-bit.

Below is the output of "transmission-remote -si"

    VERSION
      Daemon version: 2.84 (14307)
      RPC version: 15
      RPC minimum version: 1

    CONFIG
      Configuration directory: /home/<username-redacted>/.config/transmission-daemon
      Download directory: /home/<username-redacted>/finished
      Listenport: 60001
      Portforwarding enabled: Yes
      uTP enabled: Yes
      Distributed hash table enabled: Yes
      Local peer discovery enabled: No
      Peer exchange allowed: Yes
      Encryption: preferred
      Maximum memory cache size: 32.00 MiB

    LIMITS
      Peer limit: 500
      Default seed ratio limit: 10.0
      Upload speed limit: 5.12 MB/s (Enabled limit: 5.12 MB/s; Disabled turtle limit: 50 kB/s)
      Download speed limit: Unlimited (Disabled limit: 5.12 MB/s; Disabled turtle limit: 50 kB/s)

    MISC
      Autostart added torrents: Yes
      Delete automatically added torrents: No

Change History (6)

comment:1 Changed 7 years ago by x190

Please check to see if your start-up script is setting this value. Also, despite what Transmission reports, check for other settings.json files. Make sure you are editing the settings file correctly. https://trac.transmissionbt.com/wiki/EditConfigFiles Other IPv6 reports refer to trackers, which you should peruse vis-à-vis your use case.

comment:2 follow-up: Changed 7 years ago by ranpha

I do not have any start-up scripts, after all all I do is 'su <username-redacted> -c "/path/to/transmission-daemon" to start the daemon. I compile and install everything myself, so I know where the files goes to.

#find  / -type f -name settings.json
find: File system loop detected; `/var/named/chroot/var/named' is part of the same file system loop as `/var/named'.
/home/<username-redacted>/.config/transmission-daemon/settings.json

Plus I do edit the settings.json file correctly. If I want to configure the daemon to use 2a00:dd80:fb80::200 IPv6 address for IPv6 traffic, then the setting should be like below right?

"bind-address-ipv6": "[2a00:dd80:fb80::200]",

comment:3 in reply to: ↑ 2 Changed 7 years ago by x190

Replying to ranpha:

Plus I do edit the settings.json file correctly. If I want to configure the daemon to use 2a00:dd80:fb80::200 IPv6 address for IPv6 traffic, then the setting should be like below right?

"bind-address-ipv6": "[2a00:dd80:fb80::200]",

Please edit your settings.json again, after stopping the daemon, without the square brackets.

https://trac.transmissionbt.com/wiki/EditConfigFiles#Peers

Last edited 7 years ago by x190 (previous) (diff)

comment:4 Changed 7 years ago by ranpha

Without the brackets, the setting now works, but I will not be able to remote load any .torrent files at all.

https://miku.hatsune.my/cf/di/IQX3/transmission-loading-torrent-error-message.jpg

With this, I can only add torrents via magnet links.

comment:5 Changed 7 years ago by x190

  • Resolution set to invalid
  • Status changed from new to closed

comment:6 Changed 7 years ago by x190

Please use the forum for support issues.

Note: See TracTickets for help on using tickets.