You need to identify it though, because if it is transmission, then it's working fine.
Ok.
Could you help me find a way to identify it, because it is most likely transmission.
Problem is,
while transmission is actively trying to download,
it doesn't actually download,
I chose a torrent that has a lot of seeders so that it can work seamlessly,
and all other traffic to internet gets blocked by the openvpn client,
i.e. I cannot open a random website,
it seems as if the openvpn client,
since it blocks P2P traffic,
suspends the connection until i pause transmission,
then the internet is restored.
thank you
Edit
For example I cannot even post here till I pause transmission
however,
if I stop openvpn,
and start the transmission,
the torrent downloads within seconds
I goofed up.
Yesterday, while I was trying to get transmission to work with user 'transmission', while trying everything I chown -R transmission:transmission /overlay so, many things got the user '224' which I allowed to bypass openvpn 
so it could be anything that is using that port
Sorry for the confusion, I'll do a fresh install tomorrow and report back!
Thank you kind Sir
1 Like
netstat -anp | grep 51820
1 Like
I did a fresh install.
The good news is while transmission is trying to download, the rest of normal traffic isn't getting choked.
Some progress, I guess.
Bad news is transmission still isn't downloading.
tcpdump - https://ufile.io/dc6eflcs
Edit
root@OpenWrt:~# netstat -anp | grep 58766
udp 0 0 0.0.0.0:58766 0.0.0.0:* 2234/openvpn
Edit
tcpdump - https://ufile.io/icpjvg45
root@OpenWrt:~# netstat -anp | grep 55284
udp 0 0 0.0.0.0:55284 0.0.0.0:* 4495/openvpn
Thank you
But this is not the port that transmission is using. You are matching the port of OpenVPN.
doesn't seem to be showing anything
tcpdump - https://ufile.io/ue6vq8o1
root@OpenWrt:~# netstat -anp | grep 4569
root@OpenWrt:~# netstat -anp | grep 4569
root@OpenWrt:~# netstat -anp | grep 4569
root@OpenWrt:~#
What is the output of netstat -anp | grep transm ?
tcpdump - https://ufile.io/b85hkunp
root@OpenWrt:~# netstat -anp | grep 55284
udp 0 0 0.0.0.0:55284 0.0.0.0:* 4495/openvpn
root@OpenWrt:~# netstat -anp | grep 4569
root@OpenWrt:~# netstat -anp | grep 4569
root@OpenWrt:~# netstat -anp | grep 4569
root@OpenWrt:~# netstat -anp | grep transm
tcp 0 0 0.0.0.0:51413 0.0.0.0:* LISTEN 3171/transmission-d
tcp 0 0 0.0.0.0:9091 0.0.0.0:* LISTEN 3171/transmission-d
tcp 0 0 192.168.1.1:9091 192.168.1.113:55126 ESTABLISHED 3171/transmission-d
tcp 0 0 :::51413 :::* LISTEN 3171/transmission-d
udp 0 0 0.0.0.0:48039 0.0.0.0:* 3171/transmission-d
udp 0 0 0.0.0.0:51413 0.0.0.0:* 3171/transmission-d
udp 0 0 0.0.0.0:44671 0.0.0.0:* 3171/transmission-d
udp 0 0 :::39075 :::* 3171/transmission-d
unix 3 [ ] STREAM CONNECTED 4754 3171/transmission-d
unix 3 [ ] STREAM CONNECTED 4755 3171/transmission-d
root@OpenWrt:~#
Thanks.
Edit
The user 'transmission' with uid '224'
gets trimmed to 'transm'
do you feel maybe that's why specifying the uid
in the config below,
is not working
config rule
option lookup '100'
option uidrange '224'
config route
option metric '200'
option table '100'
option gateway '192.168.0.1'
option interface 'wan'
option target '0.0.0.0'
option netmask '0.0.0.0'
Looking at the posted configuration, the correct logical interface name should be wwan and not wan.
This is (most likely) why routing table 100 is empty.
This doesn't look right either (the uidrange selector is missing).
Comment out the ip rule/route in /etc/config/network and create them manually
ip route add default via 192.168.0.1 table 100
ip rule add uidrange 224-224 table 100 prio 1
If it starts working as expected, find the correct uci syntax.
If it still doesn't work, I would start thinking about the opposite approach - disable the default route via vpn for the router itself and create an ip rule/route for the LAN clients to use the vpn service.
2 Likes
This worked, Thank you, however there was a funny byproduct, transmission upstream webui (http://192.168.1.1:9091/transmission/web/) does not load, downloads continue in the background without transmission upstream webui loading.
Once I change the target to 0.0.0.0/32, transmission upstream webui loads but downloads stop.
I'm sure it is some other related issue like transmission whitelist or something but I don't know why, if you could please shed some light on what could possibly be the cause, thank you
Manually added as below
config route
option table '100'
option interface 'wwan'
option gateway '192.168.0.1'
option target '0.0.0.0/0'
config rule
option lookup '100'
option uidrange '224-224'
option priority '1'
Try adding this:
config route
option table '100'
option interface 'lan'
option target '192.168.1.0'
option netmask '255.255.255.0'
Also the trasmission is using port 51413.
2 Likes
Sorry for misleading you, I edited the previous post, it is transmission upstream webui (http://192.168.1.1:9091/transmission/web/) that is not working, I'm not trying to reach transmission webui remotely via 51413 and I didn't mean 'luci-app-transmission'
Thank you
Edit
Also, when I manually create a route, via luci
a subnet is required. option target '0.0.0.0/0'
I just don't quite understand while everything works as expected, why the transmission upstream webui (http://192.168.1.1:9091/transmission/web/) does not
config route
option table '100'
option interface 'wwan'
option gateway '192.168.0.1'
option target '0.0.0.0/0'
config rule
option lookup '100'
option uidrange '224-224'
option priority '1'
I tried
config route
option table '100'
option gateway '192.168.0.1'
option interface 'wwan'
option target '0.0.0.0/0'
config rule
option lookup '100'
option uidrange '224-224'
option priority '1'
config route
option interface 'lan'
option table '100'
option target '192.168.1.0/32'
Didn't work to load transmission upstream webui (http://192.168.1.1:9091/transmission/web/)
Edit
Just to be clear, it partially loads, i.e transmission upstream webui html loads, the torrent information and resume which has user 'transmission' (
chown -R transmission:transmission /overlay/samba/downloads/temp
chown -R transmission:transmission /overlay/samba/trans/
chown -R transmission:transmission /overlay/samba/trans/resume
chown -R transmission:transmission /overlay/samba/trans/torrents
) does not load
So, I guess that needs to be routed back to local network, like you suggested, but it does not happen
I understood that.I mentioned port 51413 because in the previous netstats you kept trying to find the port transmission is using to connect to other peers.
The netmask is wrong, should be /24.
2 Likes
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.