I've posted this over at the Rhodium Thread located here:
http://forum.xda-developers.com/showthread.php?t=731292
but haven't gotten a single response yet. Since this is a concern for more than one device I feel like I should post it here. Mods feel free to move this to the correct location if need be.
===================
So it seems to me that this is a problem on ALL Android devices that I have tested with. Here's the situation
I have a router in my house in which I have DHCP turned off so my device will grab an IP (Not Static) and DNS from the ISP. I need to find a way to be able to just change the DNS Settings to 208.67.222.222 and 208.67.220.220 on android without having to manually put in an IP since the IP will automatically get changed every few day's.
Android doesn't seem to let me do that. Does anyone know how? Going into the Advance Menu in the Wifi settings and changing the dns does not actually change anything... I noticed this on the following android devices as well: Moto Cliq, MyTouch 3g, old Kaiser running android on NAND, and my Rhodium Devices running android.
Any reason as to why Android isn't updating my DNS Settings? Any help would be appreciated.
starmena said:
I have a router in my house in which I have DHCP turned off so my device will grab an IP (Not Static) and DNS from the ISP. I need to find a way to be able to just change the DNS Settings to 208.67.222.222 and 208.67.220.220 on android without having to manually put in an IP since the IP will automatically get changed every few day's.
Click to expand...
Click to collapse
Ok so DHCP is assigning your network config, but you want to use different DNS servers than the DHCP allocated ones?
starmena said:
Android doesn't seem to let me do that. Does anyone know how? Going into the Advance Menu in the Wifi settings and changing the dns does not actually change anything... I noticed this on the following android devices as well: Moto Cliq, MyTouch 3g, old Kaiser running android on NAND, and my Rhodium Devices running android.
Click to expand...
Click to collapse
On my HTC Hero running an Android 2.1 ROM, unless "Static IP" is selected, I dont even get the option to change the DNS servers (option is greyed-out).
One way to manually change DNS is via shell if you have root access on your phone using ADB shell (or ssh, telnet etc if your ROM supports them), see this thread [Q] Help! Changing DNS settings .
Any network config tools on the app store?
-jc
starmena said:
I've posted this over at the Rhodium Thread located here:
http://forum.xda-developers.com/showthread.php?t=731292
but haven't gotten a single response yet. Since this is a concern for more than one device I feel like I should post it here. Mods feel free to move this to the correct location if need be.
===================
So it seems to me that this is a problem on ALL Android devices that I have tested with. Here's the situation
I have a router in my house in which I have DHCP turned off so my device will grab an IP (Not Static) and DNS from the ISP. I need to find a way to be able to just change the DNS Settings to 208.67.222.222 and 208.67.220.220 on android without having to manually put in an IP since the IP will automatically get changed every few day's.
Android doesn't seem to let me do that. Does anyone know how? Going into the Advance Menu in the Wifi settings and changing the dns does not actually change anything... I noticed this on the following android devices as well: Moto Cliq, MyTouch 3g, old Kaiser running android on NAND, and my Rhodium Devices running android.
Any reason as to why Android isn't updating my DNS Settings? Any help would be appreciated.
Click to expand...
Click to collapse
I'm confused by your question. If you have DHCP turned off your device's are not going to grab an IP address from your router. Why don't you turn on DHCP and let your router assign IP addresses. As doing so your devices will also use the DNS setting from the router which will be your ISP's DNS ip address. Unless you change your DNS settings in your router to one of the many public DNS servers available. My recommendation is turn DHCP to "ON" on your router. Maybe start your DHCP IP assignment at 192.168.1.100 and go up to 150. That way you can use the range from .2 to .99 for static IP's. This is how I configured my router but I'm also using DD-WRT firmware on my router which highly customizes the router. Alternately you can change your routers DNS ip setting to Open DNS server so there would be no need for you to change it on the phone if you are using WIFI. Just let your router do all that work for you. Hope this helps. Viva Santiago Rep Dom y NYC.
I set up my Gizmo5 account for SIP calling yesterday on the wireless network provided by my Verizon Fivespot, and it worked fine. Now I'm on my home network (Verizon DSL), and when I try to use Gizmo5 on my Nexus S, I get the error "Account registration failed: (transaction terminated); will try later." Why does this happen on only my home network? Is there anything I can do to get Gizmo5 to work at home?
Device: Nexus S
OS: Gingerbread 2.3.1
Carrier: None (Verizon Fivespot)
It may be network related at your house. Possibly a router/firewall not allowing the traffic in/out. I doubt it but I suppose the provider could be blocking that type of traffic as well.
What can I do to fix it though? I already checked my router settings and the firewall isn't blocking anything.
aaronbp said:
What can I do to fix it though? I already checked my router settings and the firewall isn't blocking anything.
Click to expand...
Click to collapse
It isn't only the outgoing ports that need to be open (they definitely do), but the firewall has to support NAT *correctly*. SIP requires intelligence from a firewall, opening/keeping-track of outgoing/incoming UDP ports, etc. If your router supports it, try a third-party firmware like Tomato.
I had this same problem with new ubee modem/router. It is indeed NAT, and the ubee has no option to disable it.
I ended up putting my old router on the ubee DMZ and now gizmo and sipgate work.
Anyone have suggestions on making a ubee work with voip?
Sent from my Nexus S using XDA App
There are static ip, gateway, mask in advanced wifi setting, but there isn't proxy setting. I'm on CM7 #41. Can anyone help on this? Thanks much!
CM is still Alpha, which means not all features implemented yet.
Have you tried searching the Market for a proxy app? I saw this one just now, along with many others: http://www.appbrain.com/app/http-proxy-settings/org.credil.proxysettings
I've never tried them, but couldn't hurt for you to.
I was also wondering about the wi fi proxy settings, i tried the http proxy settings application, it doesnt work for me, plus it doesnt have the option for a usename and password....
anyone else got an ideas?
Anyone try the IPv6 Beta for ICS Nexus S? They have IPv6 enabled on 3G now.
https://sites.google.com/site/tmoipv6/lg-mytouch
Didn't work for me. Lost data.
I set up the apn for it, still waiting on the confirmation from t-mobile saying they've provisioned my number for use of ipv6.
dls5375 said:
Didn't work for me. Lost data.
Click to expand...
Click to collapse
What did not work for you?
I read this review that it worked well. http://www.prolixium.com/mynews?id=963
Highlights were that users get public IPv6 addresses and inbound connections to the phone work
its not working for me either. ive been exchanging emails with a person from that tmobile beta program, and he has a theory why its not working for me, custom rom. im on cm9. cm9 might not include the correct RIL files. i will try with a stock rom later on.
elgato99 said:
What did not work for you?
I read this review that it worked well. http://www.prolixium.com/mynews?id=963
Highlights were that users get public IPv6 addresses and inbound connections to the phone work
Click to expand...
Click to collapse
I set it up the way the instructions said to, rebooted and lost my data connection. It came back when I restored default.
IPv6 works fine for me with the stock Nexus S IML74K firmware, both with the special beta APN and the standard epc.tmobile.com APN (which is IPv6-enabled in the Bay Area). I did some reading on the topic last night for a friend, and it does look like you need support from the cellular radio for IPv6 to work correctly (for Android, I assume that means both baseband and RIL).
Apart from just doing it, what are the advantages of doing it?
mobilehavoc said:
Apart from just doing it, what are the advantages of doing it?
Click to expand...
Click to collapse
Fair question.
To people with mobile phones, the benefits are real public IPv6 addresses that allow for the bidirection flow of traffic. Read -- inbound connections... can have a web server or ssh server on your phone... A phone now becomes a real node on the real Internet, not a "mobile web" experience. Actually, each mobile phone is assigned 2^64 IPv6 addresses... that is a codified standard (yes, there are a lot of IPv6 addresses, no i dont think this a bright, but it is not actually a problem). There is no NAT from IPv6 to IPv6 addresses. But, other than that, not a whole lot is different from a user perspective. One can wax poetic about re-establishment of the internet's end to end principle, or how IPv6 is going to help battery life... but it gets kinda hand wavy. This is why IPv6 has been around for 10+ years without much traction.
The real benefit i see is to the mobile network providers, or Internet in general. Mobile devices are growing at a very high rate and there is just not enough IPv4 addresses to go around. Internet wide, IPv4 is pretty much exhausted.
I thought this article had some interesting pointers http://tech.slashdot.org/story/12/01/13/2348206/ipv6-only-is-becoming-viable
And, Facebook, Google, Bing, Yahoo ... are all turning on IPv6 for good in June. On the Internet, IPv6 is a pretty big deal in terms of how data flows through the tubes.... But, ideally, plane old joes dont have to care about IPv6. It should just work.
Here is some info on the World IPv6 launch day http://www.worldipv6launch.org/
Thanks. I noticed on the site they say P2P services like Skype won't work with IPv6 and there's obviously going to be some compatibility issues. I'm excited to try it out but at the same time I don't want to break apps or functionality. Guessing by this fall people will adopting it more and there'll be less breaks.
Right, some technologies are going to evolve quicker than others. The slashdot article had a link to a list of apps that work and dont work, i think it said 85% work fine... but a few fail. In any event, for this beta, switching between the IPv4 APN and the IPv6 APN is pretty easy (3 taps). I think one of the goals is to create an early adopter critical mass to find the broken things, complain, and get them fixed.
Here is another interesting link about getting the apps cleaned up http://www.gossamer-threads.com/lists/nsp/ipv6/32908
And, if you really want to go deep, there is this code which fixes the broken apps by doing translation on the phone from IPv4 to IPv6
http://code.google.com/p/android-clat/
Works fine for me....CM9 Euroskank kang and the Trinity t132 kernel. The lack of mms support makes it a non daily use apn for me..(kids, grandparents, etc...lots o' pictures)...but otherwise...good to go here...
working here now too. cm9 kang and trinity t144. i did have to flash the newest radio then let it sit there for a bit before it connected to data for the first time. now it connects quick every time. ive found one problem though, it wont let my laptop get data while its tethered, even though the phone has a good data connection. as soon as i change my apn back to the original and let it connect, data starts flowing to my laptop again. will someone else try to tether. it connects fine, just no data flow.
I got it working with the browser but my signal bars never turn blue and Sync doesn't work at all along with most background sync apps. Seems odd. I'm on 4.0.2 stock. I switched back to iPV4 and everything works perfectly. At least I have it configured to try later on in the summer.
mobilehavoc said:
I got it working with the browser but my signal bars never turn blue and Sync doesn't work at all along with most background sync apps. Seems odd. I'm on 4.0.2 stock. I switched back to iPV4 and everything works perfectly. At least I have it configured to try later on in the summer.
Click to expand...
Click to collapse
syncs here just fine with blue bars.
simms22 said:
syncs here just fine with blue bars.
Click to expand...
Click to collapse
Which APN are you using? The website lists one and the email I got from T-Mobile listed a slightly different one?
I tried it again and it worked this time with the blue bars and sync using the scpcf000 APN. Wonder why it didn't work before? Wonder if different towers/regions have issues because I was travelling when it wasn't working. Who knows.
I would keep it but no MMS is a bummer - if there were some practical advantage to using IPV6 right now I'd stick with it but there doesn't seem to be. Yet.
mobilehavoc said:
Which APN are you using? The website lists one and the email I got from T-Mobile listed a slightly different one?
Click to expand...
Click to collapse
epc-scpcf000.t-mobile.com
simms22 said:
ive found one problem though, it wont let my laptop get data while its tethered, even though the phone has a good data connection. as soon as i change my apn back to the original and let it connect, data starts flowing to my laptop again. will someone else try to tether. it connects fine, just no data flow.
Click to expand...
Click to collapse
Yeah, no Internet connection on my laptop when I try to tether either. It looks like Android's tethering infrastructure isn't IPv6-aware yet -- the laptop isn't picking up an IPv6 address, and the phone doesn't have an IPv4 address, so it's not capable of routing IPv4 traffic to the Internet.
That said, even if Android were to grow IPv6-aware tethering, providing Internet access is going to be a problem. I can see four possible approaches:
(1) The phone assigns IPv4 addresses to tethered devices (as it does now), and implements NAT46 to translate that traffic into IPv6 traffic to send upstream. I don't know of any NAT46 implementations, though, never mind any ones suitable for a phone.
(2) The phone assigns IPv6 unique local addresses to tethered devices, and implements NAT66 to push that traffic upstream. (Basically, this is like the current tethering setup, except with IPv6 everywhere instead of IPv4.) Highly experimental NAT66 standards and implementations exist, but their very existence seems to be controversial (one of the original ideas behind IPv6 was to have enough address space to not have to use NAT in the first place).
(3) The cell provider assigns a /64 or larger block of globally-routable IPv6 addresses to the phone, and the phone assigns those addresses to tethered devices. (This is the approach fixed-line broadband providers are taking.) As far as I know, though, there isn't a standardized way to hand out prefixes (other than DHCPv6, which people don't seem to like either), and of course, this requires carrier involvement, with implications for everyone who wants to tether without a carrier-approved tethering plan.
(4) The cell provider assigns an IPv4 address (public or private) to the phone, and tethered clients use the existing IPv4 tethering infrastructure. This requires no changes on our end (it'd work right now on carriers that provide dual-stack access), but T-Mobile has apparently decided to assign IPv6 addresses only and use NAT64/DNS64 to provide access to the IPv4 Internet, so this won't work for us.
I found this article to be well written and informative for IPv6 on ICS http://www.androidpolice.com/2012/0...ere-is-what-it-all-means-and-yes-no-more-nat/
http://dan.drown.org/android/clat/
I tried this code out. It is pretty cool since it allows some additional functionality by doing a NAT from IPv4 to IPv6 locally on the phone. Skype and a few other apps that require IPv4 now work while they did not work before.