Posts made by MrMazda

This largely depends on a few factors, the three biggest of which are:

1. The upload speed that your ISP provides for your internet connection. Most residential internet connections have a substantially slower upload speed than their download speed, so be sure to find out what your connection's limits are.

2. Whether your ISP uses traffic shaping to throttle your speeds based on the presence of P2P traffic from a computer on your connection. If this is the case, a VPN such as PrivateVPN will get you around this problem. Also, if you're on a DSL service and your ISP supports it, you may also be able to get around this problem with the use of MLPPP. If you wish to go down this avenue and your ISP doesn't offer technical support for MLPPP, I would be more than happy to assist you with it. On my connection here I am on a 3 line (soon to be 4 line) MLPPP setup, but this is largely because a single line simply won't deliver a reasonable speed.

3. Whether you have the correct port for your torrent client forwarded both in TCP and in UDP from your router to your computer. This is the #1 most frequently missed step in the process that results in little to no upload traffic.

Of course, there are a few other factors, such as the number of leechers actively downloading the torrents, their connection speeds, what all else they're connected to, and so on, but the above 3 factors are the 3 biggest factors.

Also, remember, that DSL technology, especially the older DSL technology from the pre-Y2K era is a dying technology with very limited potentials. In terms of upload speed, you'd be looking at the following:

Copper ADSL2: 512 - 800 kbit
FTTN ADSL2: 800 - 1088 kbit
FTTN VDSL: 1088 kbit - 10 mbit

The biggest problem with FTTN service, as opposed to FTTP (aka FTTH) is the upload speed limitations, as they are largely dependent on distance from the SLAM where the copper begins. With Fibre going all the way to the end of the connection at the premise, the upload speed potential is far greater. The problem is that most of the world still hasn't rolled out this kind of technology.

Actually, not all mods can tell you why it was deleted… This is something that only a select few mods have access to. The two most common reasons for torrents disappearing are duplicates and DMCA removal requests.

Hehe… Different people like different things....  ;D

I see that you are using Linux… Also, that error message suggests that you are using Transmission. When Transmission says that a torrent is "Stalled", generally it means that there is no activity on the torrent within the last however long your threshold settings are set to. This is not a problem necessarily, as it just means that there has been no activity.

What catches my attention though is that the tracker says you are using a different torrent client. I'm not sure how you'd check the tracker state or error message in the torrent client the tracker says you are using (or otherwise have used). I would imagine that the problem is that you're either not able to resolve the tracker's IP address. This is the most common issue with tracker communications, aside from the tracker timing out occasionally. To ensure you are able to resolve the IP address properly, I would suggest changing to Google DNS by using 8.8.8.8 and 8.8.4.4 as your DNS server settings.

Actually, with some torrents and some torrent clients, this is not unheard of. It's nothing to worry about though

Actually, I sent a PM to a particular mod who handles this kind of request. They should handle this for you once they login next.

The helpdesk request would only end up getting forwarded to said mod anyway.

No… Once a torrent has been taken down by DMCA, it will come up in the tracker with an "unregistered torrent" error. Unlike duplicates, they are outright removed, rather than being put in a special state where any current leechers can at least finish their downloads the way that the duplicates are.

Generally speaking, a VPN is a safety assurance. With that being said however, not all VPN connections (or even providers) are the same. Always check to see what (if anything) that your VPN provider logs. The ideal answer is nothing. This way, this means that your VPN does not keep any logs that can connect their users with IP addresses, which is a big part of what makes them a "safe" place.

The second thing to consider is the type of VPN that you're using. Using a PPTP VPN for example is probably the worst thing you could possibly think of from a security standpoint, because it can in theory be reverse engineered under the right circumstances. For best results, I would recommend a properly installed OpenVPN session. To enable port forwarding, you will need to ensure that you are using UDP + TAP, however for general security, I would recommend using UDP + TUN. It all depends on what you want to use it for, and if you want to have the potential to share network resources across the VPN.

My best advice is to use a secure VPN (preferably OpenVPN based) that does not log anything such as PrivateVPN. This will ensure that you're able to mask absolutely ALL of your internet traffic, including DNS lookups and the information of where you're actually connecting to and what you're really doing on the internet. Regardless of what VPN you use, make sure that they support P2P traffic, that they log nothing, and that they have a port forwarding option. PrivateVPN is all of the above, and from my experience, they just work.

AFAIK, this torrent is not currently on the list of banned clients. I know we used to have a list of banned clients somewhere, but it seems to have disappeared over time.

