Posts:
17
Registered:
11/03/09
|
|
|
|
Ip-filter selectable per torrent, not only for all the torrents.
Posted:
Nov 2, 2009 11:46 PM
|
|
|
|
In the present IP-filter applies for all torrents.
Some torrents may need it really but the others may not.
For ex., there are 'external' and 'internal' torrents according to connection and tracker.
Now we have to run 2 vuzes separately or vuze&some other bt-client.
One is ip-filtered, the other is not.
This is not useful.
So would be great to choose if ip-filter is 'on' or 'off' per torrent.
And may be ability to select the personal filter-file per torrent, if possible of course.
This feature is not present in any bt-client and so Vuze would be the first and the one!
Thanx.
|
|
|
Posts:
570
Registered:
11/13/07
|
|
|
|
Re: Ip-filter choosable per torrent
Posted:
Nov 3, 2009 2:13 AM
in response to: Gambit
|
|
|
there are 'external' and 'internal' torrents
What are external / internal torrents? |
|
|
Posts:
17
Registered:
11/03/09
|
|
|
|
Re: Ip-filter choosable per torrent
Posted:
Nov 3, 2009 3:06 AM
in response to: cyb2063
|
|
|
|
Obviously internal for internal IP's, external for external IP's, regarding to the provider's LAN or IX.
The offer was about IP filter. Many users dream about such a feature, still launching 2 clients.
|
|
|
Posts:
33
Registered:
04/02/09
|
|
|
|
Re: Ip-filter choosable per torrent
Posted:
Nov 5, 2009 11:03 AM
in response to: Gambit
|
|
|
|
If it's on the LAN, why would "internal" torrents have a problem with the IPfilter in the first place? Are you banning your own network?
|
|
|
Posts:
17
Registered:
11/03/09
|
|
|
|
Re: Ip-filter choosable per torrent
Posted:
Nov 5, 2009 8:21 PM
in response to: np1
|
|
|
|
"Internal" torrents need using ip-filter.
"External" basically do not need a filter, although why not?
Today this task is being solved running 2 BT-clients - 2 Vuzes or Vuze&uTorrent or 2 uTorrent (in the most cases)
Preferable is to have the ability to simply point if ip-filter is to be enabled or not, using the only one client.
p.s.
I understand that the modern implementation is using filter as a gate - all the torrents are standing after the ip-filter.
If a peer has run through this gate there's no need to think of the torrent he is communicating with.
Choose-able filter is hardly to make (maybe) as this "gate" will be needed for each torrent. So a peer may run through one torrents' "gate" but not through the other.
But I think it's real to make as Vuze still has a lot of per-torrent options and capabilities.
Why not be another great feature?
|
|
|
Posts:
570
Registered:
11/13/07
|
|
|
|
Re: Ip-filter choosable per torrent
Posted:
Nov 5, 2009 11:53 PM
in response to: Gambit
|
|
|
"Internal" torrents need using ip-filter.
"External" basically do not need a filter
? |
|
|
Posts:
17
Registered:
11/03/09
|
|
|
|
Re: Ip-filter choosable per torrent
Posted:
Nov 6, 2009 5:46 AM
in response to: cyb2063
|
|
|
|
What is misunderstanding, really?
Internal trackers accept only some ip's, external trackers do not differ.
There's the trackers/forums where you can't even enter if your ip is not within the white range.
With internal torrent a user blocks all the ip's out of allowed range, with external torrent - does not.
But he can work with both types of torrents simultaneously or, let's say, download/seed only internal torrents
with high speed and absolutely for free, and browse web simultaneously without any affect of downloading torrents.
Besides, such tariffs generally offer the limit for external download amount of GB, but internal traffic is completely
free (unlimited). Therefor such a user serfs web, downloads some torrents from Internet, but the main downloading activity
runs through the internal provider/region traffic. Is it clear-cut?
In fact, I'm saying not about internal/external trackers/torrents but adjustable ip-filter per torrent.
What is it for - people will find the usage, believe me.
Would be great to hear an opinion of the developers.
|
|
|
Posts:
33
Registered:
04/02/09
|
|
|
|
Re: Ip-filter choosable per torrent
Posted:
Nov 7, 2009 6:30 AM
in response to: Gambit
|
|
|
|
Eh... Ok, so there's a tracker INSIDE your LAN that takes care of LAN torrent files for your network and then there's the usual trackers outside the LAN (the normal ones).
So you want to block outside traffic to your private LAN torrents but not for torrents coming from outside trackers? If that's the case, how could someone get a hold of YOUR internal .torrent file and actually manage to download from your private LAN tracker? I'd expect you'd have setup your LAN tracker on your private server, which in turn would only be configured to communicate inside your LAN. I fail to see where the problem is in this scenario. Also, if you really must have your LAN tracker communicate with the internet, you could have setup a private tracker and create all your torrents using the private flag. Vuze automatically disables DHT and other peer exchange protocols when a .torrent has the private flag so there's no way your torrent would somehow get distributed outside your LAN.
Unless your "internal"/"external" distinction isn't really that and all you're saying is that some trackers have specific IPs allowed and others don't, but if that's the case
the guy who made the tracker in the first place should implement and enforce the private flag on his tracker, so that 1) once you pass that whatever IP check you can download the .torrent and share but 2) Vuze will disable DHT and stuff so only people from that specific tracker can trade these torrents.
Either that, or I, like everyone else, fail to understand the whole issue.
|
|
|
Posts:
17
Registered:
11/03/09
|
|
|
|
Re: Ip-filter choosable per torrent
Posted:
Nov 7, 2009 7:26 AM
in response to: np1
|
|
|
|
If you fail to see this doesn't mean it doesn't exist.
A lot of people want this feature to be included. Tell them not to see.
All you suggested is obvious of course but doesn't work.
-"If that's the case, how could someone get a hold of YOUR internal .torrent file and actually manage to download from your private LAN tracker?"
Who's talking this tracker is private? Who's talking a peer has an ability to make tracker's admin to insert a private flag? No one.
There are also the regional nets - it's NOT the a LAN but a subnet of several providers. And the IP's of regional peers will be external (normal, not 192.xxxx or 10.xxxxx, etc.), but traffic between them is free, unlimited and fastest. Therefore peers use a filter.
If a torrent is not private - any external peer may connect to the peer. It's not good.
Of course, we can manually block DHT, PEX. But even if torrent is private (dht and pex blocked) any peer may connect as "incoming". We can't know how an incoming peer has got our IP. So user has to block "incoming" peer source? This is pleasant? - NO, as this will block incoming "legal" peers.
The problem is present. There's no way to avoid it except one - running 2 clients - one with filter, one without. But it's not pleasant.
|
|
|
|
Legend
|
|
Master: 200
- 999
pts
|
|
Expert: 150
- 199
pts
|
|
Advanced: 100
- 149
pts
|
|
Intermediate: 50
- 99
pts
|
|
Beginner: 10
- 49
pts
|
|
Newbie: 0
- 9
pts
|
|
Vuze Staff Member
|
|
Vuze Project Developer
|
|
Vuze Community Moderator
|
|
Helpful Answer
(5 pts)
|
|
Correct Answer
(10 pts)
|
|
