I said, you can always change the brand of the router.

jimasek wrote

I said, you can always change the brand of the router.

Sure I will do that when this router failed on me. And why would I spend more money when the problem at hand can be resolve by the manufacturer with ease?

BTW, I don't want to sound rude but if you have nothing else to contribute I rather you keep your comment to yourself as it is not helping at all. Thank you.

I suggested only two possible ways to solve your problem with shell access, that's all.

jimasek wrote

I suggested only two possible ways to solve your problem with shell access, that's all.

Your so-called "solution" is a no-brainer in the first place. Coming into TP-Link forum and talking about third party firmware and changing router brand is a joke.

Don't forget that WR1043ND is only SOHO router without many features like in SMB products.

jimasek wrote

Don't forget that WR1043ND is only SOHO router without many features like in SMB products.

Shell access is just a simple feature and is readily available in most SOHO router nowadays.

Anyway, I don't see the point in arguing/debating any further.

I will post a ticket and see what TP-Link has to say.

But no in TP-Link and you have to accept the fact at this moment.

jimasek wrote

But no in TP-Link and you have to accept the fact at this moment.

Which is why I making noise here hoping they will reply or take some action.

BTW, you're beginning to get into my nerve.

Admin comment:

Gentlemen. This thread has been closed as discussion was going irrelevant.

Thank you for your interest on TP-LINK products. Unfortunately ssh shell is not integrated in stock firmware and there is no plan of implementation.

You can still find this forum useful on other topics. Any helpful discussion here are much appreciated.

Thanks.