http client test: unknown

[dpham00]

I was using the lte onoff app and before, the ping, ping hostname and http client test would show pass. Now, the ping and ping hostname show pass, but the http client test shows unknown. I tried several battery pulls with the same result. The signal was around 52db, and mobile data signal was near 100. I have tried it at several locations with the same result.

Some websites take forever to load, like google, which takes 30seconds. Before it would load right away. I do have 4g connectivity. I also notice youtube taking much longer to load, even the main page on the app. AC loads snappy as usual though.

Anyone else have this problem?

 

[Mortiel]

World IPv6 Day, maybe? Maybe it has nothing to do with your phone?

 

[FrankXS]

World IPv6 Day, maybe? Maybe it has nothing to do with your phone?

Haha... I love it. Good catch. IP6 is such an old idea, now. Started way back before everyone had a router in their own home dishing out private IPs. Was born in an era when you had to purchase each and every block of IPs. And that all the stuff in your house would need an IP (i.e. The toaster, heater, oven, refrigerator and TV). Well, they got one right, the TV, but a private IP (free and plentiful) is fine. Ah yes... IP6. I know there was more to it than simple numbers of potential IPs. But that was the driving force.

Why don't they just wait for Cellular 5G before implementing this

-Frank

 

[88 FLUX]

Haha... I love it. Good catch. IP6 is such an old idea, now. Started way back before everyone had a router in their own home dishing out private IPs. Was born in an era when you had to purchase each and every block of IPs. And that all the stuff in your house would need an IP (i.e. The toaster, heater, oven, refrigerator and TV). Well, they got one right, the TV, but a private IP (free and plentiful) is fine. Ah yes... IP6. I know there was more to it than simple numbers of potential IPs. But that was the driving force.

Why don't they just wait for Cellular 5G before implementing this

-Frank

There's no place like 0:0:0:0:0:0:7f00:1

 

[Mortiel]

Haha... I love it. Good catch. IP6 is such an old idea, now. Started way back before everyone had a router in their own home dishing out private IPs. Was born in an era when you had to purchase each and every block of IPs. And that all the stuff in your house would need an IP (i.e. The toaster, heater, oven, refrigerator and TV). Well, they got one right, the TV, but a private IP (free and plentiful) is fine. Ah yes... IP6. I know there was more to it than simple numbers of potential IPs. But that was the driving force.

Why don't they just wait for Cellular 5G before implementing this

-Frank

Because IPv6 have nothing to do with wireless technology? Fact is that we are running out of IPv4 addresses. Makes when you have decimal grouping with fixed places... 192.168.1.1 is going the way of the dinosaurs. Hexidecimal grouping with more places makes for a near infinite number of IP addresses.

And MAC addresses are not IP addresses. IP means Internet Protocol. Meaning its an address for something over the internet, not on a local network. MAC addresses are for items over the local network, such as your said toaster... mmm... bagels.

As I was told (or read, I can't remember), the US has the same problem with 1-800 numbers a decade or more ago. I have no idea how they fixed that, though.

 

[dhendriksen]

IP matters on a local network...MAC address is completely different. IP address on a local network is almost like a number parking stall...that may not be the best analogy.

IP matters big time on a local network, whether it had internet access or not. A lot of the technical points you bring up I won't argue with you, but on this one you're plain wrong.

 

[dpham00]

World IPv6 Day, maybe? Maybe it has nothing to do with your phone?

interesting, it could be. have been having trouble connecting to google and google voice as well. my clnr tb i just got today exhibits the same issues. glad i didn't call and complain about my replacement...yet.

 

[dpham00]

Have same problem today on my replacement.

 

[FrankXS]

Because IPv6 have nothing to do with wireless technology?

it was a joke.

And I never mentioned anything about MAC addresses. Where'd that come from? Also IP=Internet Protocol=The Technology! It does not indicate it is "over the Internet".

-Frank

 

[paintdrinkingpete]

Haha... I love it. Good catch. IP6 is such an old idea, now. Started way back before everyone had a router in their own home dishing out private IPs. Was born in an era when you had to purchase each and every block of IPs. And that all the stuff in your house would need an IP (i.e. The toaster, heater, oven, refrigerator and TV). Well, they got one right, the TV, but a private IP (free and plentiful) is fine. Ah yes... IP6. I know there was more to it than simple numbers of potential IPs. But that was the driving force.

Why don't they just wait for Cellular 5G before implementing this

-Frank

Because IPv6 have nothing to do with wireless technology? Fact is that we are running out of IPv4 addresses. Makes when you have decimal grouping with fixed places... 192.168.1.1 is going the way of the dinosaurs. Hexidecimal grouping with more places makes for a near infinite number of IP addresses.

And MAC addresses are not IP addresses. IP means Internet Protocol. Meaning its an address for something over the internet, not on a local network. MAC addresses are for items over the local network, such as your said toaster... mmm... bagels.

As I was told (or read, I can't remember), the US has the same problem with 1-800 numbers a decade or more ago. I have no idea how they fixed that, though.

Hey, and not only did you need public IPs for everything, but subnet mask was determined by network class, so often thousands of potential IPs would get wasted on a single network.

It is true that MAC addresses are used for local Ethernet networks, but any device that connects to the Internet needs an IP. Today, most homes has one public IP, and people, without even knowing it, rely on their router to provide NAT from a private network (i.e. 192.168.1.0), but that wasn't always the case, which is all I believe FrankXS was getting at.

IPv4 may have actually been sufficient for the entire world for a very long time, but the distribution mis-handled at the beginning when none of the experts ever would have predicted how widely used the Internet is today. The US currently "owns" a major portion of the publically available IP addresses, but in other countries, like China, that have huge populations and limited IP address space, it is a real concern right now...and why moving to IPv6 is necessary.

As far as 800 numbers, the phone companies just starting using alternate exchanges for toll-free numbers (i.e. 888, 866, etc)

 

[Mortiel]

Hey, and not only did you need public IPs for everything, but subnet mask was determined by network class, so often thousands of potential IPs would get wasted on a single network.

It is true that MAC addresses are used for local Ethernet networks, but any device that connects to the Internet needs an IP. Today, most homes has one public IP, and people, without even knowing it, rely on their router to provide NAT from a private network (i.e. 192.168.1.0), but that wasn't always the case, which is all I believe FrankXS was getting at.

IPv4 may have actually been sufficient for the entire world for a very long time, but the distribution mis-handled at the beginning when none of the experts ever would have predicted how widely used the Internet is today. The US currently "owns" a major portion of the publically available IP addresses, but in other countries, like China, that have huge populations and limited IP address space, it is a real concern right now...and why moving to IPv6 is necessary.

As far as 800 numbers, the phone companies just starting using alternate exchanges for toll-free numbers (i.e. 888, 866, etc)

Ah true. I was thinking that my router uses MACC addresses to *filter* devices on its local network. However, it also assigns every device an internal IP (i.e. 192.168.1.xxx), as well as an external IP (i.e. 72.xx.xx.xxx). That's two IPs per device. While internal IPs can be recycled easily since they are used inside the LAN, external IPs and DNS servers are the concern since they use multiple IP addresses regularly.

Although subnet masks don't really matter, as they are identical per class (i.e. 255.255.255.0).

 

[dpham00]

Found a solution, if you are rooted, go download "Set DNS" from the android market, and set DNS to Google's public DNS instead (8.8.8.8 and 8.8.4.4).credit meballard