Ok, there have been a number of people who can't connect with this version of the lib, following are some basic troubleshooting points for the current version of the lib (0.3 ONLY - later versions will fix several of these points)

But, before all that - check your router's compatibility on nintendo's wifi site: http://www.nintendowifi.com/ - if it's not compatible there it's probably going to cause you grief.

Problem:
Can't see any access points, but they were there in an earlier version (v0.2)
Probable Causes:
* this is probably a bug in the lib, I'm looking for it..

Problem:
Hangs at ASSOCSTATUS_SEARCHING
Probable Causes:
* your router has SSID Broadcast disabled, this must be enabled for the current version of the lib, though it is planned to be fixed in the next version.
* your router may be off.... well, it might be!

Problem:
Hangs at ASSOCSTATUS_ACQUIRINGDHCP
Probable Causes:
* your router is denying the lib's DHCP request; I've seen this on a few routers and am looking into it.
* You have the wrong WEP key or mode configured.

Problem:
Fails to connect (ASSOCSTATUS_CANTCONNECT)
Probable Causes:
* Shared key authentication is enabled - the lib does not support this yet but it is planned for the next release.
* your router has a configuration that is blocking the DS from connecting. (MAC filtering, or etc..)

Problem:
Connected OK but can't send/receive data!
Probable Causes:
* WEP could be incorrectly configured.
* IP address may be manually incorrectly configured.
* Router may be incompatible!


If you guys have other problems connecting, please post them here - I'm sure there are other issues I haven't documented. I'm listing just the problems I know about at the moment.

As always, good luck
-Stephen

I have this problem. But, if I disable my wireless usb adaptor on my pc, i'm able to connect to my router just fine. I can then re-enable the adaptor and not have any problems.

Thanks Stephen, it's always good to have a FAQ that clearly lists the problems and solutions!

Well done!

Here is the problem I have: My DS connects to Nintendo Wifi just fine. And, your wifi-lib detects my AP too. But it won't connect to it at all. I'm broadcasting my SSID but the name doesn't appear when it detects my AP. Any ideas as to what it could be?

Any help??

And what about this error, but happening randomly ? (seeing it works everytime with WFC games)
Router i'm using: Netgear DG384G

With packet captures, i'm able to see that it doesn't send anything (not even ARP).
It happens even with WEP disabled.

754boy: you have either a problem with open system authentication (which will be added in the next lib), or your configuration isn't set up the way you think it is - due to your explanation I can't tell which it is.

thoduv: what kind of packet capture?
I'm not sure what your problem is yet.

Network packet capture (using ethereal). I'll try to do a wireless one, but I'm not sure of what kind of software to use...

Thanks for your reply. I will keep tweaking my setting and if all else fails, I'll just wait until your next update

hey i have tried several ds wifi programs such as dsremote and pointy remote.

i am using a ds lite with a superkey and a sd supercard

i am copying the.nds files to my sd card then run the server applications

when i start the programs i stop responding after it goes

"Waiting for ARM& to init..
ARM7 init confirmed."


i am new to this

any help will be appreciatied

khalil.

khalil: could be a failed connection due to lack of shared key authentication support (mis-stated in previous posts, heh), or because your access point isn't broadcasting a SSID. Beyond that it's hard to tell

-Stephen

I think your using the normal .nds file, and supercard requires you to use the .ds.gba, but renamed to .nds.

thanks this solved my problem.

I think I also have problems with the open authentication system. But not sure. NWFC runs perfectly well using shared weg (128bit). And open non-wep also works, but open wep, either 64 and 128-bit, wont work. I'm able to connect to an ap, but then I don't receive any data (tried dns query and stuff).

I have a problem connecting with dswifilib. I downloaded version 0.3a and tried the wifi_lib_test app, but it will not connect to the access point. It stops at ASSOCSATUS_SEARCHING. I tried using WFC settings and manually. Wardriving will not see any access points either, even though I know there are a few in radio range. Packet capture does not capture anything. The wifi_example program cannot connect, either.

I have tried other homebrew too. DSMail does not work, but strangely DSOrganize can connect. I'm not sure what the difference is, since it uses dswifilib as well.

Official games can connect and use wifi without a problem. I am using a DS Lite (in the US, if there are different regions) with a EZ Flash 4 Lite.

I have tried compiling my own copy of dswifilib and testing apps. The wifi_example app does not work (will not connect; same as provided binary), and the wifi_lib_test app will not compile (missing ascii_bin.h).

