Jump to content

Recommended Posts

Posted
Hey! I'm working on an UDP chatserver on winsock to communicate with the UDP experimenter. The only problem is that messages sent from the pc to the ds, that have an odd amount of letters (such as 3, 5, 7, 9 letters), result in an "UDP receive checksum incorrect" message on the ds. Messages with an even amount of numbers (2, 4, 6, 8 letters)  do get through  :-).

Is it my bad programming or a bug in the experimenter?

 

Anyway, I'll release the chatprogram/server soon (will be able to act as a remote for winamp!).

 

Hi, I know there is a problem receiving odd sized packets. My solution was quite simple (I wrote the transfer program for the DS): use even sized packets, adding some padding to the end (at that point having the first two bytes of the packet to indicate the size of the actual data in the packet).

 

This worked out fine to me. I instead have problems when sending packets from the DS to the server: after a while the DS will simply stop sending them (on both my program and Sgstair's).

Does anybody has the same problem or is it particular to my configuration?

I talk about sending packets for 2/3 minutes, not a few seconds.

 

Bafio

  • Replies 39
  • Created
  • Last Reply

Top Posters In This Topic

Posted

yes, checksum problems with odd-sized packets are a known issue. I'm working on this, next version will have it fixed.

 

-Stephen

  • 2 weeks later...
Posted (edited)

Bit the bullet and applied the Australian firmware..... Why do people always make things sound harder than they are? It's just a normal firmware update but the router's IP changes to 10.1.1.1 after the update... big deal!

 

It's all working fine now. Including the wifi lib test app :)

 

It was this email from Dlink that made me go ahead with the Aus firmware:

 

I'm sorry there are no plans of releasing a Nintendo DS compatible firmware in the UK.

Using another country's firmware will indeed void the warranty.

For returns or replacements contact your reseller

 

I was going to take it back and exchange for a router that works but got lazy.

Edited by LargePig
  • 3 weeks later...
Posted

Wow, this is awesome. I turned on my DS and put this into wardriving mode, and left it on in my pocket while I was at school and walking home. By the time I got home, it listed almost 115 netrworks.

Posted
Wow, this is awesome. I turned on my DS and put this into wardriving mode, and left it on in my pocket while I was at school and walking home. By the time I got home, it listed almost 115 netrworks.

Its very sensitive. I can see around 5 networks right now, and my laptop only sees 1.

 

At home, I can see my neighbor's router, whereas regular laptops cant.

  • 4 weeks later...
Posted
Wow, this is awesome. I turned on my DS and put this into wardriving mode, and left it on in my pocket while I was at school and walking home. By the time I got home, it listed almost 115 netrworks.

Its very sensitive. I can see around 5 networks right now, and my laptop only sees 1.

 

At home, I can see my neighbor's router, whereas regular laptops cant.

 

Here in the UK, a sort of circular drive around the city of Bath got me exactly 200. rad :huh:

 

Not sure about the signal detection though, some networks I was miles from at the start of my trip got stuck at 7% signal when there blatantly should have been none :blink:

 

Very cool!

 

Rat

Posted (edited)
I’ve fixed the WEP support in the Wifi driver so that it can authenticate with APs that use Shared Key authentication.

 

Usage:

iwconfig nds channel <N> essid <ESSID> key <wepkey>

 

Thanks go to sgstair and the ethereal dev team.

 

Update: It looks like only 64bit WEP is working.

 

Update 2: 128bit WEP in the next build.

Pepsiman added WEP 64bit support to his DS Linux project!

http://www.dslinux.org/blogs/pepsiman/

 

 

i hope sgstair releases the new wifi lib test soon :P

and after this release WEP 128 bit support.

YAY i love u sgstair!

Edited by Öhr GmbH
Posted (edited)

Yes, thats cool, I have tested it, it worked the first time for me (the original lib didnt even work for me, when i disabled WEP).

And as an addition: WEP 128 works now, too (as of 20.02.2006). There was an error in the documentation.

I hope, pepsiman helps you to add these changes into the original library, so I can continue developing with your lib ;)

Edited by FloFri
  • 2 years later...
Posted (edited)

Is there any guide to how to know what is what? Primarily what I want to know is how to see which connections are open (that i can connect to) from the wardriving menu. I would approciate any help.

Edited by kallelej
  • 3 years later...
Guest
This topic is now closed to further replies.

×
×
  • Create New...