Infinite Recursion

I might be able to do this for a future release, if I ever get time to work on it again. IR-GTS doesn't like file paths that have special characters in them, notably accented letters (like the ö in your attached image). Sorry, it's not particularly international-friendly. To fix this, you should be able to either move the files to a path that doesn't have characters like that, or change the ö to an o. What's your OS?

Minor update: IR-GTS-BW v0.05 will now show the filesize when it detects an invalid input file. It also adds a bit of text to statlog.txt if the retrieved Pokemon has a Dream World ability.

Your firewall is blocking the external connection. Anything internal will work, and anything external will not; it wouldn't matter which version of IR-GTS you use. New releases available! This one should fix the stat oddities previously mentioned when sending a 136-byte pkm to the game. I've also changed README.txt to be a URL for the IR-GTS wiki, so I can keep it better updated. IR-GTS v0.43 and BW v0.04 are now up on the Google Code site.

I think I've figured out what the problem with incorrect stats is. When I reordered the output of statlog.txt, I forgot to reorder the inputs for another function used in boxtoparty.py. I'll have that fixed in the next version (it applies to both releases), coming soon. Have a look at this page. The error comes before the DNS spoofing comes in, so it probably is a problem with Nintendo's GTS servers, or your connection to them. As for the ports that IR-GTS uses, it's only 80 and 53. Try running it in Safe Mode w/Networking, as paperfairy was doing, to see if that fixes the error. Both Pokesav and Pokegen should work, though I haven't used either personally.

Have you tried depositing the Pokemon into the PC and retrieving it again? If not, it may be a problem with the 'boxtoparty' function within IR-GTS. Otherwise, IR-GTS doesn't change the .pkm file at all, so what goes in will come out on the DS. Can anyone else confirm this issue? Also, sorry I've disappeared from the forums the past few days. I've been pretty busy with class and work, and I have a job interview coming up that I've been preparing for. Thanks to everyone offering assistance in this thread!

What happens when they try to connect? Do they get any errors on their DS? My guess is that your firewall is only set to partially allow Python, which would explain why you can access it on your local network, but others can't from remote networks. Make sure that Python is completely allowed through the firewall. Also updated the OP with a link to the CommonIssues wiki page. Keep an eye on that if you have problems with the program. At this point, it works for most people that are using it, so any problems are likely confined to the computer/network using the program. If you run into an issue not covered there, or if the solutions there don't work for you, let me know and I'll try to help to the best of my ability. Another quick note: if you're getting error code 13275, there's really nothing that can be done about it, aside from trying again later. Nintendo's GTS servers have been having problems recently (and who can blame them, really?), so that is almost certainly the issue with that error.

You'll have to be more specific than that - do you have a link to this conversion tool? If it just changes the file size, it won't work properly. There's actual data within the .pkm file that needs to be changed. Based on what you've said, it looks like at least the nickname/OT name was not converted to the new format. I'm pretty sure both Pokesav and Pokegen can do 4<->5 conversion.

What's the version number that IR-GTS reports? Wait, so you sent this .pkm to your DS? Did you do conversion from GenIV to GenV first? IR-GTS-BW doesn't do that yet. It won't do that by default, but you can get it to send one .pkm repeatedly by changing line 90 of sendpkm.py ("while not sent:") to "while True:" Note that Bond has been having trouble with it dying after a while when using this variant. IR-GTS is mostly meant for one-shot sending/receiving; it doesn't do sustained transfers very well, unfortunately. Something to do with how it's handling its network sockets, but I'm not sure what I can do to fix that. Check the OP.

You can do it, certainly, you'll just have to ignore the DNS that IR-GTS tells you to use. Instead, use your public IP. Sites like whatismyip.com can help you find this. IR-GTS v0.42 and IR-GTS-BW v0.03 now available. BW was logging incorrect natures into statlog.txt; fixed that, and changed the order of EV/IV output for both versions. What is its actual nickname, in-game? Could you send me a copy of the .pkm that IR-GTS-BW created for you? I'm curious why that's happening too.

Hah, they must have changed the location data; it used to be East Midlands, England. Were you sending or receiving? If sending, could you send me/post the .pkm you were using? If receiving, what was its nickname?

Do you have a guest network setup through your router for your DS? If so, is there a DNS option in the configuration for that? If so, try setting that to what IR-GTS tells you, and let me know if that works.

If possible, try putting the DS and computer on the same network. Otherwise, try forwarding port 53 and 80 to your computer and connecting to your external IP. If you have a guest network setup through your router, it may not work. Can anyone confirm whether they got it working with this setup?

Tried something to see if it would fix the problem with connecting to the real GTS. It's no longer available, since it didn't work, and I wanted to avoid that solution. At least one person found that their DS was connecting to a different network than the one their computer's on. Try deleting all other connections in the DS options if you're getting forwarded to the real GTS. This has also failed for others, so YMMV. Edited the OP to note this issue.