Any thoughts?

Problem:
Hangs at ASSOCSTATUS_ACQUIRINGDHCP
Probable Causes:
* your router is denying the lib's DHCP request; I've seen this on a few routers and am looking into it.
* You have the wrong WEP key or mode configured.

I was able to fix this by manually adding my client manually to the DHCP settings in my router, instead of setting it to auto.

I have the same problem using M3 minsd on DS clasic, the strange thing is that I was able to connect but only a few times... this is not a router problem because my original mariokart can connect without problems to my router.

I was trying to use beup but the problem happens, after adding another accesspoint to WFC, beup ran with no problems but after reset the same problem happens and adding more accesspoints did not help. After that, I tried deleting the WFC data in firmware (using MarioKart orginal) then I tried beup and it works again.. but after two resets the problem happens again.. since that I cant connect to my router. I've got the same problem with the two examples in wifilib, so I think it is a bug in the lib.

I was trying to do some debug and I found that in someway the lib doesn't initializate correctly... for example: when I call Wifi_GetData(WIFIGETDATA_NUMWFCAPS,...) returns the correct number of APs in WFC but Wifi_GetNumAP() returns zero and thats why the lib keeps in searching state... I will try to do more research and post it if i found something

same problem here using G6 Lite on DS lite.

Are you able to connect with DSOrganize?

i'm afraid i'm not able to get DSOrganize to work with my G6 card.

Same problem here (ASSOCSTATUS_SEARCHING).

EZ3Flash + EZPass3

I know the router works with original games. (Netgear WGR614v5)

Do you guys know if it was working before?

NUMWFCAPS is not the same as GetNumAP! The first one is the number of APs you have configured in retail games on your DS. GetNumAP is the number of APs that were found by the scan. No?

I erased all WFC settings and then added a new AP. After this, any program using wifilib works(beup, wifi test,...), but after another reset, it doesn't work anymore until i erase all WFC settings again.

I'm not sure I understand. You erased all WFC settings in a commercial game and added back an AP in that game, then loaded a program using the wifi lib? How can you "not reset" between the time you add a new AP and the time you load a wifilib program?

Also, would it change anything to flash my DS firmware???

It works!!! I flashed my DS Lite (flashmev7) and dswifi now works!!! Connects successfully to my router and everything. Wouaaou!!!!!

i do a soft reset after i add a new AP in the game. then i load wifi_test. it works. After that a hard reset is needed. After that, wifilib doesn't work anymore.

I just reflashed my DS Lite with FlashMe V7, and wifi now works!

It is somewhat annoying that the wifi lib does not work properly with the stock DS Lite firmware, but at least it can be noted as an issue. I still wonder why it worked for DSOrganize and nothing else.

FYI, I got flashme v7 from:

http://forums.maxconsole.net/showthread.php?t=28470

If you have an EZ-Flash 4 Lite, you do not need to use the EZ Client software to transfer the flashme file, but you have to rename the flashme.nds to flashme.bin.

What's weird is that I tried the sample program on my friend's DS Lite (not flashed) and it worked for him, exactly the same setup... (same router, same flash cart, same ezpass, etc.)

Im quite desperate now.

I got a DS Lite with Passcard3 & G6 Lite. I tried beup and it didnt work. Then i tried both (.nds and .ds.gba) wifi lib tests and nothing is working. Wardriving gives me nothing, finding an AP also nothing.
The weird thing is, WFC works flawlessly. I found like 40 AP's during a 10min ride yesterday. After doing the same ride with the wifi lib testit gave me zero results.

How is that even possible?
The weird thing is that it doesnt even connect to a WFC AP which works fine in mario kart and tetris... Anybody knows a solution for this? I want to use beup....

Update:

After flashing my DS Lite with the v7 firmware wifi lib is working. I can connect to a few AP's but nothing is working. DNS is not working or anything. Wardriving and packet scanning is working fine.

Beup is getting to the handshaking part and then hangs on that. I am sure i am using the latest version.


Anyone knows what can be wrong?

Oh, and btw : WFC is connecting to my router fine but wifi lib test cant connect using that data. Thats weird...?

I also have the problem where Nintendo WFC works (with WEP), but homebrew applications using this lib will not when WEP is on; they will if it's off.

However, that's with my router, a sitecom wl-114 (version 1). I tried it at someone else's place, and there the connection DID work, with WEP and all (a Belkin router).

So, it's related to the router, but it remains odd that everything else works normally. I can't find anything weird in the settings either....

