I unplugged the cable to isolate the issue, to just the spider and make sure it is not related to my network and router…
What I do not understand is that why my spider receives a connection request while the cable is unplugged? Which is causing the exception since that request doesn’t come from a real IP address… So what is triggering that and where is coming from.
As for 4.2 I’ve been waiting for that for about a month since I started getting this error and I explained that in my first post, I have not touch the spider for a about a month. Also after inspecting the gadgeteer webserver42 source code I noticed it having the exact same code 4.1 has which is what prompt to start asking the question now.
Thanks.
Jay.
I guess we need more redbull and finish 4.2 already 
LOL maybe not more Redbull just less Beer ;)…
anyway, i found a way to stop the exception but i still don’t know why would this work…
in WebServer41.cs
public string StartLocal(string ipAddress, int Port)
//if i change this :
Host = IPAddress.Parse(ipAddress); //this return my Spider IP Address.
to this:
Host = (Dns.GetHostEntry(IPAddress.Any.ToString())).AddressList[0]; //this returns 0.0.0.0
IPEndPoint endpoint = new IPEndPoint(Host, Port);
i no longer get the exception and everything works as expected…
now the question is: why is it when the IPEndPoint contains the real Spider IP Address (HOST) i get the exception and when it contains a 0.0.0.0 i get no exception, and everything works as expected?
thanks.
Hi andre,
thanks for your testing…
it could take up to 15 minutes to get the exception… i’m still trying to figure out why when i bind my real DHCP Assigned IP i get the exception, but not when i assign it 0.0.0.0.
the only thing i could think of is how i updated the default Network Values (MAC and IP) with MFDeploy, maybe that has something to do with it…
i’m gonna reflash the spider and try it with the default values…
one last think can you please note your current DHCP Assigend IP and browse to your spider hello query and leave the browser open… go back to your C# and replace this :
WebServer.StartLocalServer(Ethernet.NetworkSettings.IPAddress);
with this:
WebServer.StartLocalServer("0.0.0.0", 80);//Ethernet.NetworkSettings.IPAddress
hit F5 and after the network is up hit refresh on your browser and let me know if that serves the pages from your spider…?
i just don’t know why when i bind 0.0.0.0 i still have access to my spider server… and this ran all night without a single issue.
thanks.
Jay.
Thanks for the update…
Ahh i see you are using your own implementation… the issue i think is related to Gadgeteer WebServer API…
if you don’t mind me asking can you please try the example i linked on my first post and report back… just open the solution and deploy browse to hello and wait … 10 to 15 minutes.
thanks.
Thanks and good luck with your release.
i will be using my temp fix until 4.2 arrives…
thanks.
re-flashing my board didn’t help either so i’ll be using my temp solution for now which is to bind 0.0.0.0 instead of the spiders DHCP Assigned IP Address…
i will retest when 4.2 arrives…
thanks.
Hello guys,
Some more updates on the subject…
there seems to be a bug somewhere for sure…
some background info:
i’m using Open Mesh MR500 routers (Cloud Controlled)… so basically if this router is set to DHCP and hands out the IP’s the spider throws that exception after about 10 to 15 minutes… but i disable that routers DHCP and turn it into a switch that just passes the IP from the Main router, the spider works as it should without any exceptions…
now the question is why does it hang and throws that exception when it gets it’s IP from MR500 OpenMesh router… if anyone knows please let me know…
if i have more info i’ll let you know…
thanks.
Jay.
