Quote from: Xell on April 16, 2014, 08:28:56 AM

It is beyond my comprehension that users are willing to run hardware on their local network knowing someone else (unknown) has root access to the device. Especially inside the world of digital currencies. Why risk it? Use rasp pi and feel safe in the knowledge that you are in control. The modified mining software used in this binary is on github.

No one has root access to the device, stop making things up. Feel free to run a network sniffer to confirm.

Quote from: gbyg on April 16, 2014, 11:46:24 AM

Quote from: christian1980 on April 16, 2014, 09:27:45 AM

Maybe someone can try to change the root pw, activate ssh and create a new backup by a ttl adapter:
http://forums.openpilot.org/blog/52/entry-92-unbrick-wr703n-wifi-router/
http://zerolab.net/2013/04/30/tp-link-tl-wr703r-unbrick/
I dont like a closed system in my network too, i totally agree to Xell.
Its a good work, but we must be able to check what it is doing else. Sorry Sandor.

Is ssh not active? I gave away my 703n , so can't check.

SSH is disabled and serial console is disabled.

Quote from: mazedk on April 16, 2014, 11:57:40 AM

Absolutely nothing happens. It seems like its either not taking DHCP address or giving it out if i put a client in the ethernet port.

I should possibly say that its with the standard tp-link firmware that its having this issue.

Connect the Tp-link directly to a PC, log in to telnet and change the network configuration.