*update*

I replaced my Sitecom router with one from Belkin (for various reasons) and now programs using the wifi-lib work fine here too.

it remains a little odd though that some routers do not work with homebrew where others do....

Has anybody figured out what's wrong with the library when connecting to certain routers?

going to post this as a new topic

Hi,there is a problem here.

I use Nintendo wifi usb connector, can run official wifi games with no probelm.

but when I want to use wifi_lib_test 0.3 to connect the connector by "use nintendo WFC data",it prompt

"cannot connect to Access Point",search for an AP cannot find the ssid of the AP, (I have configured SSID )

what can I do ?

plz tell me,thanks.

I'm having trouble connecting through my router using manual settings or WFC settings. Here are the results of a few different wifi_lib_tests.

Version 0.3 Build Date: Apr 24 2006 14:55:12
Does not see my SSID, just neighbor "IBob"

Version 0.3 Build Date: Apr 24 2006 14:55:12
Does not see my SSID, just neighbor "IBob"
When connecting to AP using WFC settings, hangs at ASSOCSTATUS_SEARCHING

Version 0.3a Built Date: Jan 10 2007 23:11:18
Sees my SSID, and 3 of my neighbors', including "IBob".
When connecting to AP using WFC settings, hangs at ASSOCSTATUS_AUTHENTICATING; eventually says "Cannot connect to Access Point"

Router: The router is a Linksys WRT-54G.

DS Lite: Original v5 firmware (I have not re-flashed it). Ran tests using R4 (v1.07). I can connect fine using any of my WFC cartridges or backups.


Any suggestions that don't involve re-flashing my firmware? (When I develop a Wifi game, I'd rather not ask people to potentially brick their DS)

Thanks!

Try forcing your router to 802.11b mode, it worked with my Action Tec MI424-WR. Using wifi lib test in war driving mode it saw my access point but showed 0% signal strength.

Good luck.

I found that on newer DS Lite homebrew WiFi works only using wireless radio channel in between 5 and 11.
Could someone test/verify this found ?

Thanks

dm

I found and fixed a bug in the DHCP messages in dswifi (at least present in dswifi 0.3.2 and most likely in earlier versions). I did this by running a packet sniffer on my laptop to see the DHCP packets between my ds and my router.
The client address field was not being padded/initialized with zero bytes before filling in the nintendo ds mac address. If the router looks at the entire field (all 16 bytes, i.e. the mac address and the next ten bytes too), then two subsequent DHCP messages would look like they come from different clients - my guess is that the router would reject/ignore them.

The dswifi developers have already committed my patch to cvs so this will be fixed in dswifi 0.3.3 when it comes out! So we just wait for dswifi 0.3.3 now ..

Try using a more recent dswifi version! 0.3d came out a while back and 0.3.2 is now out too (0.3.2 is part of devkitpro so if you just use the regular devkitpro updater you should already have 0.3.2). I fixed a bug in 0.3.2 (so if 0.3.2 doesn't work with your router either, then wait for 0.3.3 to come out!). Email me privately if you would like me to mail you a test build of 0.3.3

Hi, new here, hope I'm doing the right thing posting this here instead of in a new topic..

This is my problem:
Connected OK but can't send/receive data!

I have a DS Lite (bought in Japan, but I don't think that matters?), a Thompson SpeedTouch 716 router, an R4 v1.10 and wifi_lib_test 0.3.3. I can connect to the AP, but nothing is sent/received. Non-homebrew WiFi works like a charm. I'm using 128 bit WEP, shared key and DHCP, but I've tried static IP and no WEP as well without success.

I would really appreciate some help interpreting the test program results.

I'm at work at the moment, so I'll try to describe my results from memory and I'll update this post tonight.

* UDP Test
-

* DNS Test
- DNS seems to work

* TCP Connect Test
- I'm not sure what's supposed to happen
I can connect to the AP at work and use the web browser in DSOrganizer 3.05, so I assume this is working.
If I try TCP Connect at work, I get:

Resolving host...
port 80
T : <hex a> <hexb> 0800
R : <hex b> <hexa> 0800

Not sure what 0800/0806 means, but I assume this is me, <hex a> connecting to <hex b> and getting a positive response?

* TCP Listen Test
- Not sure how this is supposed to work, does it just open a listen socket and it's up to me to try to connect? I'll try this when I come home tonight.

Any other suggestions on what I could try? Anything I've forgotten to mention? Please help!