Re:AT&T updates firmware to block access to 1.1.1.1
by juliangoldsmith on Thursday May 03, 2018 @10:19AM
(#16986250)
Any sane gateway would block any access to anything from RFC1918, and using a private IP address for a public service is a bad idea in general.
[ Parent
| on HN ]
Re:AT&T updates firmware to block access to 1.1.1.1
by unethical_ban on Thursday May 03, 2018 @10:44AM
(#16986470)
Fair enough, if it was traversing public (non-ATT) networks without a tunnel.
Re:AT&T updates firmware to block access to 1.1.1.1
by juliangoldsmith on Thursday May 03, 2018 @03:13PM
(#16988910)
It would be reasonable for AT&T equipment to block any private IP traffic outside a customer's private network by default. That's ignoring that AT&T's network is public, and it wouldn't make sense to use a private IP for a service they provide.
Reversing that would likely require AT&T to make a firewall change to literally every piece of equipment they operate, and that's assuming that they don't use the blocks internally. That, and I can guarantee that some customer, somewhere, would be using whatever IP they chose.