Hi
anyone here have the DOD of USA constantly over taking as the primary server of the device?
Boost mobile aka Sprint is Carrier ...
But when tracing back to my device it is always in a ip range belonging to the department of defense.
Have tried to block the domain [email protected] .mil still phone connects to their servers
Called the register at DOD ... They also do not understand how device is in their server...
11.0.00. A columbus OH. DOD server
Are they impossible to block from my device
PS im just a carpenter thats been on PC's since the days of loading them with a casset tape.
And my privacy i like.!!!
Related
Does xperia can use ipv6 as we know the ipv4 is almost finish so
My question is there any way to convert xperia x10 to ipv6
or this is implemented to the software?
OR
EDITED
BY THE WAY HOW TO SET UP in X10
HTML:
The main reason for the concern? There's an explosion of data about to happen to the Web - thanks largely to sensor data, smart grids, RFID and other Internet of Things data. Other reasons include the increase in mobile devices connecting to the Internet and the annual growth in user-generated content on the Web.
Why a New Internet Protocol is Needed
Currently the Web largely uses IPv4, Internet Protocol version 4. Each IPv4 address is limited to a 32-bit number, which means there are a maximum of just over 4 billion unique addresses. IPv6 is the next generation Internet Protocol and uses a 128-bit address, so it supports a vastly larger number of unique addresses. Enough, in fact, to give every person on the planet over 4 billion addresses!
John Curran from ARIN, the non-profit responsible for managing the distribution of Internet addresses in the North American region, told ReadWriteWeb that of the approximately 4 billion IPv4 addresses available, all but 6% have already been allocated. Curran expects the final 6% to be allocated over the coming year.
This is largely an issue that ISP (Internet Service Providers) and telecoms carriers need to deal with. However content service providers, including large-scale Internet companies like Google and Facebook, also need to ensure that the transition from IPv4 to IPv6 takes place. Curran explained that a content company like Google (for example its YouTube operation) will need to work with its ISP to transport the content via IPv6 as well as IPv4.
This transition is happening "slowly," says Curran. But he warns that "deployment is where we're behind."
Google, Facebook & Others Making Good Progress
John Curran told us that large carriers like Verizon and Comcast have announced trial IPv6 activity. Curran also noted that new Internet of Things initiatives that use sensor networks, power grids, RFID and similar technologies, are being directed to use IPv6 and not IPv4.
There is also solid support from the big Internet companies. Curran said that Google has already put the majority of its services onto IPv6. Declaring its support for IPv6 on a special webpage, Google states that "IPv6 is essential to the continued health and openness of the Internet [and] will enable innovation and allow the Internet's continued growth."
In June, Google held a Google IPv6 Implementors Conference. At that event, Facebook announced that it had begun to use IPv6.
In his opening remarks to the conference, Google's Chief Internet Evangelist Vint Cerf urges ISPs to move to IPv6, so that a "black market" for Internet addresses won't occur.
Another Y2K?
Critics view some of the push for IPv6 as Chicken Little 'the sky is falling' talk. Commented @ajbraun, a self-described technology leader at Sony Ericsson, via Twitter: "We should call this "IPv6: Y2K II." An obvious issue for 10 years, we will panic at the end and finally much ado about nothing."
Others see a technology called NAT (Network Address Translation) as a solution - it maps multiple addresses to a single IP address, thus reducing the amount of unique IP addresses required. However this is at best a temporary solution. Google argued back in 2008 that NAT and similar technologies "complicate the Internet's architecture, pose barriers to the development of new applications, and run contrary to network openness principles."
Whether or not there is Y2K-style fear mongering, the bottom line is that IPv6 is a much larger platform for the coming Internet of Things. So one way or another, the move will have to be made.
HTML:
References
http://win7vista.com/index.php?PHPSESSID=54d50a392a858b2105fcc3987bb2b422&topic=19481.0
What is that?
Edit: ok, thanks for editing your post
Sent from my Nexus One using XDA App
Edited
firstly the link below read it please!!
this is not a application!!!
This is "Internet Protocol version"
Read this
http://en.wikipedia.org/wiki/IPv4 <-------
http://en.wikipedia.org/wiki/IPv6
http://inetcore.com/project/ipv4ec/index_en.html
http://www.potaroo.net/tools/ipv4/index.html
http://www.pcmag.com/article2/0,2817,2373903,00.asp
please read before
Now every body suppose to understand
Edited
I find this
http://forum.xda-developers.com/showthread.php?t=733965&highlight=ipv4
But my question is specyficaly about X10
Is your mobile operator moving to IPv6? Do you have a IPv6 network in your home? Do you encounter IPv6 out and about?
With that said:
http://androidboss.com/android-2-1-actually-does-ipv6/
No they don't but I was wounder if it is possible or do I have buy new phone in less that 83 days.
Not sure if this belongs in this section or not. I know this is an ongoing issue with some Android OS phones. I just wanted to see if any other Atrix owner is having the same issues or if anyone has ideas on how to fix.
Problem
Network monitoring shows that your Android OS based phone is causing a problem on the campus wireless network.
Your phone is not properly communicating with the campus DHCP servers, which assign (“lease”) IP addresses to allow your phone to communicate on the campus network. Your phone contacts our DHCP server to obtain an IP address, and is given an IP address to utilize for a period of three hours.
During that three-hour period, if your device remains connected to the campus network, your phone should automatically contact our DHCP server to request a renewal of that lease for an additional three hours. If your device does not complete that renewal, the lease on the IP address your device is using will expire and your phone must stop using that IP address. At that time, the IP address is returned to the pool of available IP addresses that can be assigned to other users.
The problem we are seeing from your device is that it does not request a renewal of this IP address and it does not stop using this address after the three-hour lease expires. In some cases, we have even noted your device attempting to renew the lease on the IP address it was using well after it was expired.
As the IP address your device was using returns to the pool of addresses to be assigned to other users as soon as the lease expires, by continuing to use this IP address, your device will be interfering with others users who have been leased that IP address by our DHCP servers.
We have seen this issue from many Android OS based devices manufactured by a variety of vendors and sold by a variety of mobile carriers. As such, we suspect this is due to a bug in the underlying Android Operating System.
We do not expect that there are any configuration changes or settings on your device that would resolve this issue.
So there it is. I've read through some Google forums and even here at XDA. Any ideas or help would be greatly appreciated.
Just wondering if anyone else has run into this issue. When I turn on wifi at work, I get an error that says "sign-in not supported". Our work wifi requires a username and password, both of which are used to log into the network. Just wondering if this is an issue with the device or my IT network set up?
WiFi at home with encryption works fine, and public WiFi's works.
I'm thinking this stems from the same issues we having reading and replying to Corporate Exchange emails. My Exchange requires a password on device, although the Gear S has the ability to set a pin lock the whole thing stems from Corporations not being able to have access to wipe the watch.
Well, you know the wifi work cause you can access internet at home and public places.
I would first ask the corp IT dept if it is ok for you to log in with a unauthorized device first to the corp network. Now days corp IT dept have very strict access to what device and who can access their network due to hacking/virus......etc. If you can the ok, then you can ask if the GS is capable of accessing corp email and how to set it up.
I will make this quick, and I hope to see some insight into that question:
We all known how sensitive the DNS Service is. With most of our carriers/ISP proving the service, is not a surprise that lots of people are pressuring vendors to include more privacy-focused DNS services. And that is justified, with that information a company is able to infer lots about you, what banks you have an account, what is your e-mail provider, what porn sites you like to visit and etc, basically is possible to know pretty much everything you do online. Another aspect is that, if your Carrier/ISP got pwned, you are in bad sheets, as the hacker may redirect legit traffic to a custom server, waiting to -eager- to receive your connection and fool you.
Our best bet is to be able to change, and possible setup our own DNS service if paranoid.
Now, we have on Android an option to ask the system to use a encrypted connection to reach a DNS server on the Internet. This feature is called "Private DNS". That would be a solution, if Google were actually *enforcing* the config. Even if I use an VPN, the Carrier is able to ask the system to add a *custom route* that will redirect the traffic going to the Carrier DNS server *out* of the VPN. And if you use a VPN connection and your carrier do not enforce a route to their DNS, you will not be able to use Google's Private DNS as it doesn't work while a VPN is connected.
If you ask me, this is pretty much BS. There is zero need to have a VPN to push a DNS server, but what really shook me is that Google pushed the Private DNS, over TLS and over HTTPS but that setting is not global in the system. What the actual ****?!
The fact that I may need to root the device in order to control the DNS configuration is so bad.. I can't even express how I fell about that.
Any thoughts about the matter? Have you managed to control the DNS config without root and wifi tricks?
felco
Hi.
I have Wifi disconnections frequently on my phone (Xiaomi Redmi 5) and my researches lend me to focus on IPv6.
When my phone is connected to my home Wifi, I can see in the connections parameters that there are 2 local IP addresses : one IPv4 and another IPv6.
I disabled in my router settings the IPv6 management but my phone still has an IPv6 address.
What do I need to do (On the router or on the phone) to get rid of it?
Thanks!
Dude, i was just coasting down the information highway, not actually looking for this, but found it nonetheless, and coincidentally i go thru the same rather annoying events. Did you ever solve it? Care to share?
Yep, it appears to me that while using a VPN disconnections didn't occur anymore.
I don't understand why but if works.
I use this workaround since.
I'll give that a try! Thanks
I don't think it's a problem with ipv4 or ipv6. precisely if you don't establish an IP address it can't be connected to WiFi. maybe you can try resetting the Router you are using. CMIIW
@Double Jo
A Local IP address ( to be corect: Private IP address ) is an IP address that's reserved for internal use behind a router or other Network Address Translation (NAT) device, apart from the public. Private IP addresses are in contrast to public IP addresses, which are public and can't be used within a home or business network
The Internet Assigned Numbers Authority (IANA) reserves the following IP address blocks for use as private IP addresses:
10.0.0.0 to 10.255.255.255
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255
As one can see those all are IPv4 addresses.