Feature requests for stack

[gsxrex]

Please post here if you have feature requests for the stack. This will make it easier to see all the requests, and we can prioritize what we can/can't do.

[gsxrex]

- Port existing Ethershield library to run using WiShield. *Note that this will require an ATMEGA328.

- Have print capability similar to Ethershield to make dynamic webpage creation easier

- Currently, sketch only supports 128-bit WEP. We need to bring up the support for 64-bit WEP out of the driver (although, you really should be using WPA in the first place anyway )

[peterM]

Error reporting.
Maybe this is enabled but not yet documented? It would be useful to have feedback on the progress of making and maintaining a connection, being able to catch the result of key actions (log-on, etc). I'd like to enable my own "status lights" in addition to the current red LED connection indicator.

[peterM]

And also, here's another vote for a Client mode.
I envision the wishield doing its own polling & posting to a specific known web site out in "the cloud", not in a LAN.

[shard7]

Big second on Client mode, I need the ability to send email messages or post Tweets.

[gsxrex]

@peterM
You can do more error reporting/status, but the unfortunately thing is this will eat up lots of resources with all the Serial.print() statements all over the place. Since we are already running really low on space in the 168, we tried to keep everything to a bare minimum. Maybe if we just document where you'd insert your code to turn on your own LED array or print a message, then users can elect to do as much or as little as they want.

Client mode is coming. We're working on that now. Then you'll be able to autonomously send http requests wherever you want. For email, you'd need a smtp service, which is neither http server or http client.

[peterM]

@gsxrex
Yeah the Serial.print() thing is unsuitable for me long-term anyway (my objects wont be connected to a computer). Hooks in the .c where LED calls can be made would be super.
Looking forward to the client mode, when you get around to it <phew!> (btw, my particular app wont need email).
Thanks for all the great feedback...

[zhobbs]

@peterM
You can do more error reporting/status, but the unfortunately thing is this will eat up lots of resources with all the Serial.print() statements all over the place. Since we are already running really low on space in the 168, we tried to keep everything to a bare minimum. Maybe if we just document where you'd insert your code to turn on your own LED array or print a message, then users can elect to do as much or as little as they want.

Client mode is coming. We're working on that now. Then you'll be able to autonomously send http requests wherever you want. For email, you'd need a smtp service, which is neither http server or http client.

Docs on how to check on the network status would be great. Right now if I restart my wireless router the red led turns on and off, but the web server in the WebServer example sketch stops responding unless you reset the device.

[benquark]

ARP client to enable periodic interaction with the AP to prevent disconnection from the WiFi network.

[rpowell]

Can we get an example ntp sketch.

Also can we make a change to to uip-stack so that prog_uchar wep_keys[] PROGMEM is not defined as a const but is instead profiled in.

Can we also change:

unsigned char security_type = 2; // 0 - open; 1 - WEP; 2 - WPA; 3 - WPA2

to be #defined. This wastes code space. We can then profile in the wep_key.

Thanks