Hopefully this helps someone. I simply changed the channel from 36 ( 5180 ) to 40 ( 5200 ) and the problem went away.
Edit: spoke too soon :/
Search found 6 matches
- Sun Nov 10, 2024 10:06 pm
- Forum: Wireless Networking
- Topic: "not responding" - f.k.a. SA Query timeout
- Replies: 371
- Views: 92059
- Fri Aug 16, 2024 12:03 am
- Forum: General
- Topic: No TR069 support for AX routers
- Replies: 0
- Views: 960
No TR069 support for AX routers
These have been on the market for over 2 years now and there is still no support for WiFi on them. Is this ever going to be addressed?
- Tue Aug 06, 2024 6:31 pm
- Forum: General
- Topic: MLAG hopelessly broken?
- Replies: 58
- Views: 24437
Re: MLAG hopelessly broken?
Well isn't that awesome? The whole reason I bought a pair of CRS326 was to MLAG some critical ports. Is anyone from Mikrotik going to chime in here?They acknowledged it is broken and even asked me how things should work, then said they don't have time to fix it.
- Thu Jan 04, 2024 7:40 pm
- Forum: Wireless Networking
- Topic: wifiwave2 & tr-069
- Replies: 4
- Views: 3503
Re: wifiwave2 & tr-069
Any update on this? This is causing a lot of friction in our provisioning process.
- Thu Jan 04, 2024 6:44 pm
- Forum: Scripting
- Topic: Trigger script on NTP Client Sync
- Replies: 2
- Views: 1855
Re: Trigger script on NTP Client Sync
This isn't for a reboot scenario, but part of a TR069 provisioning process.
- Thu Jan 04, 2024 5:50 pm
- Forum: Scripting
- Topic: Trigger script on NTP Client Sync
- Replies: 2
- Views: 1855
Trigger script on NTP Client Sync
Does anyone know of a way to trigger a small script to execute after the clock syncs with an NTP client? The script relies on an SSL certificate that isn't valid until the clock is right. So far, the only thing I can come up with is to schedule a script every few seconds to check it which is hacky.