For those that are getting to the actual GTS, make sure that you put your computer's IP into the first DNS slot. If that doesn't work, say what happens (Communication error, IR-GTS crash, etc.). Also check to see if the IP that IR-GTS gives you is the same as your computer's. I'm really curious as to how this is happening, because it shouldn't be possible if the DS is sending DNS requests to the computer running IR-GTS. If you're using a USB device or something similar for DS connectivity, though, that may be the problem. In that case, try setting your computer's (not the DS') DNS to 127.0.0.1 while using IR-GTS. What happened when you tried with a longer name? There might be something wrong with how it reads in filenames. If the filename has actual Japanese characters, though, it almost certainly will not work; you'll have to rename those using Roman letters.

Updated to v0.02. See OP for details. For those with Macs running into the 'reserved keyword' error, let me know what version it shows if you type in '/usr/bin/python' into the Terminal. If that is anything less than 2.7, try 'whereis python' and post the results. I'll be fairly busy for the next few days, so I won't be able to check this thread very often. I'll answer the questions I can, but I can't make any guarantees. I'll try to keep the OP updated with a list of common problems, so keep an eye on that as well.

Try opening a Terminal, then entering 'chmod +x ' then dragging ir-gts-bw.py into the window. That should allow you to execute the file by double-clicking on it. Otherwise, you can run it straight from the command prompt, if you cd into the IR-GTS directory first. Would it be possible to try connecting the PC to the same network as the DS to see if that works? I'm guessing the guest network is the problem here. Based on that warning, it looks like it's using a version older than 2.6. Try uninstalling all versions of Python and reinstalling 2.7.1, see if that helps.

I'd actually recommend installing 2.7.1 from here. After that, you can just follow the instructions in the readme to get IR-GTS-BW to work.

I assume that when you drag the file into the window, it adds quotes around it? That should be a fairly easy fix if so, I'll work on adding that in soon. Are you able to get into the room at all? I know that was a problem I had initially with the old code, but was able to fix it. Make sure that you have IR-GTS-BW, rather than IR-GTS.

Made a new thread for IR-GTS questions here

Making a new thread for this to avoid clogging up the GTS Research thread with questions specific to IR-GTS-BW. Download available here. Note that IR-GTS-BW is a separate release from the GenIV version, and is currently on version 0.05, rather than 0.43. -Japanese character support is currently unavailable - haven't been able to test what happens when you try to send a Pokemon with a Japanese nickname/OT just yet. Added a placeholder in lieu of proper Japanese character support in v0.02. -GenIII and GenIV Pokemon files are currently unsupported. For a list of common errors and possible solutions, see http://code.google.com/p/ir-gts/wiki/CommonIssues Several people have been connecting to the actual GTS, despite inputting the DNS settings correctly into the DS. I'm not yet sure what is causing this, but am looking into it. Make sure the DNS settings that IR-GTS tells you to use are entered into the primary DNS slot on the DS. If you are using a USB device to connect your DS to the internet, try setting your computer's DNS to 127.0.0.1. Otherwise, try deleting all other connections in the DS settings, as it may be accessing a different network than the one IR-GTS is running on. Also make sure that your firewall is set to allow Python. If you run into problems not covered here, let me know when it failed (e.g. after first entering the GTS room), which function you were trying to use (send/receive), the OS on your computer, and what error you're getting - preferably from Python (run from a command prompt if the window closes before you can get an error message). Also, if you're trying to send a pkm when you get the error, it'd help if you could post that as well. NOTE: Read the Readme before asking for help. Otherwise, your request will be ignored. Thanks, and enjoy! Changes: v0.01: Initial Release v0.02: Japanese text placeholder. Now uses the PID as the nickname, and 'TRAINER' for the OT. Now removes quotation marks at the beginning and end of the filename, to make dragging and dropping easier. v0.03: Statlog.txt now reports the correct Nature. Also reordered the IV/EV output. v0.04: Fixed the stats generated for a 136-byte pkm file, which were broken by the previous release. v0.05: Shows the filesize of invalid files, and detects Dream World abilities.

Even better, I now have a preliminary release! I've finally got (most) everything working. I have successfully sent and received a Pokemon from White. Everything is nearly the same, with a few caveats: -No support for GenIV .pkm files or GenIII .3gpkm files yet -Japanese name parsing has not yet been implemented. Not sure yet what happens if you send a Japanese pokemon to your computer. I'll work on a placeholder tomorrow, so the filename isn't completely unreadable. Note that this is essentially a 'beta' release, so you may run into some problems that I haven't noticed yet. If you do, please let me know via the email address in the README.txt file. Get it here

Thanks to some help via IRC (was missing 16 padding bytes between the pkm and GTS data), I've successfully sent a Purrloin to my DS. Almost finished.

That's where I've been getting most of my information, between that and this page. I've got all of the GTS-specific data in place, I just need to be able to properly encode/decode the actual Pokemon data.

You do not need an external IP to make this work. I was able to successfully get into the fake GTS after adding 'socket.shutdown(SHUT_RDWR)' after every response is sent. Now that I have that out of the way, I should be able to finish IR-GTS-BW within the next week or so. Looking at the descriptions of the DPPT and BW .pkm structure, it looks like everything is in the same place, with the exception of the last few bytes of a party Pokemon. Is the block shuffling/encryption algorithm still the same? Haven't been able to find anything about that.

Turns out I was completely wrong; I think I may have figured it out. Killing IR-GTS, then restarting it immediately picks up the second packet from the DS. Looks like the connection wasn't closing properly, which caused the DS to time out. Getting closer...