DynDns equivalent for Android?

[Guest paaland]

I love the ability to SSH into my phone. While I'm at home I've given it a static IP from the wireless router, but when connected to 3G it's kind of hard to find the IP (opening a shell on the phone and tapping netstat is hard, ok?). So I'd love some kind of dyndns support so I could access SSH via some dns name instead.

Anyone have any experience with such tools?

[Guest pulser]

I love the ability to SSH into my phone. While I'm at home I've given it a static IP from the wireless router, but when connected to 3G it's kind of hard to find the IP (opening a shell on the phone and tapping netstat is hard, ok?). So I'd love some kind of dyndns support so I could access SSH via some dns name instead.

Anyone have any experience with such tools?

Not tried it personally, but search market for 'dyndns' and get the app of that name (it's free and by a guy called Neil Boyd).

Sounds like it would do the trick.

[Guest paaland]

Not tried it personally, but search market for 'dyndns' and get the app of that name (it's free and by a guy called Neil Boyd).

Sounds like it would do the trick.

Doh :) Should have done that first. Did a google search for "DynDns client for Android" without coming up with anything promising, but didn't think of checking Market. Will try it and report back.

[Guest paaland]

Worked like a charm, even uses local IP when I'm connected to WiFi. But I'm unable to connect to my phone when it's on 3G network. If it's because dropbear is only configured to accept connections from same subnet or because my tele operator blocks port 2222 to phones I don't know. I'm able to ping my phone though :)

[Guest pulser]

Worked like a charm, even uses local IP when I'm connected to WiFi. But I'm unable to connect to my phone when it's on 3G network. If it's because dropbear is only configured to accept connections from same subnet or because my tele operator blocks port 2222 to phones I don't know. I'm able to ping my phone though :)

OK. One suggestion/question.

What country and network are you in/on.

Reason I ask is I am on T-Mobile UK, and I think I get a NAT-type shared IP address. (or maybe one from a pool) but what I'm pretty certain about is that I'm not the only person with that external IP address.

Reason being is that I can see my 'internal network' IP Address is currently 10.216.239.xxx, but a web-based IP address finder returns 149.254.xxx.xxx(Manchester). The last two parts seem to change, but I have an inkling that the address may be shared between users.

I may be wrong though, but I don't think DynDNS can get through a NAT router, since no-one can directly access the 10.216 address (like 192.168.0.1), but it can access the address possible shared between users (149.254), but can't direct the query to your phone since the router doesn't know where to send the packet, so it drops.

This would also explain being able to ping the IP, since it might be a server, but not actually access it on port 2222.

[Guest paaland]

OK. One suggestion/question.

What country and network are you in/on.

Reason I ask is I am on T-Mobile UK, and I think I get a NAT-type shared IP address. (or maybe one from a pool) but what I'm pretty certain about is that I'm not the only person with that external IP address.

Reason being is that I can see my 'internal network' IP Address is currently 10.216.239.xxx, but a web-based IP address finder returns 149.254.xxx.xxx(Manchester). The last two parts seem to change, but I have an inkling that the address may be shared between users.

I may be wrong though, but I don't think DynDNS can get through a NAT router, since no-one can directly access the 10.216 address (like 192.168.0.1), but it can access the address possible shared between users (149.254), but can't direct the query to your phone since the router doesn't know where to send the packet, so it drops.

This would also explain being able to ping the IP, since it might be a server, but not actually access it on port 2222.

I'm in Norway using Telenor's network. My IP at the moment is 188.148.253.x. This is a valid public address. So I don't think my provider uses NAT, but you are right that is NAT is used you cannot SSH in easily.

Update: Now it works with SSH over 3G as well. First time I tried I was a work and apparently port 2222 is not opened for outbound traffic at work. When I retry at home it works fine.

Edited January 6, 2010 by paaland

[Guest pulser]

I'm in Norway using Telenor's network. My IP at the moment is 188.148.253.x. This is a valid public address. So I don't think my provider uses NAT, but you are right that is NAT is used you cannot SSH in easily.

Update: Now it works with SSH over 3G as well. First time I tried I was a work and apparently port 2222 is not opened for outbound traffic at work. When I retry at home it works fine.

Good result!

I also investigated a bit more, and it seems that I am not getting NAT on T-Mobile UK. I was mistaking the DNS IP address with the current external one (both are very similar, and I skipped a line when reading).

Having NAT for different users is certainly not a good solution, so I'm glad T-Mob at least seem to give us semi-unique addresses.

[Guest ippoP]

Good result!

I also investigated a bit more, and it seems that I am not getting NAT on T-Mobile UK. I was mistaking the DNS IP address with the current external one (both are very similar, and I skipped a line when reading).

Having NAT for different users is certainly not a good solution, so I'm glad T-Mob at least seem to give us semi-unique addresses.

Even without NAT maybe you are firewalled!

In the (damaged) brain of telco operators there's no use for incoming connections to a mobile phone.

I would suggest you to make a portscan once you see your current 3G IP.

Then you'll kow the truth.