Wed Aug 24, 2022 3:06 pm
Big Problem? I don't see the problem. Unless one insists in using only that same address to connect to different devices for initiating the connection.
I have configured routers and devices, with many addresses configured, and then I have identical hardware with exactly the same configuration (and IP addresses), there is absolutly no problem for keeping them apart in my LAN, and doing things like synchronizing their config files.
They are identified with different IP address in my LAN addresses. Their interface addresses do not belong to the LAN range, but only to that small sub-LAN (also sometimes called DMZ) that is NATted to that device range.
We do it all the time. 100.000 LAN's contain a device with IP address 192.168.1.100. They all go to Internet, and if we allow (incoming) port forwarding, they can be addressed from Internet, with their public address. This works because we use srcNAT/MAsquerade/dstNAT in the transition between the Internet (WAN) and LAN. Those devices cannot be addressed with 192.168.1.100 from the Internet, but nobody seems to need that. (Well even then it could work with a double conversion: (192.168.1.100 ->unique WAN address of wanted device -> 192.168.1.100) see last Forum link given above)
One way of explaining this, is thinking of your LAN as being the Internet, where your router is connected with it's WAN port to your LAN. And the LAN ethernet ports of your routers leading to private LAN's that use 192.168.x.0/24 address ranges. If multiple identical rangess are needed then the WAN port needs multiple addresses for separate incoming addressing, and "%ether" must be added in the IP route. Then one does srcNAT/Masquerade/dstNAT as with an Internet connection. Outcoming direction can be done with one (Masquerade) or multiple WAN-port addresses.