4 ms·

> I can't access 1.1.1.1 right now since I'm connected to a Cisco router. I've never seen or heard of a Cisco router doing anything that would interfere with a

> I can't access 1.1.1.1 right now since I'm connected to a Cisco router. I've never seen or heard of a Cisco router doing anything that would interfere with access to 1.1.1.1. Their wireless LAN controllers on the other hand, use 1.1.1.1 as the default (but entirely configurable) Virtual IP to use as an anchor for the captive portal. If you can't access 1.1.1.1 behind a Cisco router it's likely because someone set it up incorrectly.

zaroth 8y ago
> I've never seen or heard of a Cisco router doing anything that would interfere with access to 1.1.1.1. Well, now you have. > If you can't access 1.1.1.1 behind a Cisco router it's likely because someone set it up incorrectly. That’s kinda the point.
- RKearney 8y ago
  > Well, now you have. Allow me to rephrase, I've never heard of a Cisco router doing that from a reliable source. > That’s kinda the point. Then it has nothing to do with Cisco and everything to do with the person who configured it.
lathiat 8y ago
> I've never seen or heard of a Cisco router doing anything that would interfere with access to 1.1.1.1. I have news for you... "After very little research we quickly came across Cisco mis-using 1.1.1.1, a quick search for “cisco 1.1.1.1” brought up numerous articles where Cisco are squatting on 1.1.1.1 for their Wireless LAN Controllers (WLC). It’s unclear if Cisco officially regards 1.0.0.0/8 as bogon space, but there are lots of examples that can be found on their community websites giving example bogon lists that include the /8. It mostly seems to be used for captive portal when authenticating to the wireless access point, often found in hotels, cafés and other public WiFi hotspot locations." from: https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-globally/ https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-g...
- RKearney 8y ago
  As I already mentioned, their wireless LAN controller uses it as a configurable default. The Cisco Wireless LAN controller is not a Cisco "router".

zaroth 8y ago

> I've never seen or heard of a Cisco router doing anything that would interfere with access to 1.1.1.1. Well, now you have. > If you can't access 1.1.1.1 behind a Cisco router it's likely because someone set it up incorrectly. That’s kinda the point.

RKearney 8y ago
> Well, now you have. Allow me to rephrase, I've never heard of a Cisco router doing that from a reliable source. > That’s kinda the point. Then it has nothing to do with Cisco and everything to do with the person who configured it.

lathiat 8y ago

> I've never seen or heard of a Cisco router doing anything that would interfere with access to 1.1.1.1. I have news for you... "After very little research we quickly came across Cisco mis-using 1.1.1.1, a quick search for “cisco 1.1.1.1” brought up numerous articles where Cisco are squatting on 1.1.1.1 for their Wireless LAN Controllers (WLC). It’s unclear if Cisco officially regards 1.0.0.0/8 as bogon space, but there are lots of examples that can be found on their community websites giving example bogon lists that include the /8. It mostly seems to be used for captive portal when authenticating to the wireless access point, often found in hotels, cafés and other public WiFi hotspot locations." from: https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-globally/ https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-g...

RKearney 8y ago
As I already mentioned, their wireless LAN controller uses it as a configurable default. The Cisco Wireless LAN controller is not a Cisco "router".