Can't Seed

[Nearsighted Scrappile]

I did mention it before. My computer is wire connected to a Netgear wi-fi box. The Netgear is wirelessly connected to the Xfinity modem.

[RodneyYouPlonker]

In my computing world a modem and a router are 2 different things unless it is a combined modem/router.  I'm really not sure how you do your set up but I can tell you that when I used to have Cable internet a while ago I had a router/modem which was provided for me by the Cable company.  It wasn't really something that I liked all that much but there was a mode where you could disable all the router parts and just use it as a modem.  This is what I did, turned the router bit off and used the Modem only mode.  This was great then as I was able to use my Cable modem and connect it to my router and then was able to wire up the computers using that.  It was a good way for me to do that, going from a Modem and then into a Netgear Router.

I don't use this Netgear router anymore now but I did for a few years.  The whole Port Forwarding settings were accessed from logging into the Netgear router and then changing the open ports for your computer to allow connections.  Simply putting the same value as what you had in uTorrent would allow for the port range to open up and then like Moe says you are allowing your PC to accept incoming connections to the swarm.

If you're not doing it like this whether you have Wifi or not it's not going to work really.  Opening up a range of ports through your firewall is the only way you can see properly.

I'm usually more, when it comes to all this stuff, better when I can actually see what people are doing instead of just guessing when you're posting on a thread in a forum somewhere.  I'm a lot better when I have these things in front of me so I can see what's going on, usually then I can identify what's happening.

I still say though just sign up for a seedbox, they're a lot better and you get proper seeds and you can seed from a Linux Client which is a lot better.  I used to Seed using Windows for years but then eventually I stopped doing that because the speeds were poor and with a seedbox you can do so much more.  If you make a torrent yourself you can send it out first and then get your seedbox hosting it and then it's better it can run 24/7 and you don't have any issues about power cuts or having to reboot so often like if you're using your home computer for example.

Seedboxes are the way really, if you want to do proper seeding I mean...

[Nearsighted Scrappile]

Oh dear.

It would seem that my computer thinks it is directly connected to the modem and the Netgear wi-fi box is nowhere to be found. I have no idea how that happened. I'm about to just say fuck it.

[waregim]

Looking at this last post , I remembered a similar problem I once had, but......

I used wired CAT5.

This is a wireless network.
The desktop is connecting directly to the modem, bypassing the router.

If the Xfininity modem is recent, connect the desktop to it with cat5 and log into it with 10.0.0.1, 10.0.1.0 or call their tech support for the address (sometimes it is on the label). you should be able to set up a connection to the router. Make a note of the router IP. Then disconnect the CAT5 and see if the desktop is now seeing the router (instead of modem) as the *default gateway*. You may need to enter manually the router IP into your network/TCPIP settings for default gateway, typically something like 192.168.0.0.1

If I am missing something, hopefully Moe will be along to correct me...

[RodneyYouPlonker]

typically something like 192.168.0.0.1

I've never heard of an IP address before that has more than 4 numbers separated by dots...

It seems the OP has decided now that he 'gave up' the other day and has already said now "f**k it".

[Nearsighted Scrappile]

I'm still checking the thread, but I don't know how to fix this. I don't have a cable long enough to reach the modem. I can use the internet, so if I end up never being able to seed again, oh well. I'm not going to screw everything up by trying to get numbers off of the wi-fi box and the modem. Disability problems prevent me from being able to do all that crap as easily as I once did. I appreciate everyone's input, though. I see it this way, if Windows 10 can't offer the level of help that it gives me for everything else, then I won't bother.

[RodneyYouPlonker]

Do you have anybody you know that knows a few things that maybe you can call on them?  I know there's a lot of people around, people who are into Tech.  Anybody you might know in the area or somebody who is on Facebook who knows a thing or two?

I know these problems can be terrible.  You can believe me the problems I've had to deal with over the years, crazy stuff really just to get something working like it should.

I'm not sure what to suggest really and it's hard on here trying to help people.  The question is really what has changed really since you was seeding before.  What changes have happened and how can you reverse the problem to try and get it working again.

Part of all this computing stuff these days is being able to fix it and if that's the problem it's also being able to call on somebody you know well to offer help.

[waregim]

192.168.0.0.1 - need new glasses.
Indeed it should be :192.168.0.1
But it can have variations such as 192.168.1.1
Newer routers may use 10.xx.xx.xx (But I have usually seen that on modems with NAT. )

Last digit can even be 0.

Overall point being is that if you got 2 NATs on a system there is a possibility of confusion over which one is the address *server* . I have a 2 NAT system here, but *wired*, where this problem has occurred. The desktop need to be instructed to use the router, rather than the modem for the gateway, and the router's gateway should be the modem.

You can turn off NAT on Xfinity modems (that I have seen) - but its not a good idea.
I really like a 2 NAT system as it does appear to provide extra security.

I dont think we have far to look for a real expert on networking: Here.
Moe.

[Moe]

Double NAT adds complexity, but can still pass incoming connections if proper ports are forwarded at both routers.  This happens frequently when running a VPN client on a router rather than on the desktop, for example.  Wired vs. wireless isn't really relevant as the configuration is the same either way.

A side effect of NAT is that incoming connections can't pass through the router if they are not forwarded, but that shouldn't be considered security.  That comes from a good set of firewall rules in both directions.

The modem should be configured as a network bridge and let the router handle the routing.  There is nothing to gain from multiple routers.

Avoid using IP addresses that end in 0 or 255.  While both are legal, they have historic meanings and older equipment doesn't handle them well.


All this is academic really until OP determines where network connections are being blocked.  To reiterate, if your client can download, your client can also seed as once you are connected to one or more peers, data can flow both ways.  Being able to accept incoming connections just increases the ability to connect to more peers in the swarm, which is important for small swarms.


One other thing specific to TPB is the ability to create outgoing UDP connections.  That is because TPB magnet links include only UDP tracker URLs.  Additionally, DHT uses the UDP protocol exclusively.  Firewalls differentiate between TCP and UDP packets, and if you have a firewall configuration that lets TCP traffic pass, but not UDP, then you will never be able to start a torrent from TPB.  You can successfully start torrent files or magnet links that include a TCP tracker, so that will add to any troubleshooting confusion.

[Nearsighted Scrappile]

Well, I opened a couple of torrents and lo and behold, they seeded. I didn't change anything, so I guess it's going to seed when it can.