Dixon

Hi Netduinerd, You have to declare the switch as InterruptPort, so you will receive an event whenever it changes (as you receive interrupts with serial communication): Private WithEvents SW1 As new InterruptPort(Pins.GPIO_PIN_6, true, Port.ResistorMode.Disabled, Port.InterruptMode.InterruptEdgeHigh)

We could also add a Reset feature to a future firmware release. The function is already built into the firmware...we'd just have to create a wrapper for it. You could also create one and build it into your own custom firmware.

The firmware could also be tweaked to activate the hardware reset function in case an exception occurred. Lots of options.

Hi Chris,

Did you manage to include the Reset function within the firmware? if not, how can we tweak it to activate the reset without need to use a GPIO?
Can the firmware be tweaked to just reset the TCP/IP stack?

I can confirm this bug.

Netduino will stay up for days on a quiet, local LAN. If I take it and plug it into our university's LAN, it freezes within minutes. The board remains responsive to input pin events, but the network connectivity no longer works until you press the reset button.

It seems the Netduino's stack can't handle tons of broadcast traffic created by management services on large lans. (Cisco proprietary, or STP, etc.)

Exact same behavior in my university, after few seconds of our typical 30-45KB/s background broadcast noise, while it worked fine for weeks at home with low traffic.

A potentials work around would be to put a cheap nat router between the netduino and lan, and port forward 80 on the wan side ip to the netduino. That should block all of the broadcast noise, but let in the http requests.

But this kill the beauty of a tiny electronic to connect something to internet. If an additional router was requited, then is better and far cheaper to buy an OpenWRT compliant router such as Linksys 54G for 60€ and program it in C

I would be just happy if it would be a way to reset the eth interface when N+ detect lose of network connectivity

Its SimpleStorage included already?

4.2 RC1 has a known issue with Socket.Connect().

The issue was discovered by Christopher Gilmore and discussed here

Carlos