Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Need some help with double wan setup and rutorrent ports… can't get green led

    Scheduled Pinned Locked Moved NAT
    1 Posts 1 Posters 435 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      sladinki007
      last edited by

      HI all,

      First of all this worked on an ubuntu 14.04 kvm setup
      but i wanted to upgrade to 16.04 and now it doesn't work any more

      what i did was make a backup of the 14.04 kvm setup

      upgraded to ubuntu 16.04
      when i tried to open the kvm it didn't work
      so i installed from scratch again
      imported the backup
      but can't get a greed led in Rutorrent whatever i try :(

      here is the setup

      Wan 1: fibre 100/20
      wan 2: fibre 40/5
      Lan

      as mentioned this is running into a KVM on ubuntu 16.04 on a dual processor server with 4 nics
      the ruttorent is running in a docker

      this is /etc/network/interfaces

      
      # source /etc/network/interfaces.d/*
      
      # The loopback network interface
      auto lo
      iface lo inet loopback
      
      # The primary network interface
      
      auto eno4
      #iface eno4 inet dhcp
      iface eno4 inet static
      address 192.168.1.110
      netmask 255.255.255.0
      gateway 192.168.1.1
      dns-nameservers 8.8.8.8 8.8.4.4
      
      #pfsense nics
      
      auto eno1
      iface eno1 inet manual
      #iface eno1 inet static
      #address 192.168.10.10
      #netmask 255.255.255.0
      #gateway 192.168.10.1
      #dns-nameservers 8.8.8.8 8.8.4.4
      
      auto eno2
      iface eno2 inet manual
      #iface eno2 inet static
      #address 192.168.20.10
      #netmask 255.255.255.0
      #gateway 192.168.20.1
      #dns-nameservers 8.8.8.8 8.8.4.4
      
      auto eno3
      iface eno3 inet manual
      #iface eno3 inet static
      #address 192.168.1.1
      #netmask 255.255.255.0
      #gateway 192.168.1.1
      #dns-nameservers 8.8.8.8 8.8.4.4
      
      #pfsense bridge
      
      auto br10
      #iface br10 inet manual
      iface br10 inet static
             address 192.168.10.10
      #       network 192.168.10.0
             netmask 255.255.255.0
      #       broadcast 192.168.10.255
      #       gateway 192.168.10.1
             dns-nameservers 8.8.8.8 208.67.222.222
              bridge_ports eno1
              bridge_stp off
              bridge_fd 0
              bridge_maxwait 0
      
      auto br20
      #iface br20 inet manual
      iface br20 inet static
             address 192.168.20.10
      #       network 192.168.20.0
             netmask 255.255.255.0
      #       broadcast 192.168.20.255
      #       gateway 192.168.20.1
             dns-nameservers 8.8.4.4 208.67.220.220
              bridge_ports eno2
              bridge_stp off
              bridge_fd 0
              bridge_maxwait 0
      
      auto br30
      iface br30 inet manual
      #iface br30 inet static
      #       address 192.168.1.1
      #        network 192.168.1.0
      #       netmask 255.255.255.0
      #        broadcast 192.168.1.255
      #       gateway 192.168.1.1
      #       dns-nameservers 8.8.4.4 8.8.8.8 208.67.220.220
              bridge_ports eno3
              bridge_stp off
              bridge_fd 0
              bridge_maxwait 0
      
      

      the docker is running on it's own bridge

      brctl show

      
      bridge name     bridge id               STP enabled     interfaces
      br10            8000.3c4a92b25c1c       no              eno1
                                                              vnet1
      br20            8000.3c4a92b25c1d       no              eno2
                                                              vnet2
      br30            8000.3c4a92b25c1e       no              eno3
                                                              vnet0
      docker0         8000.0242864e8f10       no              veth1cd2731
                                                              veth21dc85b
                                                              veth2d938bb
                                                              veth528c62f
                                                              veth64bd613
                                                              vethb254583
                                                              vethc1c87a0
                                                              vethe494834
                                                              vethe5eea20
      virbr0          8000.000000000000       yes
      
      

      route

      Kernel IP routing table
      Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
      default         192.168.1.1     0.0.0.0         UG    0      0        0 eno4
      link-local      *               255.255.0.0     U     1000   0        0 br10
      172.17.0.0      *               255.255.0.0     U     0      0        0 docker0
      192.168.1.0     *               255.255.255.0   U     0      0        0 eno4
      192.168.10.0    *               255.255.255.0   U     0      0        0 br10
      192.168.20.0    *               255.255.255.0   U     0      0        0 br20
      192.168.122.0   *               255.255.255.0   U     0      0        0 virbr0
      
      

      the ports that are special are portforwarded from the Fibremodem  to the IP of the lan used by pfsense

      it works great for Plex media server which is also running in a docker
      but this ruttorrent i can't get to work with open ports

      i made  following NAT rules

      WAN1_Txx
      TCP/UDP
      *
      *
      WAN1  address
      32700 - 32710
      192.168.1.1xx
      32700 - 32710
      Torrent_Proliant_Txx

      WAN2_
      TCP/UDP
      *
      *
      WAN2 Txx address
      32700 - 32710
      192.168.1.1xx
      32700 - 32710
      Torrent_Proliant_Txx

      Which resulted in the automated firewall rules

      and like that it always worked on 14.04

      now i have tried a lot of stuff  as adding outgoing rules / floating rules
      traffic shaper to see if i could force it over one lan to see if either of them worked
      but all to no use

      so i am forgetting something … just no clue what for the moment and it is driving me nuts

      i can not bridge the modems to rule out the double nat as we have no access to the special info needed to logon to their networks
      and it works fine for PLEX

      and id you look at the firewall rules you see something gets logged

      1 /48 KiB
      IPv4 TCP/UDP
      *
      *
      192.168.1.1xx
      32700 - 32710
      *
      none
       
      NAT Torrent_Proliant_Txx

      so i think there is no problem with the port forwards on the modems
      i am sure rutorrent docker is listening on these ports

      so now i am at my wits end and come ask help from the experts

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.