Hi deluge team,
i just using deluge Vr1.0 for the Pass 48 hours.
i can only say it fail to bypass TMNET DPI (Deep packect inspection)
Believe or not, i was able to download 100kps when using deluge 0.5.8
but since it Fail ( now less 15 Kbps) , i have use your newer version.
It is worse than the old version.
speedtest.net show i have 1003kb/s on downloading from china.
Deluge VS MY ISP (TMNET)
Re: Deluge VS MY ISP (TMNET)
have you tried using a different (higher) port and forced encryption?
Re: Deluge VS MY ISP (TMNET)
Yes, i did try that.
And the result are similar.
and when i some test on http://www.canyouseeme.org/ it show that high port on my ISP network are closed.
Error: I could not see your service on 60.51.30.102 on port (64000)
Reason: Connection timed out
And the result are similar.
and when i some test on http://www.canyouseeme.org/ it show that high port on my ISP network are closed.
Error: I could not see your service on 60.51.30.102 on port (64000)
Reason: Connection timed out
Re: Deluge VS MY ISP (TMNET)
that means your port forwarding is not configured properly. Please forward port 64000 to your modem/router. Check also if your windows firewall is running (if you are on windows).
Re: Deluge VS MY ISP (TMNET)
ok guys,
i manage to forward the port on my modem.
but now i have encounter that my ISP silent blocking the tracker.
i have enable DHT, LSD ...etc.
but with peer information is still missing .
Same torrent.
my friend in Taiwan got 100 + seed
my house only 9 , sometimes it show i have seed but not from tracker.
E.g Seed 9 (0) peer 123(85)
please advise
i manage to forward the port on my modem.
but now i have encounter that my ISP silent blocking the tracker.
i have enable DHT, LSD ...etc.
but with peer information is still missing .
Same torrent.
my friend in Taiwan got 100 + seed
my house only 9 , sometimes it show i have seed but not from tracker.
E.g Seed 9 (0) peer 123(85)
please advise
Re: Deluge VS MY ISP (TMNET)
are you sure the tracker's not down?
try a different tracker for that torrent or a different torrent with a different tracker
try a different tracker for that torrent or a different torrent with a different tracker