10 replies to this topic

[Anshul]

What's the proper method to check if the ethernet cable is connected, or if the Netduino+ has an IP Address, or both? Thanks

[Nathan Baker]

Hrm, this is a good question. I have to do this at some point to make my client more stable, just been lazy.

[Chris Walker]

Hi Anshul, If you're using DHCP, you can check your current IPAddress through the NetworkInterface object (in Microsoft.SPOT.Net). Chris

[clem0338]

Hi, I know that i'm digging an old thread but I have the similar question and I must manually set the IP address (so no DHCP). Is there any way to do it ? Thanks. Cédric

[Nicky]

Except from NetworkAvailbilityChanged event, which cannot be used to detect the initial state, I suggest making somekind of request, wrapped in a try-catch ... if it fails, no network.

[clem0338]

Except from NetworkAvailbilityChanged event, which cannot be used to detect the initial state, I suggest making somekind of request, wrapped in a try-catch ... if it fails, no network.

Thanks,

but it is exactly what i don't want. Let's explain myself:
The network can be down or unplugged.
When I'm trying to do the Socket.Connect, my ND+ is totally stuck (and all my threads ...)
It seem's to be a well known bug (corrected in MF 4.3 beta)
http://netmf.codeple...m/workitem/1396 for more info

So, i'm looking for a way to "check" the network before Socket.Connect even after boot up ...

Thanks anyway, regards

Cédric


Edit:
More info
http://netmf.codeple...m/workitem/1181
http://www.dotnetsol...word-of-warning

Didn't work with 4.1 neither 4.2 (Flashed for this bug)

I still have an IP address in memory even unplugged (DHCP trick)

[andybareweb]

Hi,

I know that i'm digging an old thread but I have the similar question and I must manually set the IP address (so no DHCP).

Is there any way to do it ?

Thanks.

Cédric

Hi Cédric:

var interfaces = Microsoft.SPOT.Net.NetworkInformation.NetworkInterface.GetAllNetworkInterfaces();
                foreach (var networkInterface in interfaces)
                {
                    Debug.Print(networkInterface.IsDhcpEnabled ? "Dhcp Enabled" : "Static Ip");
                    Debug.Print(networkInterface.IPAddress);
                    if (networkInterface.IsDhcpEnabled)
                    {
                        networkInterface.EnableStaticIP("192.168.0.9", "255.255.255.0", "192.168.0.1");
                    }
                }

This prints out whether you're already Dhcp Enabled or Static, and if Dhcp it sets to static.

You'd probably want to be a little cleverer around releasing leases if you want to be friendly to your dhcp server, but otherwise the above works.

Regards
Andy

[caEstrada]

Use any network operation inside a {Try/Catch} and then, check the Exception Value and Message, works perfect.

[Nobby]

One method I use is to create a socket which is a listener using IPAddress.Any for the binding. The listener will be created if the network is up or down but you can call Socket.Poll(). It will throw a SocketException if the network is down with an error code 10050. The only time this approach fails is if you power the ND+ up and it initially isn't connected to the switch/router. There's some bug which is apparently being fixed in 4.3 where network connectivity to the ND+ is impossible under this start-up condition but the ND+ internally believes connectivity is fine after you plug the network cable in.

[clem0338]

Many thanks for your answers and please, excuse me for the while I took. To andybarweb: I may be static IP or DHCP (from configuration file on SD). I don't want to force a static IP To caEstrada: Already in a try/catch. The problem is Socket.Connect never returns even with an exception To Nobby: This can be an half way solution. This will be OK for the ethernet activity test but, if my server is down, the problem's remains. Thanks to all. Cédric

[Nicky]

Did you set a SendTimeout on your socket before trying to connect?