Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Get HideMyAss! VPN, PC Mag's Top 10 VPNs of 2016 for 55% off for a Limited Time ×

Submission + - What follows shouldn't have been possible, but Verizon managed to pull it off:

MakerDusk writes: This evening, on a network I administer, I noticed an oddity with Verizon's mobile network. Two unique users on different devices with the same WAN IP.

Posted with the users' permission
* Client connecting: Tootsie (yaaic@99.sub-174-229-xx.myvzw.com) [174.229.xx.99] {?} [Tootsie]
* Client connecting: Laen (yaaic@99.sub-174-229-xx.myvzw.com) [174.229.xx.99] {?} [Laen]

After some investigation, it turned out to be a NAT collison on the Verizon end. The devices in question were a Sony Xperia and a Droid X. As can be expected, the phones fought for a bit, including freezing. Even after multiple restarts, the phones continued to obtain the same IP address from Verizon. At the moment, both phones are offline, and are unable to obtain a signal, thusly forcing the users to move back to their computers in order to continue fueling their IRC addiction.

To all this, I only have one thing to say: well done, Verizon.

This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

What follows shouldn't have been possible, but Verizon managed to pull it off:

Comments Filter:

System checkpoint complete.

Working...