TUF BE3600 behavior

[markman34]

Hi All,

I've been having some troubles with my TUF-BE3600.
A few weeks ago I tried connecting one of my sonos speakers to the router via Ethernet. This event coincides with the beginning of some weird behaviour with the router.
I began to have disconnection issues with some clients, loT devices. Phones, laptops would not auto reconnect when powered up. loT devices would be disconnected.
After much messing around on my own and the sonos help desk, I decided to redo the whole setup.
I reset the router to factory and now, (as well as before) the router keeps assigning IP addresses outside of the DHCP pool. My devices keep getting 172... addresses on most occasions. Only if I reserve an IP based on MAC address will it get properly connected. When trying to connect the loT devices, this makes the process impossible.
This is absolutely not the case when I first set up this router. The first setup was as smooth as could be expected. Nothing surprising and completely painless compared to this time around.
I called ASUS and that was no help.
No additional routers on network. No AP's/extenders. Firmware is current.
I'm sure I'm missing something obvious but thought I'd ask the collective.
If anyone has any tips, please, let me know! I'm pulling out the remainder of the little hair I have left.

 

[Tech9]

My devices keep getting 172... addresses on most occasions.

Sounds like you have a device running second DHCP server on your network.

 

[markman34]

Sounds like you have a device running second DHCP server on your network.

Something I considered.
Modem is in bridge mode.
No unknown devices listed on the client list.
No mesh nodes. No routers. No APs. No extenders.

 

[markman34]

Sounds like you have a device running second DHCP server on your network.

ok. I think you're right. Again.
I think it's my ooma voip unit that's dolling out unwanted IPs.
I'll have a closer look tomorrow.
What a weird one.

 

[degrub]

Look into putting the OOMA on its own VLAN ?
i doubt it needs access to the rest of your network other than a route out to the internet anyway.

 

[Tech9]

Not familiar with OOMA devices, but I still have an VoIP ATA device and I believe it's also a router and can run DHCP. It's locked by the service provider and if the connections to it are wrong most likely it will mess up the network.

Your router doesn't have VLAN to LAN port feature. Smart Home Master series device with VLAN to WLAN only.

 

[markman34]

SUCCESS!
The ooma was definitely the problem. That and my poor eyesight.
When moving stuff around I must have run the ethernet cable to the wrong port on the ooma unit.
I didn't even know the ooma had a built in DHCP server. But a google search of the ip addresses and gateway led me to the ooma.
After reversing my error, I haven't had a phantom ip address yet. I still need to look into the need to isolate the unit on a vlan.
I've been able to reconnect most of my many devices.
Thanks to all for the help. Always helpful to brainstorm with such a body of knowledge.