> Le sam. 8 sept. 2018 à 18:06, Jay Hart <[email protected]> a écrit : >> >> > Le sam. 8 sept. 2018 à 13:40, Jay Hart <[email protected]> a écrit : >> >> -----ifconfig -A from the router------------------ >> >> re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >> >> lladdr 00:22:4d:d1:48:d5 >> >> inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 >> > >> > >> > Some CPEs have 192.168.1.1 hardcoded as management ip address, even >> > though they are currently used as modem/bridges. Renumber your >> > internal subnet to some other private address space and see if the >> > logs go away. >> > > >> I don't get why I would set up a second IP on re0, explain your thought >> process here... > > This is to confirm or deny that the modem do have 192.168.1.1 as > management address. That could be an explanation for the duplicate ip > address message you're seeing. > > You could just temporarily delete 192.168.1.1 from re1 to perform the > test, and only if it's successful (ie 192.168.1.1 on re0 answers to > pings) modify the IP configuration of re1 and renumber your lan. > > This is one of the reasons why I tend to avoid using 192.168.0.0/24 > and 192.168.1.0/24 as home lan addressing ranges. > >
Moved everything over to a 10.a.b.x subnet. Its all tested and working. Now I can back to seeing about that duplicate IP address BS, but suspect that particular issue solved itself.
