>trying to share some 20GB+ linux isos with a friend
>both are sitting behind cgnat
>use private tracker with ipv6 support
>use selfhosted tracker on ipv6 only
>use transmission, deluge, qbit
>get the 0(2) peers/seeds shown
>no configuration combination starts seeding
>other torrents from the internet work fine and we can even see each other in the peer list
Where did we frick it up? As far as Google tells me IPv6 is supported by everything using libtorrent, but frick all has any advice why nothing starts seeding besides "forward your ports". As mentioned above, i do got a little ipv6 box due to another project and am trying to figure this out now, but pretty much same result.
>
 Tip Your Landlord Shirt $21.68 |
 UFOs Are A Psyop Shirt $21.68 |
Tip Your Landlord Shirt $21.68 |
cute picture, but i've never used cgnat nor ipv6
test the torrent client using ipleak ipv6 magnet maybe? to make sure ipv6 indeed working for torrent
if no one has his torrent client port forwarded then no data can be transmitted, forward your port
Frick off, moron.
Weird. I get results with transmission, but not with deluge or qbit. I take that as step in the right direction.
Good for you, but here they're all charging 15€+ for dedicated IPv4, cause "that's for businesses". If there'd be a proper option left, i would have switched already.
>Frick off, moron.
>kid cant connect 2 pcs
pottery
You don't know what CGNAT is, do you?
I was put behind cgnat recently so walked up to my provider and said "no thanks please" and they put me back in the old ipv4 pool. Problem solved. May not be an option with cuck providers.
where i live, IPv4 is alive and well, i've never even seen any kind of cgnat cancer. IPv6 is for 4G+ only, doesn't exist over cable for consoomers.
Got some connection working between me and my vps using transmission on both sides and a third party tracker. So i assume it's a libtorrent problem after all.
By the way any ressource to know how to do streaming with torrent from a server and using jellyfin?
Last but not least, i spun up torrust on my vps and am getting up and down from my home to said vps. I tried qbit on another laptop to hop in but still nothing. Installing transmission made it work yet again. Maybe i'll write this all down properly and open a ticket later, but it's good enough for me right now.
If you're only sharing with a friend, why not just set up an sftp server?
Another option is using TeamViewer, which is the most moron-friendly method I know for p2p file sharing between 2 PCs. Even my boomer parents are able to set it up.
>TeamViewer
Holy Boomer. Did they just thaw you out?
TeamViewer just works
And if both PCs are on CGNAT options are pretty limited, depending on the implementation by the ISP not even ftp/sftp might work.
Unless you have a better suggestion? Don't be a zoomer and say Discord ffs
Lmao, teamviewer is an insecure piece of shit. Why do you think their numbers dropped continuously after 2016?
When has DHT ever worked?
>VPS too small
>checking for filesums cumbersome
>he's using windows, so way back is also cumbersome
>bias, as torrent used to just werk
Mix of all above basically.
Probably Anydesk or Rustdesk. That said, too much of a hack solution in my opinion.
>VPS too small
so? ssh does forwarding, so you can connect to your friend through the vps without actually storing anything on the vps, like a proxy
IPv6 is such a mess
Just use the magic-wormhole
you gotta have a port open on at least one side. Easiest way is to either use a VPS and dynamic dns to do port forwarding or vpn to the same network, or use zerotier/tailscale.
Are you creating a torrent with the private track flag enabled? Why not just leave that shit public and find your friend through DHT? Also, enable UPnP on qBittorrent if you haven't already.
>Why not just leave that shit public and find your friend through DHT? Also, enable UPnP on qBittorrent if you haven't already.
they're both behind CGNAT, anon, neither of them can be connected to directly
done something similar in the past and also had similar issues. iirc had to enable some settings that seemed dumb in order to get it to finally work. try this in qbittorrent for both clients
>options -> bittorrent -> encryption mode require encryption
>make new torrent file private
>share torrent file
>add peers manually
voila
forgot in qbit you cant add peers manually anyway you can figure that out Im sure as you already see 0/2
In what client *can* you add peers manually?
its been nearly a decade but I think utorrent and bittorrent both had that feature. wouldnt recommend either these days
i haven't used it before because i've never had cgnat, but there are tools out there to set up wireguard connections with STUN, which may be a good fit for your situation
with a wireguard tunnel, it trivialises any other kind of connections as well, since you'd effectively then be on the same "lan"
Isn't the cgnat for your outbound IPv4 addresses to route to other ipv4 sites? Can't you just make the ipv6 addresses talk to each other directly, and make sure your traffic is going through that path? If everything is ipv6 it works without nats needed anywhere.
>ipv6
I disable ipv6 at build time from my kernel config.
Cute artist.
NAT traversal has always been a thing. Get a proper torrent client like troonymission or queerBittorrent
you and hour friend have fake/cuck internet
your israeli controlled ISP doesn't allow you to forward incoming connections over IPv6 in your telco shitbox, try opening ports in your ont/router/modem whatever your ISP gives you, they usually lack configuration for ipv6 firewalling and the ipv4 configuration is meaningless behind cgnat
other torrents can kinda work since one of the parties can receive incoming connections, thus sturn works
croc just werks in my experience, it has relaying thus no need to care about opening ports, nearly perfect tool for sharing stuff with a other party
this thread is full of morons
use TURN or STUN servers. it was meant for nat traversal
Forward your ports.
Seriously, how do you think IPv6 works? It may not be firewalled by a CGNAT, but it still is firewalled by your router, so make an expection for it in the router settings.
I think SSH isn't a bad idea here