Related
I'm posting on behalf of the girlfriend, shes just been given this phone (I know its old) as her other phone broke, she's wondering what are the internet settings for this as we have both scowerd the internet for this and everything we tried didn't work even the settings from o2 didn't work and the customer service had question marks above there heads. I'm pretty much stumped on this one
I'm probably doing everything wrong so I thought I'd come here and ask for help as there isn't any shame in that
the way it goes is,
Description: "o2 GPRS"
Connects to: "WAP Network" (there's a choice of 4 I think)
Access point: "payandgo.o2.co.uk"
User name: "payandgo"
Password: "password"
Primary DNS: "0.0.0.0"
Secondary DNS: "0.0.0.0"
IP address: "193.113.200.195"
-----
if manually or automatically put in it either says
“Unable to
connect. Verify
your Dial-up or
proxy settings are
correct, and try
again.”
or
The phone is
unable to connect
to the Internet
-----
even if she has full signal (she has free internet on the tariff shes on) any help would get her off my back :L
Okay, I'm here in Houston and as of yesterday, I have noticed that it takes FOREVER for certain web pages to load. Specifically, Google.com(along with google search), and Yahoo (m.yahoo.com)
When I switch to 3g and Wifi, they resolve normally. On 4g, it's as if the dns server is having a tough time getting there. The weird thing is when I ping the sites by domain, I'm getting responses on my phone so I'm not even sure if it's DNS. Since if it was DNS I'd get slow responses, or I would only be able to ping it by I.P address.
So, I got an app on the market called SETDNS, and it seems to change my DNS server (I have it set to OpenDNS) and it still doesn't load up these sites fast.
Anyone in Houston having an issues with slow sites?
I've verified that it's not my rom (CUBEDROM) as my Co-worker here is on BAMF and is currently experiencing the same thing. I thought it was just the tower we both happened to be on, but we went somewhere outside of work on the other side of town, and still the same thing
Any ideas?
Samsuck said:
Okay, I'm here in Houston and as of yesterday, I have noticed that it takes FOREVER for certain web pages to load. Specifically, Google.com(along with google search), and Yahoo (m.yahoo.com)
Click to expand...
Click to collapse
FWIW, I'm in Denver and experiencing the same issues on those sites. While on the LTE network, some sites are ridiculously slow to load compared to 3G. I don't believe it's strictly a DNS issue; you'd never get the page to load at all if you couldn't resolve the domain name, you'd just get a 404 or the like.
Same thing with me in Pittsburgh. Even happens when trying to load the XDA app. Just takes forever on 4G but then 3G works fine.
NickWarner said:
FWIW, I'm in Denver and experiencing the same issues on those sites. While on the LTE network, some sites are ridiculously slow to load compared to 3G. I don't believe it's strictly a DNS issue; you'd never get the page to load at all if you couldn't resolve the domain name, you'd just get a 404 or the like.
Click to expand...
Click to collapse
Yeah, you know what you're right. If it was strictly DNS then I would only be able to ping by I.P
So is 4g being routed through a proxy or something?
It's getting annoying because I use google search alot on my phone, and it will only load up properly on 3g.
Hrm, so apparently it's not just a Houston thing.
If anyone could continue to confirm this that would be great.
Purely just a theory, but with the big sites like google.com and yahoo.com, they are testing IPv6 (Global IPv6 test day, started yesterday at like 4pm West time i believe). Possible that your wifi and 3g can handle IPv6, but the 4g switches were struggling? Just a theory.
Same issues here in Detroit, was better 20 mins ago but back to the same problem again.
I agree that World IPv6 Day could be a cause, but that's only if you have trouble routing to the IPv6 address. I'm testing using purely IPv4 addresses for m.google.com (First response I get is 74.14.213.193).
On LTE, I'm averaging 300ms for the first hop (69.83.157.73), and ~75ms for the other hops.
On 3G, I average 130ms for the first hop (69.83.157.73), and ~115ms for the other hops.
If that's on each packet, I'm experiencing about double the load time for any traffic to m.google.com on LTE vs. 3G. Of course, that's not taking into account actual transfer speeds, so some of that might be recouped on larger packets, but still, it's significant.
Same in Columbus, Ohio except that 3g was doing the same thing. I was trying to stream Tunewiki on the way to work around 8am and nothing would load. I tried rebooting but it didn't help. At that point I chalked it up to network problems. I jumped on wifi when I got to work and have been waiting for the threads to pop up here to confirm.
Same thing in socal so its a national thing
good thing we have options to change to 3g
and not 1x
Hrm, that's interesting.
Yooooo, i think you're right
check this article out
http://www.metro.co.uk/tech/865705-google-facebook-and-bing-test-ipv6-as-net-runs-out-of-space
I can't resolve google,yahoo, facebook,and bing is occasional.
They all will failover to IPv4, and I was testing using the IPv4 addresses. I still think there's something wrong here, and the World IPv6 Day stuff is masking it.
I can resolve all of the major sites in DNS and get both an IPv6 and IPv4 address for them. I chose to test with only IPv4 to ensure that my results would be comparable to each other.
Nick, i agree that there is an error here. I'm just outside of my 4g at work, but can you check what your IP is if you are on 4G? I have a sneaky suspicion that there is a correlation here. If we are on v6 and pinging to v4, could possibly see higher load times if there is software glitches on verizons end. Awfully suspicious if they are not related! And i do know the t-bolt is v6 ready, as all LTE on verizon are required to be v6 ready.
Hrm. When on 4g my IP is 166.249.220.38, for 3g my IP is 166.249.197.80
Samsuck said:
Hrm. When on 4g my IP is 166.249.220.38, for 3g my IP is 166.249.197.80
Click to expand...
Click to collapse
Well there goes my theory. Thanks for checking Samsuck.
I too see addresses in the same IPv4 Class A (10.0.0.0) when on either LTE or 3G. I'm seeing non-routables, of course, which then get NAT'd through to a pool of external IPv4 addresses.
Running netcfg on the phone shows that I only get IPv4 addresses. I don't believe that these phones are receiving IPv6 addresses from Verizon, which makes sense if they're non-routable addresses, since they'll have to be NAT'd at some point.
Ok, so netcfg on Android only supports IPv4, which is my bad.
I may have spoke too soon. This guy says his VZ LTE always assigns him a IPv6
www(dot)anandtech(dot)com/show/4289/verizon-4g-lte-two-datacards-wifi-hotspot-massively-reviewed/3
I can't seem to find any sites discussing for definite what IP's VZ deals out on LTE.
Samsuck, was the checker you used IPv6 capable?
cmhfdisker said:
Same in Columbus, Ohio except that 3g was doing the same thing. I was trying to stream Tunewiki on the way to work around 8am and nothing would load. I tried rebooting but it didn't help. At that point I chalked it up to network problems. I jumped on wifi when I got to work and have been waiting for the threads to pop up here to confirm.
Click to expand...
Click to collapse
Same here in Reynoldsburg man. Went down forbme last night around 1am n spotty ever since...
4Geezy ON DopeDiculous's ROOTED TBeezy!
NickWarner said:
I too see addresses in the same IPv4 Class A (10.0.0.0) when on either LTE or 3G. I'm seeing non-routables, of course, which then get NAT'd through to a pool of external IPv4 addresses.
Running netcfg on the phone shows that I only get IPv4 addresses. I don't believe that these phones are receiving IPv6 addresses from Verizon, which makes sense if they're non-routable addresses, since they'll have to be NAT'd at some point.
Ok, so netcfg on Android only supports IPv4, which is my bad.
Click to expand...
Click to collapse
Man it sucks not being on 4g to try myself, but if someone could try usb tethering, and also wifi tethering, then IP checking on a IPv6 capable checker. Might find out if it is the culprit.
When you say checker what do you mean? How did I check my IP?
I just browsed to http://whatismyip.com
I pinged the different sites via the terminal emulator.
nbdysreal said:
Man it sucks not being on 4g to try myself, but if someone could try usb tethering, and also wifi tethering, then IP checking on a IPv6 capable checker. Might find out if it is the culprit.
Click to expand...
Click to collapse
Ok, when I'm on LTE, I do indeed get a public, routable IPv6 address. Using http://whatismyipv6.net on the phone, I can both see the address and traceroute back to it. Awesome.
On 3G, going back to the same site shows me that I only have an IPv4 address. It's a non-routable 10.0.0.0 address that gets NAT'd to a 166.250.0.0 address on the outside.
I am using a Samsung Focus S, version 7.10.7720.68 and whenever I am on cellular I cannot download apps, look up achievements on the xbox app, or use the search at all. When I am on WiFi, it works fine. Here's the catch; I am using it with a Str8 Tlk SIM card. I can browse the web fine, just not use apps that use the live services.
All the proxies for att.mvno resolve to:
Code:
Name: rds-proxy.mycingular.net
Address: 66.209.11.33
Aliases: proxy.mvno.tracfone.com
So I've tried just using the IP address, plus other MVNO proxies that I've located, but it doesn't matter since they all resolve to the same place.
I've reset the phone, I've removed the phone from my live account and I got it to work for 1 app, then it stopped working immediately after downloading it. I've tried a samsung focus and had the same results.
I don't know to look up the error logs to see what the problem is. I'm wondering if it's blocked in DNS somewhere on AT&T's side since it works fine on WiFi.
Any ideas where I should continue?
Not sure if you are still having this issue, but I just ran into a similar thing but with net10 on my Focus. I sent an email over the net10 support and they had to fix some data provisioning on their end. Once they fixed it, all live services worked.
One thing to note though - under the APN settings, I just put att.mvno for the name and left the proxy address and port blank. If I put in the proxy url/port, I couldnt get live services working. So try the the apn setting first, reboot your phone and see if it works. If it doesnt, you might need to send an email to Straight Talk to see if there is something wrong with the data settings for the sim.
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.
Hi I just got lycamobile in london, and Id like to tether using a samsung focus from 2011 that I bought in the USA.
Well Ive been tethering using vodaphone in London but recently changed to lycamobile, I know lycamobile allows tethering, but I need to know the settings for the dial up connection that I need to setup on windows (PC), in order for me to tether using a USB.
Vodaphone details for the connection are:
phone number: *99***#
username: wap
password: wap
NOW ID LIKE TO KNOW THESE SAME DETAILS FOR LYCAMOBILE, THANKS A LOT.
Hi,
I guess I've got almost the same problem except I want to use my GS4 as USB Modem.
I recently moved to London, I've got a GS4, classic ROM at the moment, just took a Lycamobile Bundle, 3Gb Data and configured my APN as follow:
Name: lycamobile
APN: data.lycamobile.co.uk
username: lmuk
password: plus
MMC 234
MMC: 26
Authentication type: PAP
APN type: default,*
Roaming is on and wifi is off.
When I connect to my Windows 7, it detects the new NDIS but says there's not internet access, the windows diagnostic didn't help at all, it says everything is ok.
Lycamobile doesn't help for other devices than mobiles.
The reason why I'm asking here for someone tell me what could be wrong or if you resoved yours and can point me to what to do ?
Thanks,
-Fred
same
WAS working here and then, stopped working (DE, although the network config is probably similar).
Have yet to figure out what it is.
Lycamobile (.de)
lmde
plus
data.lycamobile.de
DNS resolution is working, but data doesn't pass. The client gets an IP then nothing. It will be investigated further.
If other people can offer updates, please post them.
ndrsconschrtysvcs said:
WAS working here and then, stopped working (DE, although the network config is probably similar).
Have yet to figure out what it is.
Lycamobile (.de)
lmde
plus
data.lycamobile.de
DNS resolution is working, but data doesn't pass. The client gets an IP then nothing. It will be investigated further.
If other people can offer updates, please post them.
Click to expand...
Click to collapse
Have you guys figured this one out? I have exactly the same problem, but with Lycamobule netherlands.
Hi, I am having the same problem here with LycaMobile in the UK, I tried to tether but to no luck at all, having the same situation in what DoubleFX is having.
It seems their tethering detection system is hot on it and knows somehow that ANY other device is trying to connect through to the internet.
Same problem here in Portugal. Anyone was able to tether with success in lycamobile sim? Thanks
http://kenstechtips.com/index.php/tethering-on-uk-networks
Lycamobile doesn’t allow tethering on their network. The terms and conditions pertaining to tethering can be seen on the Lycamobile bundles page (scroll to the bottom and click the small link saying ‘Terms and Conditions’):
The offer is for non-commercial, private, personal use only – Lycamobile reserves the right to withdraw or suspend the offer or to disconnect you if we suspect that offer is being used for commercial purposes, for conferencing, or if it is not being used in a handset (in a SIM box for example), if it is being used for tethering or if any reason Lycamobile reasonably suspects that you are not acting in accordance with this policy where we consider that the usage was illegitimate.
Source: Lycamobile Bundles Page
Tariff Information: Lycamobile Website
One can tether but the client phone must be rooted, you need to download TTL application from the playstore in case of Android, dont know if there is a similar app on IOS, and on PC you ll need to change TTL setting on the PC (google how to do that).
Change TTL value from 64 to 65
Thats all
start hotspot on the Lycamobile phone and on the recieving phone or pc change TTL TO 65
bR