This works fine, unless I take out the ethernet cable. In that case, the Socket.connect call hangs forever.
I have googled a bit about this and it seems I’m not the only one who has experienced this behaviour. However, if I understand correct, this should be fixed in version 4.2 of the SDK.
This leeds me to two questions:
Is there a way around this in 4.1?
Could I upgrade EMX to 4.2 at this time? As far as I can tell, it’s not completely ready for EMX right?
Of course it is possible. 4.2 has a complete different TCP/IP stack and things should be better. The only problem here is that 4.2 is a release candidate still and new stack could mean little problems here and there. We are fully concentrating on this.
Thanks Gus, I will give 4.2 a try.
I was a bit confused after reading this info from the NetMF 4.1 to 4.2 Wiki:
Now, for the answer! We now have a little problem, 4.1 is complete but not all module drivers were built for 4.1 so they are only available in 4.2. To add more confusion, our gadgeteer SDK installs 4.1 and 4.2 currently! This will be all resolved and 4.2 is the answer in few weeks but till then here is what you need ot know:
If you are using a System-on-Module (USBizi, EMX, ChipworkX) then keep on using 4.1
If you are a gadgeteer user and need WiFi then keep on using 4.1
If you are gadgeteer user and do not need WiFi then 4.2 beta is recommended