1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Transmission can't bind other IP than 192.168.1.1 or 192.169.2.1

Discussion in 'Tomato Firmware' started by sintei, May 12, 2017.

  1. sintei

    sintei Network Newbie Member

    Hello,

    Running latest shibby.
    In the built in transmission, in custom configuration I have these values:
    "rpc-bind-address": "192.168.2.1",
    "bind-address-ipv4": "192.168.2.1",

    I thought that I could bind transmission to any IP that is available, example: 192.168.2.5
    But if I change the values, I cant access transmission.

    But if I go and change values to 192.168.1.1, it works.

    I have 2 VLANs, hence the **1.1 and **2.1
     
  2. sintei

    sintei Network Newbie Member

    Log file says:
    May 13 10:12:09 unknown daemon info transmission-daemon[4495]: RPC Server Adding address to whitelist: LOCALURL (rpc-server.c:903)
    May 13 10:12:09 unknown daemon info transmission-daemon[4495]: RPC Server Serving RPC and Web requests on LOCALURL (rpc-server.c:1110)
    May 13 10:12:09 unknown daemon debug transmission-daemon[4495]: RPC Server Unable to bind to MYURL , retrying in 5 seconds (rpc-server.c:768)

    I think its due to it being built in to the router and not added via a package (optware etc).
     
  3. waeking

    waeking Networkin' Nut Member

    you have to create something like this in you init script
    ifconfig br0:1 192.168.2.5 netmask 255.255.255.0 up
     

Share This Page