So I disconnected power to one of the MoCA devices and that allowed me to connect to the wifi network with an IP in the range of the router. Strange since it's been operating like this without issue for months. Ok well it does seem related to the MoCA set up in some way. If that clears it up, you may need to install a MoCA filter or talk to your cable isp about filters and MoCA network use in-house. I suggest removing your MoCA adapters and see if you continue to have a rogue DHCP service answering for you. I keep looking at MoCA and just can't shake the what-if someone removed a filter at my house so I have yet to try playing with it. Do you have a MoCA filter on your incoming line? If not, you're sharing MoCA network with anyone else on your cable head, your neighbors may be in your network, if they were addressed right. I was just looking at the cabling (for the nth time) and it seems fine (ISP lan to router WAN), and I have been trying to see if there is some kind of DHCP relay setting but haven't found that. I have been trying to undo my settings to see if that helps, I have even tried to factory reset router and instal an older firmware version, but none of that has helped. Hard not to think there is a relationship there. This has been working well for many months, and last week I attempted to modify the DNS server and had been changing some of the settings of the main router and then the next day I had this issue. The AP is in AP mode, no DHCP server running. The setup I have is a main third party router (asus 86u) connected to ISP, and I have an AP (asus 56u) connected via MoCA. It happens whether ethernet connected to LAN or connecting with wifi.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |