2 replies to this topic

[sjmill01]

Hello,

 

I've tried many options, but still can't ping my new Netduino 3 from the command prompt and my router cannot see it as an attached device. 

 

I have a WEP router acting as a switch and another router with WPA-PSK [TKIP] + WPA2-PSK [AES] acting as a router to the WAN.

 

When I try either WIFI access point using MFDeploy, I get an amber, then steady green light on reboot, but it doesn't seem to authenticate.  The passphrase is correct for the WPA.

 

For WEP, the Network Key seems to have a mind of its own and flips itself back to 2048-bit and adds a bunch of zeros.  My WEP key is set at the router as a 64-bit hexidecimal number 10 digits long.

 

 

I don't know what ReKey Internal is so I'm leaving it blank.  

For Authentication type, I've tried from None to Shared with no luck.

 

 I have deployed a "hello world" solution to it.

 

Any thoughts?

 

Thanks,

Sean

[sjmill01]

I guess I just had to post that I had to problem for it to fix itself.

 

It now works.  After posting, I redid my settings to WPA with an authentication of EAP and stared blankly like Neo at the screen.

 

Then I realized that my Hello World routine ran.  It then pinged.

 

So, I guess problem solved.  Perhaps, I was just too impatient because I saw green and expected it to be ready to ping.

 

Sorry for the false alarm.

 

Thanks,

Sean

[Chris Walker]

Hi Sean,

Yeah, sorry, the WEP key setup in MFDeploy is a bit confusing. If you use WPA/WPA2, it's much simpler.

Plus...with open WEP networks (by spec) you can connect (green LED) without fully authenticating or getting an IPv4 address allocated--which makes things even more confusing.

Glad you're up and running; let us know if you run into any other troubles!

Chris