This is incredibly frustrating.. until 2 days ago my phones & service have worked just fine and Verizon would always assign the ppp (3G) interface on my DROID (& other phones win mobile etc.) a real pingable and reachable PUBLIC IP address..
Suddenly (no changes on my end) they are assigning me a NATted
dynamic ip of 10.224.X.X which is of course NOT reachable from the outside world!!
No answers from 8 hours of tech support and escalating the issue yet.
I've talked to 10 people and 2 'supervisors' an engineer and one 'NOC liason' so far.. none of which even knows what the term "NAT" means.
That is the frustrating part...
Everyone I've spoken to has told me if I can browse the web that there's
no problem with the service.
I've tried unrooting and also factory resetting the phone (Droid-x) all of
which have no influence... Verizon *is* indeed assigning from a 10.x
natted firewalled IP address pool..
I'm not sure if this sudden change is global or just in my area or if it's some kind of temporary test or work-around on Verizon's part.
Ever so frustratingly they won't put me through (yet) to anyone who can tell me WTF is going on and why the change 2 days ago.
If they're going to play like this they just lost a loyal 10+ year customer and I hope they loose a whole lot more..
This is the degrading **** that ISPs who don't believe in providing actual Internet pull and I'll have no part in supporting or living with it.
Main point I'll finally make now is if your Have a Droid on Verizon.. could you kindly check & see if you are still getting a public IP like normal or some Natted 10.x.x.x IP?
Oddly all of our Windows mobile phones are still getting public IPs.
I'm the oddball with Android and don't yet have another point of reference. ;-)
It was fine and *was* getting a dynamic public for 2+ months until now.
I have made no software changes that would have or could have caused this.
My next test will be to move my acct to my old winmobile phone & test..
But I'm pretty sure they are forcing the NATted IP out only to Droid users.
Suddenly (no changes on my end) they are assigning me a NATted
dynamic ip of 10.224.X.X which is of course NOT reachable from the outside world!!
No answers from 8 hours of tech support and escalating the issue yet.
I've talked to 10 people and 2 'supervisors' an engineer and one 'NOC liason' so far.. none of which even knows what the term "NAT" means.
That is the frustrating part...
Everyone I've spoken to has told me if I can browse the web that there's
no problem with the service.
I've tried unrooting and also factory resetting the phone (Droid-x) all of
which have no influence... Verizon *is* indeed assigning from a 10.x
natted firewalled IP address pool..
I'm not sure if this sudden change is global or just in my area or if it's some kind of temporary test or work-around on Verizon's part.
Ever so frustratingly they won't put me through (yet) to anyone who can tell me WTF is going on and why the change 2 days ago.
If they're going to play like this they just lost a loyal 10+ year customer and I hope they loose a whole lot more..
This is the degrading **** that ISPs who don't believe in providing actual Internet pull and I'll have no part in supporting or living with it.
Main point I'll finally make now is if your Have a Droid on Verizon.. could you kindly check & see if you are still getting a public IP like normal or some Natted 10.x.x.x IP?
Oddly all of our Windows mobile phones are still getting public IPs.
I'm the oddball with Android and don't yet have another point of reference. ;-)
It was fine and *was* getting a dynamic public for 2+ months until now.
I have made no software changes that would have or could have caused this.
My next test will be to move my acct to my old winmobile phone & test..
But I'm pretty sure they are forcing the NATted IP out only to Droid users.