Posts made by MrMazda

Try now… If you still get the same error, then you need to check to make sure you downloaded ALL the files in ALL the torrents, otherwise the system will only register that you are LEECHING the torrent, rather than SEEDING the torrent.

Ask and ye shall receive.

Hehe… My network is WAY more complex now than the standard setup. I have SEVERAL IP subnets across my main network.

On the public facing side, I have the static /32 address for the main connection within the router, then I also have a static /28 and a static /30 subnet, which are public.

From there, I have THREE (soon to be FOUR) DSL lines (all with separate modems) that come together into a single router that bonds them together using MLPPP. That's the ONLY way I can get a fast enough speed out here to be able to stream movies in 1080p HD. THAT in and of itself was rather complex to arrange.

192.168.1.0/24 (Modem 1 - Port 1)
192.168.2.0/24 (Modem 2 - Port 2)
192.168.3.0/24 (Modem 3 - Port 3)
192.168.4.0/24 (Modem 4 - Port 4)
192.168.0.0/24 (Main LAN - Port 5)

Anything that is plugged directly into the main switch will get an IP address on the main 192.168.0.0/24 subnet, and also, anything plugged into any of the modems will automatically obtain an IP address on the respective subnet for that modem.

From there, I also have 192.168.5.0/24, which is reserved for anything connected to the main wireless router inside the house. In order to get there, it must hop through 192.168.0.252 to get to the desired destination IP address. There is then also a line that runs from the main switch, out the outside wall of the house, into the ground, and across the back yard some 200 feet to the trailer, where the line then reappears out of the ground behind the trailer, and connects up inside of the trailer. Anything attached to the router inside the trailer will be assigned 192.168.100.0/24, and will hop through 192.168.0.251 to get to the destination IP on the trailer's subnet.

So... As you can imagine, the concept of port forwarding is nothing new or foreign to me, and in my case, is a LOT more complicated. My laptop for example will come up as a different IP address on the /28 subnet than anything else connected inside of the trailer. There's also a 1:1 NAT translation for a few devices, in order to have those devices directly exposed to the internet (such as the VoIP box, and the server), while keeping the rest of the devices on the network masked behind one of a couple of public facing IP addresses on the network.

It gets rather complicated, but in the end, as long as everything works properly, where's the problem? hehe

So... If anyone should need further assistance, I support a LOT more advanced networking than just your standard home network. Every last stitch of hardware and wiring for my network (including the DSL lines themselves where they come off the NID into the house) was completely custom constructed, programmed, and installed my be. Every single network cable in my arsenal across the entire network was 100% custom created by ME to be the EXACT length it needs to be, without ANY excess cable to be found anywhere. Also, if it's of any value, I'm probably one of the only people you'll ever be able to find who can help support and troubleshoot issues with MLPPP.... It's a dying technology from back in the early 90's, but in cases like mine, it's a very valuable tool because it allows me to bond my THREE, soon to be FOUR DSL lines together to be able to enjoy their combined speed as a single line, so that I can actually get a fast enough speed to be able to do things like stream in 1080p HD, as a single DSL line that only gets about 3.5 mbit down in throughput, simply will NOT cut it.

Tis the down side of being in the middle of nowhere, where the only internet option is oldschool pre-Y2K legacy COPPER based ADSL2 service. When you combine that with the fact that I am just over 5 KMS from the SLAM, in theory, I shouldn't be able to get the 4 meg profiles that I'm getting, and I should only be able to get a 1.5 meg profile per line. Sadly, with copper based DSL, distance is NOT your friend. This is a large part of why I am sharing the connection with my nearest neighbour (and really, my ONLY neighbour), along with the power line that has been run underground to connect my trailer into their main breaker panel to get power. It was a royal pain in the ass to have to dig not one, but TWO different 200 foot long trenches between the house and the trailer in order to be able to bury both the underground network and underground power hookups, without running them on top of each other, which would degrade the quality of the network line that runs to the trailer, but it was TOTALLY worth it. Before when the connection was all wireless out to the trailer, it was a NIGHTMARE any time we got too hot and humid, too wet, or too windy weather conditions, as it would just screw with the wireless between the house and the trailer. Now, I'm quite glad that the only parts of my network that are wireless are either from the main wireless router inside the house to a wireless device inside the house, or it will become wireless once it's already on the inside side of the walls of the trailer to a wireless device (usually just my phone) inside the trailer. The result is that I have reliable WiFi in ANY kind of weather conditions.

The stats that are shown there in your profile are the session totals. In other words, it's the total amount of data transferred since the torrent was started. If you restart the torrent, or in some cases, if you seed from multiple locations, every time you get an update from the other IP address, or every time you stop then restart a torrent, it will refresh the stats. With that being said however, it will still accumulate the transferred amounts to your grand total.

