Can i download torrents now opendns

Where did you hear that OpenDNS blocks torrents? Even if it did, it's trivial to change DNS if they have any sort of tech inclination. If you're concerned about legality you need something that'll actually block without being circumventable.

A VPN would be the way to go, but you'll still have to actually block torrents somehow. Make that the safe DNS that blocks torrent sites. Even if you do persuade the tenants to use a VPN, without effective blocking you're relying on them to get it exactly right and never have any slip-ups. If they don't, and you start getting copyright violation notices, it's not like you can explain to your ISP that it's your tenants, because most ISPs don't allow you to share your internet connection with tenants in their terms of service.

I guess another solution might be for you to get a VPN and use it in your router if your router supports that - again you might need more flexible firmware like DD-WRT. Make the tenants pay for a high-performance VPN so that your internet performance isn't impacted. But if the tenants are still doing illegal torrenting, you have to trust that the VPN company is never going to come back on you and say that they got complaints and were forced to turn over your subscriber data by a court warrant.

Why go to that much trouble? I think I would put it to the tenants like this: - You are supplying them with an internet connection.

Don't abuse it. If you ever get a copyright violation notice, their internet will be cut off and they'll have to pay for their own connection. No excuses, no second chances. You wouldn't even know if someone were doing that. Not suggesting anything, just a random thought not related to anything in particular.

You can't totally block them. YOu can try to block some but they can find a way to bypass it like a VPN ect. But you can limit the speed and it will discourage them from downloading it. Thanks for your input, guys. VPNs are a big waste of money and I have no interest in getting one. I just don't want people downloading torrents on my connection. If they want torrents they can pay for their own internet connection.

I'm a little concerned that they could download the torrent files using their cellphone, transfer it to their PC, and then download it illegally on my connection. I'm not sure how paranoid I should be. My Linksys ev2 router unfortunately lacks the features I would need to properly lock everything down.

I would be willing to upgrade to a better router if you guys have any suggestions if you think it's necessary. Do you have any suggestions? Could I daisy chain it to my v2, just using the WRT54G to filter everything out at the internet level? It's quite hard to actually directly block torrents as in the transfer, not the file It's not even the torrent file you have to worry about.

Magnet links don't even need torrent files. Good luck doing it on a consumer router. I'm not even sure pfSense can block torrent transfers. I mean It all depends on how far you want to go with it and how much money you want to throw at it. This way if something questionable does happen, you have a record that it's not you doing it. Am I the only one that's noticed this?

I expect this isn't an issue for those that are in love with magnet links but I prefer actual. I only use magnets when I can't find a. BTW, I had to re-register with my same username on this board as my account was deleted, perhaps for non-usage as I don't visit here all that often Update: I went back to opendns to get their DNS server addresses and re-entered them as my DNS servers and the problem has reappeared.

Earlier I did erroneously state that I was getting the same error message for duckduckgo as the torrent sites however that was incorrect. The error message for duckduckgo is "this connection is untrusted" while the torrent site related error is "The page isn't redirecting properly.

Firefox has detected that the server is redirecting the request for this address in a way that will never complete. I use OpenDNS and haven't experienced anything like that. But seeing as how you didn't actually list what sites weren't loading properly, I can't confirm or deny there is any problem. Not using their DNS server just means it is a little more difficult for the them to create a history of lookups. Unless you are using a VPN, they can still see where all your packets are going.

Any decent client should treat magnet links and torrent files the same. Perhaps instead of jumping through hoops locating torrent files, you should be looking for a better torrent client. I think you confirmed what I already figured on the DNS servers being about the same vulnerability as it's been my understanding that the primary vulnerability is someone in the swarm getting your IP when actually torrenting. I reinstalled the opendns servers and the problem returns. I had this happen on several torrent sites however I can get through on others but when I choose the.

I've had this issue with more than a few torrents over the last couple of days and can't remember them all but further checking does seem like it's either particular torrent sites I can't access at all or on sites I can access but store their. On duckduckgo I get the "this site is untrusted" error. Again, when I abandon the opendns DNS servers I've been using for years and go to "automatic" both of these issues disappear with no other changes.

I've emailed opendns and described the issue and they haven't gotten back to me yet and even though this doesn't seem to be a Firefox issue I'll probably post it there as well. As far as magnets go, I can click on a magnet and get the file as always, I just don't like those as is doesn't input the file size or let me see what files are actually actually in the torrent until it downloads a bit and unless something has changed about that I don't think that's any different on any client.

Reading on this it seems to be a. As seems to be the magnet issue of not being able to change the DL location on a file until it downloads a bit. I am using an older utorrent 1. I appreciate the links and will look at those. I distrust Google over privacy issues and thus don't want to use their DNS servers but if opendns is going to be a pain I might have limited choices Update: it's definitely an opendns issue. Perhaps it's inadvertent but both issues go away using everyone else's servers from what I can see.

Thanks again for the links opennicproject has servers very close to me so I think I'll use those from now on and forget about opendns awhile. Since you mention the problem started in the last couple of days, think back on what you installed, websites visited etc along those lines. If you are very particular about finding the cause, view your http traffic to debug the problem.

Here are some tools that could help. The security certificate is good. Not sure why you get that error. Try to isolate the problem. Use different browser, PC if possible. Give bittorrent client a try if you are uncomfortable with utorrent. Interface is similar.

During installation be watchful and opt out uncheck installing "extras". I stopped testing after those two. I am guessing it is something you configured OpenDNS to do for you as I have none of the problems you are experiencing. It is a client issue. You are using a client version with limited magnet link support. The only difference between a torrent file and a magnet link is how the torrent metadata gets loaded into the client.

Either way the data itself is identical complete with file list and sizes. Don't fault the protocol because the client doesn't handle it properly. It pays to use the current versions of your Bittorrent Client.

Don't let the little things Design, Ads, etc stop you from getting a proper download. The problem absolutely doesn't exist unless using opnendns free DNS servers, it simply has to be their issue. Again, I've confirmed the issues by switching back and forth between their DNS servers and either using automatic settings or using other DNS servers and the issues only exist with the opendns free servers. I've begun using the opennicproject's servers and none of these issues exist using their DNS servers either.

I think I'll stick with those as there is one very close to me and all the links that don't work with opendns work with opennicproject. I think I mentioned it before but one clue as to what's going on is the details on the "untrusted" errors at duckduckgo and java show that the certificates belong to opendns rather than the specific sites so I expect their code is screwed up and inserting their cert rather than the proper one At any rate I'm sticking with the opennicproject DNS servers, at least for now and as always, digging into this problem has lead me to new learning experiences as I tend to go off on tangents when exploring stuff like this when I find something interesting.

I can see no other explanation other than some sort of opendns issue when it only happens using their servers and on none of the other DNS servers I've used when testing this in the last couple of days.

Thanks for the responses. As far as I'm concerned this issue is "solved" by using other DNS servers.