> 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. > > One way to verify this theory is to configure another ip in that > subnet on re0, renumber re1 to 192.168.2.0/24 for example, and try > pinging 192.168.1.1. > > If I shifted to the 10.10.10.x network, would I set all my machines to use /24 subnet?
IOW, hostname.re1 would be inet 10.10.10.x 255.255.255.0 NONE I don't get why I would set up a second IP on re0, explain your thought process here... I called Verizon and they stated that the ONTs MAC is not the MAC causing problems, and actually told me it must be coming from my house. I found my wifes PC had lost its network connection, I have to use TL-PA4010 power adapters to get the last 10 feet of connections. I'm wondering if this was causing the issue. None of the MAC addresses for these devices are 20:c0:47:... though. I think this was just nit noise... Jay
