IPv6 network - not reachable
brasax user
on March 2nd, 2014
/ post 62497
This is a very rough solution as i am very unsure if it will work?
Have you tried downloading a torrent file with a passkey instead of logging into the tracker? Try it with one file, see if you can get connectable and then download other torrents if this works.
Let me know if you are unable to locate the "download with passkey" button. You can also option this function in your personal settings.
Have you tried downloading a torrent file with a passkey instead of logging into the tracker? Try it with one file, see if you can get connectable and then download other torrents if this works.
Let me know if you are unable to locate the "download with passkey" button. You can also option this function in your personal settings.
brasax user
on March 3rd, 2014
/ post 62504
It is not working..
I need to check where the problem is.. It seems the the settings in the FritzBox are not correct..
I need to check where the problem is.. It seems the the settings in the FritzBox are not correct..
brasax user
on March 3rd, 2014
/ post 62507
I've checked the settings and I'm in general reachable through IPv6, but not within Transmission.
I tried now 3 torrents with a passkey, but I'm still not reachable, means 100% down.
Is there something else I could do? I've seen that it must be possible, as I was downloading from some people also using IPv6..
I tried now 3 torrents with a passkey, but I'm still not reachable, means 100% down.
Is there something else I could do? I've seen that it must be possible, as I was downloading from some people also using IPv6..
mmmmm, by all means this should repair the issue you are having. Possibly, the problem is deeper, possibly with your isp?
Have you tried a program outside of transmission? Like utorrent, just to see if you experience the same issue?
Have you tried a program outside of transmission? Like utorrent, just to see if you experience the same issue?
brasax user
on March 3rd, 2014
/ post 62510
Checking right now..
I've checked the connectivity with https://www.subnetonline.com/pages/ipv6-network-tools/online-ipv6-port-scanner.php and I'm reachable, defined port is open..
What does the passkey do exactly?
I've checked the connectivity with https://www.subnetonline.com/pages/ipv6-network-tools/online-ipv6-port-scanner.php and I'm reachable, defined port is open..
What does the passkey do exactly?
moocowdan wrote:
Have you tried a program outside of transmission? Like utorrent, just to see if you experience the same issue?
Have you tried a program outside of transmission? Like utorrent, just to see if you experience the same issue?
brasax user
on March 4th, 2014
/ post 62512
I had uTorrent running the whole night. Same issue..
Sorry brother, i am perplexed by your issue.....
Friends can anyone shed any light on Brasax issues?
Friends can anyone shed any light on Brasax issues?
Passkey bypasses the need to be logged into the tracker.
Normally you have to be logged into tribalmixes in your web browser before opening your torrent client. Passkey bypasses this, your login details are within the torrent file.
Normally you have to be logged into tribalmixes in your web browser before opening your torrent client. Passkey bypasses this, your login details are within the torrent file.
brasax user
on March 4th, 2014
/ post 62515
Ok.. :)
I tried with a friend and the port (IPv6) is open and reachable from other machines.. I think the problem is the tracker that only works with IPv4. If I disable IPv4, so Transmission is working with IPv6 only, the tracker cannot be connected anymore..
Is this possible?
I'm not able to open any port on IPv4 as my provider uses DS-Lite and shares the IP with some thousand other users..
Any ideas? Or maybe I'm wrong?
Many thanks in advance!
brasax
I tried with a friend and the port (IPv6) is open and reachable from other machines.. I think the problem is the tracker that only works with IPv4. If I disable IPv4, so Transmission is working with IPv6 only, the tracker cannot be connected anymore..
Is this possible?
I'm not able to open any port on IPv4 as my provider uses DS-Lite and shares the IP with some thousand other users..
Any ideas? Or maybe I'm wrong?
Many thanks in advance!
brasax
slash ProDanceCulture
on March 4th, 2014
/ post 62516
ok let me finalize this. we are really glad you tried all possible ways to solve this. let me just explain something, and this should be over, i think. and sorry i didn't do this earlier, kinda missed this thread...
here's how it all works. client starts a torrent. client announces this action at the tracker. info passed to the tracker also includes the port at which client accepts connections for this torrent. tracker wants to know if client is connectable, so it tries to connect to the client using the ip and port provided. this is done with the following php line of code:
$sockres = @fsockopen($ip, $port, $errno, $errstr, 5);
here's the info - https://us2.php.net/fsockopen - it doesn't really mention anything about ipv6, except one little note: using ipv6 one has to put the numerical ip into the square brackets. this is doable, but the problem is, you are reporting a normal ipv4 address to the tracker, and you can look it up in your profile. try any ip reporting website and see what that site says? is it same IP that is in your tm profile?
anyways, tm usually gets ip from $_SERVER['REMOTE_ADDR'] which theoretically can report ipv6, so basically what i am saying is that we first need to get your ipv6...
side note... see, because tracker tries to detect your ip, it takes what it can get. i just cross compared all of your 98 peers have same ip in database as is listed in your profile. not writing it here, because you know why... anyways, have you tried to set "report special IP to tracker", there's such a feature in utorrent, with your ipv6 address. maybe if you set there your ip as ipv6, it will be sent to tracker and then tracker will try to connect back to you?
side note... now passkey has nothing to do with this really, it allows you to seed torrent from any ip without the need to have that ip listed in your profile, thus your identity is detected via that passkey, and NOT by comparing your account ip and this new peer's ip. it allows you to seed from many different ips at once, but will not help with connectivity.
side note... just for you and only for now, here's a test: download any NEW torrent, open it in the client, and edit announce url - replace 'www' with 'testnew'. then start the download. and see what the client shows tracker response was to your announce. in there i will now set so that it will show your ip (as the tracker perceives it) and the way it was passed in $_SERVER - as ipv4 or ipv6. try a couple of clients, see if message changes, try to set that option i mentioned above - report ip to tracker, and see if anything changes, although i think tracker will look behind what you want it to see and will detect normal ipv4... anyways, try and tell me what tracker says...
i hope you're still with me, because now we get back to those explanations i started way above... so tracker initiates a connection to this new peer and if it was successful, assumes that peer is connectable, if nothing happened for 3 seconds, tracker assumes peer unconnectable. and here's the biggest secret in this all: all this connectability stuff is only for you. i am not even writing this in bold, so others won't see it.. =) and i mean, this is how it is on tribalmixes: tracker checks and tells and site explains even some stuff, but in the end, this is to help you to become connectable or look into it at least, and in the long run - improve your experience not only here, but at any other tracker, being connectable means sharing way more and faster and seeding at full speed usually, i seed 13k torrents, 5k of the active, the rest - queued, and i constantly 100% of the time use all my upload, having 30-40 active upload-connections at all times, i allow 600kb/s to utorrent and it's always every minute 100% used. anyways, getting back to the tracker, this is why it is important for you to be connectable, but not for the tracker, and to be honest, one can even ignore what tracker says, if their client, like utorrent, says "there are incoming connections and they get through and you are connectable", green (or red) circle in the right bottom of the client window.
and let me finalize this from a new line...
when someone starts new download and asks for a list of seeds on a torrent that you are also seeding (as unconnectable), the tracker gives all (up to 20) sources, not concerning itself connectable or not, all of them are sent to your client and it's not client's turn to act as it's setup, go over those sources and try to connect to them, or what not, so basically tracker checks connectivity but that's where it all ends and there's no discrimination between connectable and not connectable users. there's a big difference between the 2 groups, and it is mostly that connectable users have good ratio, and unconnectable - bad. =) your ratio is good, thus other people's clients are able to connect to you, with the ipv4 (and port) that tracker reveals to them, and you're able to seed your downloads, only your curiosity maybe here is suffering trying best of you and stuff, but no worries, connectable or not, it's up to you, and the rest is between you and other peers and if you are truly connectable, those peers will connect to you. by the way, check out some active up/down-loads in your client. dunno about transmission, but utorrent also shows if it was connection that you (or it) initialed, an outgoing one, or if it was an incoming request, and usually marked as I and O i think, and see if you have any I-s.. it may also say if ipv4 or ipv6 or udp is used on that connection... please explore those things too.
so anyways, if you're curious and wanna finish this up, and i am curious, i wanna know what testnew announce will tell you, cause others will come with ipv6 stuff only, and they will need help too, i presume... lets see though to the end of this?
here's how it all works. client starts a torrent. client announces this action at the tracker. info passed to the tracker also includes the port at which client accepts connections for this torrent. tracker wants to know if client is connectable, so it tries to connect to the client using the ip and port provided. this is done with the following php line of code:
$sockres = @fsockopen($ip, $port, $errno, $errstr, 5);
here's the info - https://us2.php.net/fsockopen - it doesn't really mention anything about ipv6, except one little note: using ipv6 one has to put the numerical ip into the square brackets. this is doable, but the problem is, you are reporting a normal ipv4 address to the tracker, and you can look it up in your profile. try any ip reporting website and see what that site says? is it same IP that is in your tm profile?
anyways, tm usually gets ip from $_SERVER['REMOTE_ADDR'] which theoretically can report ipv6, so basically what i am saying is that we first need to get your ipv6...
side note... see, because tracker tries to detect your ip, it takes what it can get. i just cross compared all of your 98 peers have same ip in database as is listed in your profile. not writing it here, because you know why... anyways, have you tried to set "report special IP to tracker", there's such a feature in utorrent, with your ipv6 address. maybe if you set there your ip as ipv6, it will be sent to tracker and then tracker will try to connect back to you?
side note... now passkey has nothing to do with this really, it allows you to seed torrent from any ip without the need to have that ip listed in your profile, thus your identity is detected via that passkey, and NOT by comparing your account ip and this new peer's ip. it allows you to seed from many different ips at once, but will not help with connectivity.
side note... just for you and only for now, here's a test: download any NEW torrent, open it in the client, and edit announce url - replace 'www' with 'testnew'. then start the download. and see what the client shows tracker response was to your announce. in there i will now set so that it will show your ip (as the tracker perceives it) and the way it was passed in $_SERVER - as ipv4 or ipv6. try a couple of clients, see if message changes, try to set that option i mentioned above - report ip to tracker, and see if anything changes, although i think tracker will look behind what you want it to see and will detect normal ipv4... anyways, try and tell me what tracker says...
i hope you're still with me, because now we get back to those explanations i started way above... so tracker initiates a connection to this new peer and if it was successful, assumes that peer is connectable, if nothing happened for 3 seconds, tracker assumes peer unconnectable. and here's the biggest secret in this all: all this connectability stuff is only for you. i am not even writing this in bold, so others won't see it.. =) and i mean, this is how it is on tribalmixes: tracker checks and tells and site explains even some stuff, but in the end, this is to help you to become connectable or look into it at least, and in the long run - improve your experience not only here, but at any other tracker, being connectable means sharing way more and faster and seeding at full speed usually, i seed 13k torrents, 5k of the active, the rest - queued, and i constantly 100% of the time use all my upload, having 30-40 active upload-connections at all times, i allow 600kb/s to utorrent and it's always every minute 100% used. anyways, getting back to the tracker, this is why it is important for you to be connectable, but not for the tracker, and to be honest, one can even ignore what tracker says, if their client, like utorrent, says "there are incoming connections and they get through and you are connectable", green (or red) circle in the right bottom of the client window.
and let me finalize this from a new line...
when someone starts new download and asks for a list of seeds on a torrent that you are also seeding (as unconnectable), the tracker gives all (up to 20) sources, not concerning itself connectable or not, all of them are sent to your client and it's not client's turn to act as it's setup, go over those sources and try to connect to them, or what not, so basically tracker checks connectivity but that's where it all ends and there's no discrimination between connectable and not connectable users. there's a big difference between the 2 groups, and it is mostly that connectable users have good ratio, and unconnectable - bad. =) your ratio is good, thus other people's clients are able to connect to you, with the ipv4 (and port) that tracker reveals to them, and you're able to seed your downloads, only your curiosity maybe here is suffering trying best of you and stuff, but no worries, connectable or not, it's up to you, and the rest is between you and other peers and if you are truly connectable, those peers will connect to you. by the way, check out some active up/down-loads in your client. dunno about transmission, but utorrent also shows if it was connection that you (or it) initialed, an outgoing one, or if it was an incoming request, and usually marked as I and O i think, and see if you have any I-s.. it may also say if ipv4 or ipv6 or udp is used on that connection... please explore those things too.
so anyways, if you're curious and wanna finish this up, and i am curious, i wanna know what testnew announce will tell you, cause others will come with ipv6 stuff only, and they will need help too, i presume... lets see though to the end of this?
you just wrote an essay slash OMG.Top job i would assume, i did not read it all. but my god, thats dedication
La petite mort
brasax user
on March 5th, 2014
/ post 62519
Wow! Thanks slash for this!
I should mention, that I'm on Mac/QNAP so there are not so many clients. For QNAP only Transmission as far as I know.
In uTorrent/Transmission there is no setting for "report special IP to tracker", maybe this is a limitation on the Mac version or I have overseen it.
I changed the tracker to https://testnew.tribalmixes.com/announce.php and it shows my IPv4 IP and failure | NOT connectable| check1:IP4v|check2:IPv4
This is shown on both, Transmission and uTorrent.
At BitRocket I'm not able to edit the tracker.
BitTorrent is the same as uTorrent..
EDIT: Transmission on the QNAP NAS is just showing "Could not connect to tracker". Nothing else.
EDIT1: if I go to https://www.wieistmeineip.de/speedtest/ it shows me the IPv4 and IPv6 IPs
I should mention, that I'm on Mac/QNAP so there are not so many clients. For QNAP only Transmission as far as I know.
In uTorrent/Transmission there is no setting for "report special IP to tracker", maybe this is a limitation on the Mac version or I have overseen it.
I changed the tracker to https://testnew.tribalmixes.com/announce.php and it shows my IPv4 IP and failure | NOT connectable| check1:IP4v|check2:IPv4
This is shown on both, Transmission and uTorrent.
At BitRocket I'm not able to edit the tracker.
BitTorrent is the same as uTorrent..
EDIT: Transmission on the QNAP NAS is just showing "Could not connect to tracker". Nothing else.
EDIT1: if I go to https://www.wieistmeineip.de/speedtest/ it shows me the IPv4 and IPv6 IPs
slash ProDanceCulture
on March 6th, 2014
/ post 62522
i was quite high when i wrote that post, sometimes thoughts can go very far and wide and one can get lost in them... i didn;t, but took me a while there...
anyways, as the test showed, tribalmixes perceives you as ipv4, i do not know why and what, i had 2 checks there for your ipv6 - the client is not passing it to the tracker.
i understand you have ipv6 enabled, and some WWW (even tribalmixes.com) when http is used will possibly confirm your ipv6, here try this link https://testnew.tribalmixes.com/c16.php and post what you see, pls.. what i wanna say, is that i am high again... it's after work, i browse forums, relaxing... anyways, torrent communications - is one thing, they are performed by the client and the tracker, back and forth, so most likely, it is what client sends to the tracker - your ipv6 converted into ipv4. i read somewhere that even if teredo and ipv6 are enabled between two hosts, if ipv4 is available on both - it will be preferred, and teredo is only used when accessing an ipv6 machine. and then there's browser to website communications, and those can carry completely different set of "side-data"...
but really what i am thinking you should do is set up a local proxy on your own computer, and have that proxy convert all ipv6 into ipv4, and back... and client only works through that proxy.. something like that... to be honest, i am not that smart...
but the point is clear: connectable or not, it won't make any difference in how tracker treats you and your peers, because in truth, connectability is a very subjective notion, it can be good or not good depending on circumstances and stuff.. that is why we simply let you and that other guy, or rather yours and that other guy's clients decide what they can or cannot do...
anyways, as the test showed, tribalmixes perceives you as ipv4, i do not know why and what, i had 2 checks there for your ipv6 - the client is not passing it to the tracker.
i understand you have ipv6 enabled, and some WWW (even tribalmixes.com) when http is used will possibly confirm your ipv6, here try this link https://testnew.tribalmixes.com/c16.php and post what you see, pls.. what i wanna say, is that i am high again... it's after work, i browse forums, relaxing... anyways, torrent communications - is one thing, they are performed by the client and the tracker, back and forth, so most likely, it is what client sends to the tracker - your ipv6 converted into ipv4. i read somewhere that even if teredo and ipv6 are enabled between two hosts, if ipv4 is available on both - it will be preferred, and teredo is only used when accessing an ipv6 machine. and then there's browser to website communications, and those can carry completely different set of "side-data"...
but really what i am thinking you should do is set up a local proxy on your own computer, and have that proxy convert all ipv6 into ipv4, and back... and client only works through that proxy.. something like that... to be honest, i am not that smart...
but the point is clear: connectable or not, it won't make any difference in how tracker treats you and your peers, because in truth, connectability is a very subjective notion, it can be good or not good depending on circumstances and stuff.. that is why we simply let you and that other guy, or rather yours and that other guy's clients decide what they can or cannot do...
you cannot post in this forum.
click here to to create a user account to participate in our forum.
click here to to create a user account to participate in our forum.
Top 20 Torrents (last 5 days)» Deep Dish - Live @ Soho Garden, IMS Dubai Closing Party - 15-Nov-2024 » John Digweed - Transitions 1055 (Guest Jonas Rathsman) - 15-Nov-2024 » Hernan Cattaneo - Resident 706 - 16-Nov-2024 » Adam Beyer - Live from Mysteryland, Haarlemmermeer - DCR 745 [HQ] - November 2024 » Eelke Kleijn - Days Like Nights 366 - 18-Nov-2024 » Marsh - Live From the Hotel Californian, Santa Barbara - November 2024 » Miss Melera - The Boom Room 533 (Residentmix) - 02-Nov-2024 » N-TCHBL - Subliminal - 18-Nov-2024 » Atric - Live @ Tipping Point x Bahnwarter Thiel [HQ] - November 2024 » EnigMat (CA) - Addicted to The Underground 011 - 03-Nov-2024 » El Reyalto - Tech Coast Tribal - 16-Nov-2024 » Henry Saiz - Live @ CIRCUS XXI Aniversario Unico (La Plata, Argentina) 2160p - 22-Jun-2024 » Digital Department - Fatalist - November 2024 » Cream - Odyssey - November 2024 » Horst Haller - Live @ Kater Blau 3h Raketenflug im Acidbogen [HQ] - November 2024 » Dixon - Live @ Cercle Festival, National Air & Space Museum Ariane Stage (France) 2160p - 25-May-2024 » Kay-D - Mindfields - 11-Nov-2024 » HOVR - Live @ Boda De Muertos [HQ] - November 2024 » Nick Varon - VIBES 048 [HQ] - November 2024 » John Cosani b2b Martin Fredes - Live at Madrid - November 2024
Recent from the Forum (Be Social)» hey, lottery winners!!! post your testimonials!!! 1d 17h » ADE 2024 » Torrents Recommended for REMOVAL by Staff » Shoutbox features » October 11th - 13th 2024 Tomorrowland Brasil » September 14th & 15th Ultra Japan Tokyo » July 12th - 14th Ultra Europe » August 23rd - 25th Creamfields » BBC Radio 1 Shows from January 2024 » August 8th-11th Untold Cluj-Napoca
I changed my landline provider and just recognized, that they use a DS-Lite Tunneling. This means I'm not reachable through IPv4, only through IPv6. Because of this, It makes no sense to do a port forwarding for now.
Any ideas how to become reachable again? Or is it impossible?
Many thanks in advance!
brasax