Transmission and Routing

Discussion in 'Tomato Firmware' started by scoobynz, Feb 3, 2013.

  1. scoobynz

    scoobynz Networkin' Nut Member


    I am running Shibby Tomato Firmware 1.28.0000 MIPSR2-104 K26 USB AIO, on an E4200 (goes brilliantly!).

    I have a VPN client enabled and route traffic with defined routing rules. This ensures that only certain IP’s use the VPN and the rest of the traffic goes through the WAN. This is all working well.

    I have now implemented the built in Transmission and have this working except for one issue. When I start transmission (through the GUI) something is happening whereby all the predefined traffic routes are being overridden/written and all traffic on the network ends up being routed through the VPN.

    I have had a bit of a dig around but cannot see why this would happen. I have disabled the transmission port forwarding (UPnP) but this didn’t help.

    Does anyone, with any more knowledge of the inner workings of Transmission start up procedure, know why my routing would be altered upon launch of Transmission and how I can stop this behaviour.

    Many thanks,
  2. scoobynz

    scoobynz Networkin' Nut Member

    Answering my own thread. . . . I saw this link where Shibby discusses putting the transmission start-up command into the admin-scripts-firewall

    I figured/guessed/extrapolated that this is what's happening with the out of the box GUI approach and hence why it is interfering with the routing/iptables etc?????

    Anyhow, I installed the transmission Entware package on a USB stick and use the automount script section to start transmission upon USB mounting. To make my settings.json survive reboot I had to save a copy somewhere on the router that does not get wiped at reboot and copy it across as part of the automount script.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice