Quote:
Originally Posted by Sephiroth
Yes - but you could have made a helpful reply. Can you think of a reason for the 172.18.200.xx IP address? That poster could only get onto his router with the 192.168.1.1. address.
|
Ermm, I think you'll find he stated the exact opposite.
There are many different reasons you might want to switch to the 172.16.0.0/12 range, deliberately or otherwise. Can you think of any good reason to use 196.168.0.0/16?
What is there to "help"? We all took guesses at what caused it. There is nothing wrong, nothing to fix, and nothing to really explain. It's no more of a problem than if their router uses 192.168.1.1 instead of 192.168.0.1 or 192.168.100.1...
---------- Post added at 22:34 ---------- Previous post was at 22:33 ----------
Quote:
Originally Posted by Kushan
So while yes, the firmware update is certainly a likely candidate for the change, it still doesn't explain why it switched to a 172 IP range.
|
You frequently get glitches across firmware updates where they have changed the location that certain variables get stored, or the encoding of them, and they flip to some unintended value as a result of trying to "preserve" older settings. This is why it is widely recommended you do a factory reset as part of any kind of firmware change.
I'm not sure what the fuss is about though. 172.16.0.0/12 is a perfectly legitimate IP range to use and evidently it worked perfectly fine, and nobody even noticed until we deliberately went searching for it.