The one thing that I would wonder about this torrent client is does it download the contents and enable you to stream as you're downloading, or is it a stream only kind of deal? If it's a stream only kind of deal, I would caution against the use of this client, simply due to the fact that it would prove to be detrimental to your ratio. If it just downloads it in order so that you can stream it while it downloads, then keep it seeding like a normal torrent client, then I think this may be something that I might want to look into.

The order of preference depends on a few factors, one of which is the speed at which the peer is able to upload.

With our tracker, another HUGE factor is having your port forwarding setup. On most traditional internet connections, your modem will either be attached to a router or have a router built into it. This takes all of the IP addresses of the computers on your home network and masquerades them to a single IP address that their connection will use for the internet. The problem comes in whereas your router needs to know what port you are using for your torrent client, as well as the IP address of your computer on the home network in order to forward the connections to your torrent program properly. If you do not do this, with our tracker, it will become extremely difficult, but not impossible to get upload traffic, as this will bounce you to a very low node priority if it is not configured correctly.

I just thought I'd point that out. In my case, my network is a little more complex and advanced beyond the need for port forwarding (at least for my server and my laptop), because both of them are on their own dedicated IP address as far as the internet is concerned, but this is not the case with most users.

It would appar that with this torrent, that is exactly what happened. There appear to be a few users who jumped on straight at the seeding process. For this reason, I will throw you some SBP to help offset that.

Ah… Yes... You do have a point there. For that purpose, I have IP range filtering in the iptables firewall rules of both my main server as well as the main super network that everything runs off of, including my trailer. It's a free way that can also be used to do such things, if you are a more advanced user, and you maintain the IP range rules manually, as they change.

If it's of any value, I have access to a professional recording studio where I can digitize such things with high end equipment that is designed for optimal quality. There is literally NO VHS tape that said machine cannot read if you play with all the available settings.

Also, it's not just VHS that I can rip from. I can also import from Sony Beta, as well as 12" vinyl, or cassette tape. There really is no media format that I cannot convert to digital format of some sort.

I used to use PeerBlock back when I used to run Windows. I can say that it is not a guarantee for a few reasons, one of which is that network assignments do tend to change. With a VPN on the other hand, this effectively eliminates the need for PeerBlock because it ensures that your direct IP address is never shared, but rather, only the IP address of your VPN. If you have a VPN that does not log anything such as PrivateVPN, you can be sure that even without peer block, your real identity will remain hidden from the internet.

Another thing to consider… Not all VPN providers are the same. It is important to check what their policies are around a few things and what geographical jurisdiction that they fall under. In the perfect world, you want a provider that is NOT based in the United States, and who does not log connections, logins, etc. This will ensure that if they are ever issued with a valid subpoena to identify a user based on an IP address and a time stamp, they will be unable to provide this information to make this link to the customer because they do not store this information in the logs in the first place.

Given the age of that one, it's possible that we may have once had part 1, however it has since been purged because it went dead and could not be revived due to its age.

Yes… It is not uncommon for universities to censor certain content from their network. This generally consists of adult content, and websites that promote or are otherwise affiliated with criminal activity. I sort of get the reasoning behind it, but what they fail to understand is that at this day and age, there is no such thing as internet censorship. Simply put, internet censorship is a myth!

Also, it is not uncommon for universities (at least in North America) to attempt to censor P2P traffic from their networks, as the majority of (although not all) P2P traffic is illegal pirating. This is generally done as a legal precaution to attempt to keep the university out of trouble by blocking such traffic from their network.

EDIT: Also, I forgot to mention that PrivateVPN can be set to work on TCP 443, or if you want port forwarding, can also be setup to use UDP 53. TCP 443 is used by HTTPS websites, and UDP 53 is used by DNS, so blocking either one of these ports to filter content would render the internet itself useless. This is one thing that I like about them. This way, there really is NO network that you cannot bypass the censorship of, because even if they force all DNS traffic to their own servers, there's also the TCP 443 route, which cannot be blocked.

So… Unless they're blocking all DNS traffic except to their own internal servers, and they're domain null routing to bypass VPN providers specifically by domain, there really is no way to control what content can pass through a network.

This sounds like a possible intermittent routing issue with your provider. Changing providers, or even using a VPN to route around your provider's defunct route, would get you around this when it happens.

@wohdin:

That's not how torrents work. The torrent files you download from the tracker contain your account credentials, which is how your upload and download traffic gets tracked in order to give you the credit you earn. You do not need to be "logged in" on the website for it to work - they're entirely unrelated elements.

Did you even read what I wrote? You have to be logged into the website to send the .torrent file to the website, and to get the .torrent file you need for your torrent client. Once you have that file, whether or not you are still logged into the website is irrelevant. Nothing I've said contradicted what you have stated.