RussellInCincinnati
Senior Member
SmallNetGuy: "Just one question though... in order to be able to connect to modem's config page, I'd need to use 192.168.1.1, and that's my router's address too."
SmallNetGuy, you are giving the impression that
(1) you have 2 different devices on your network with the same IP address on your local network. This is a fundamental and glaring address clash that I cannot imagine you would put off fixing--before asking about changing anything else about your setup in order to properly access those devices' configuration pages.
(2) you are having trouble browsing to either or both of those devices' configuration pages from some local network browser, and
(3) your question is how to make it so that you browse to the config page of the now-inaccessible device(s) and
(4) you don't know how to do this and want help and
(5) you were somehow able to reach the now-inaccessible device(s) while running an older version of Merlin firmware
You have a glaringly mis-configured network with 2 devices having the same IP address. That is a fundamental problem no matter what router or firmware you are using.
Thus it makes more sense to reconfigure one or more of your LAN devices to fix the IP address clash (perhaps by starting a thread in some more generic forum in which you ask people for help in fixing this fundamental problem).
Do this before focusing on the oddity that you had some temporary ability to navigate to your mis-configured devices while you were running some particular version of Merlin firmware. I.e. do this for your own sake, also do this before asking Merlin users who are discussing Merlin-firmware-version-specific issures for premature attention.
SmallNetGuy, you are giving the impression that
(1) you have 2 different devices on your network with the same IP address on your local network. This is a fundamental and glaring address clash that I cannot imagine you would put off fixing--before asking about changing anything else about your setup in order to properly access those devices' configuration pages.
(2) you are having trouble browsing to either or both of those devices' configuration pages from some local network browser, and
(3) your question is how to make it so that you browse to the config page of the now-inaccessible device(s) and
(4) you don't know how to do this and want help and
(5) you were somehow able to reach the now-inaccessible device(s) while running an older version of Merlin firmware
You have a glaringly mis-configured network with 2 devices having the same IP address. That is a fundamental problem no matter what router or firmware you are using.
Thus it makes more sense to reconfigure one or more of your LAN devices to fix the IP address clash (perhaps by starting a thread in some more generic forum in which you ask people for help in fixing this fundamental problem).
Do this before focusing on the oddity that you had some temporary ability to navigate to your mis-configured devices while you were running some particular version of Merlin firmware. I.e. do this for your own sake, also do this before asking Merlin users who are discussing Merlin-firmware-version-specific issures for premature attention.