SO… If you're seeding and say only ONE of your locations where you're seeding has transferred anything, when your seedbox updates, it will push those stats to the profile page there, however as soon as your next location updates, the site will see it as a different IP address, and thus as a different session, and will replace the total on the profile page with the reported total from your other location. Once your seedbox refreshes with the tracker again, the stats will be pushed to the grand totals, and the display amount in your profile will change, but once you get another refresh from the location that's not transferring to anything, it will consider it (at least for display purposes) to be yet another new session, and will reset the totals on the profile again, without affecting your grand total.

So... Yes... Traffic IS being accumulated against your grand totals, even though the site does not display the same amount in your profile as it shows in your torrent client. If you were to reduce the seed locations to just ONE location and keep it active, you would notice the stats would begin to build and accumulate there in your profile. So... Even though they do not appear to be accumulating in your profile listings, they ARE accumulating against your grand totals, which is what your overall ratio is calculated on anyway.

I'm a BIG fan of Ubuntu, which is Debian based… Especially when you combine it with a useful little tool such as Webmin. It makes life WAY more straight forward

The best I can do for you was to put some of the torrents that you are seeding on freeleech. This should help to encourage users to download these files, which in turn, should help you see some upload traffic to help restore your ratio.

I can definitely bring it up and see where things go…

I have 4 of them in total, all in different geographical areas, but that's because I also host the DNS services for several different domains online. If I were just using them for regular internet traffic, I would only need one really. Simply put, take a Linux box and install a basic copy of Bind onto it…. It is also recommended to setup RNDC, as this will help with a few things down the line.

From there, just be sure to update the root zone from time to time, then configure your computer or network's DNS settings to point to that Linux box. The Linux box will actually do all the DNS resolving for you, pulling the information straight out of the Master DNS servers, which bypasses the need for a 3rd party DNS service, which can potentially lead to DNS inquiry information being leaked.

@Topsersem:

All things considered, I guess NFO files here are frivolous. This is not a "scene" hub.  ::)

Touché

I would be inclined to say yes because the rules state that non porn content "must contain an LGBT theme". Given that LGBT stands for Lesbian, Gay, Bisexual, Transgender, I would say that they're perfectly acceptable given the current rules.

Ah… I will send you a PM because I do not want to discuss certain aspects of the matter in public view.

On an unrelated topic, is that avatar you? If so #WOOF!

I had a solution for the potential for DNS leaks… I use my own DNS servers now, so that I can control what passes through them, and I can be sure that no information is being skimmed out of the results because I own the actual servers that handle the requests.

This is definitely a change of pace for once. We really appreciate it.

I tend not to use online storage services because of the government and law enforcement's ability to subpoena information from those providers. Instead, I have a few servers of my own setup. The two most commonly used ones are the one located in the basement at my parents' place, and the one located in the basement of the house that my trailer piggybacks off of (for power and network/internet) through underground wire that runs from the house 200 feet into the bush to the trailer. In both cases, they have external hard drives that are attached, which I can access over the network when I'm in the physical location, and soon, also over the internet securely. This way, if any information is sought after, I'll know about it because I'm in physical possession of all the hardware where the information is stored, but yet, it's easily accessible from the trailer, without the need for the bulky equipment in the trailer.

Actually, I don't like how little impact that had on your ratio, so look out… Here comes round 2

I thought you would  ;D

This is actually a common question… I will explain why this happens.

Your torrent client updates with the tracker to obtain the list of peers and update your transfer statistics once every 30 minutes. This will mean that you'll have about 30 minutes where everything stays the same, and then all of the sudden, the stats will update. If you're seeding multiple torrents, this can become a little more complex, because the 30 minute refresh period is based on each torrent individually from the time it was started.

So... This is not at all unusual.

I also see that your upload speed is not the greatest, which kind of confuses me because I'm very familiar with your geographical area (as you're not all that far from me it would seem) and your ISP, and I fail to understand why it is so slow. The only thing that I could think of is that you have their ultra lite package perhaps?

Anyhoo... Since it would appear that you're trying to do the right thing, before your torrent gets purged from the system completely, I'm going to use it to gift you some SBP to help get your ratio in check. This should help to give you a boost to where you ideally need to be. Hopefully, this will help to get you on your way.

I agree that the process can definitely be frustrating, especially if you have a slower upload speed. I used to be in that boat myself, and I understand all too well how bloody frustrating that it can be.

Also, I see that you have both uploaded torrents, so I went ahead and gifted both of you a little SBP pick me up to help boost you both up a little.

Not really… While we have a strict privacy policy, the downloads themselves are run directly from peer to peer. This means that your IP address is still shown in the list of peers for where to get the content. This is something that we cannot do anything about. If you're looking for a more secure or anonymous way of torrenting, I would be inclined to suggest a VPN service that does NOT log anything, such as PrivateVPN. As long as the server you are using supports port forwarding, you'll be all set.

Now, as for the difference between encrypted and unencrypted peers, the difference there is whether or not you are establishing a regular connection to the peer, or if you are using some method of securely scrambling the information while it's being transmitted from one peer to the next. The theoretical difference there being that an encrypted connection cannot be intercepted in the manner that a regular (or unencrypted) session potentially can be.