After some more work, I think that it is temperature related. The device still fails if I disconnect the (single) ethernet connection and just use wireless. The CPU is essentially idle.

However, the case doesn't seem to get any warmer than the other two guruplugs that I have.

Any suggestions? Anybody else have the new guruplug (the one which needs the mwifi_ex driver for wireless?)

Philip

I just received my third guruplug (the version with the new wireless chip) and it seems to be behaving oddly. Before I realized that it had different hardware to my other two (original) guruplugs, I reflashed it with a new uboot and a new kernel. It was very tricky to boot the kernel (it kept on resetting when I typed any command and the uboot prompt).

Reflashing it again with the JTAG adapter was also tricky as it would reset during the flashing process.

Anyway, I ended up unplugging it for 24 hours, then plugged it in, got a new kernel flashed and booted it. This kernel stayed up for at least 2 days. Progress. However, I needed a different kernel, one based on linux 3.x to get the new wifi driver.

Getting the uboot prompt and trying to tftp a new kernel -- it just keeps resetting.

I currently have it turned off in the hope that there is something heat sensitive about uboot (?!?!).

ALternatively, the uboot that I have does not play nicely with the new Guruplug hardware. Does anyone know what uboot/kernel is loaded on new Guruplugs? And is this code available anywhere so that I can try that code?

Thanks

Philip

I'm looking to use my plug as (mainly) a IPv6-IPv4 converter. I.e. it would manage a IPv6 tunnel back to a tunnel broker (e.g. Hurricane Electric at http://tunnelbroker.net/ ) and would drop the IPv6 packets onto the local network. I don't see any reason that this couldn't be done on a single interface.

Has anybody else gone to the trouble of building such a system? Any tips?

Thanks

philip