Hello,
Did anyone manage to get the following setup to work, over 3G / Internet ? :
upnplay client, WAN configuration towards 127.0.0.1 (on android device ) -> ConnectBot SSH client with remote tunneling to foo_upnp port (on android device) -> SSH server (on windows) -> foo_upnp (on windows)
It would be really great, but so far I didn't.
What I got working so far is the following :
1- RDP client (on android device) -> ConnectBot SSH client with remote tunneling to RDP port (on android device) -> SSH server (on windows) -> RDP server (on windows)
-> working great
2- upnplay client, WAN configuration towards server IP (on android device) -> Direct connection to foo_upnp -> foo_upnp (on windows)
-> working great, thanks to instructions below
but no luck when adding SSH tunneling in the chain.
foo_upnp is latest version (0.99.35)
thanks
I'm hoping that the alternative URL method would prevent the use of HTTP authentication at all, is this the intention?
I just released 0.99.34 which allow authentification in the URL path for all clients (before it was limited to iOS PlugPlayer). So you'll be able to
remotely connect with UPnPlay. In UPnPlay edit the the WAN server configuration:
- set the Description field to /<login><password>
- change the UDN field to something else than the LAN UDN
Then if you click on the WAN server entry (it will say "connecting to server..."), then on its LAN definition you should be able to browse.
This version also addresses a few other compatibility fixes:
0.99.34
- server: allow Internet connection with http://ip:port/<login><password> from any remote client
- device description XML parser is more lax to recognize UPnPlay's renderer.
- server: workarounded TwonkyMobile requests with malformed XML.