Diversion Diversion stopped working in 386.1_2

[thelonelycoder]

It is a strange one. All of uiDivStats' processes appear to be running. I wonder if the USB is failing/slow and dnsmasq.log isn't being written to correctly. That would impact both of our scripts in the way described by OP.

Which means that both were working and the fault is with users hardware. Sort of a PEBRAC.

 

[figorr]

Here is the feedback from today,

Since yesterday, around 11:00pm, no more issues. So around 17hours running. It seems UiDivStats is updating the graph and table fine.

I don’t think It was an USB problem. I didn’t see any strange system log. And there are many other scripts (unbound, connmon, ntpmerlin, ...) working Ok and updating the graphs and tables without any issues.

It is weird but It seems to be resolved. I am going to share what I did yesterday so if could help someone else.

1. I uninstalled UiDivStats..
2. I removed the folder “UiDivStats.d“ located at /opt/share/
3. I opened amtm and Diversion.
4. I used option “d” at Diversion in order to open the install and uninstall options.
5. I used the option “Reinstall Diversion”. I think it was option “2”
6. Then I left to settle everything a couple of minutes. Just to be sure Diversion was running Ok after reinstalling it.
7. Then I reinstalled UiDivStats (option j5 in amtm). And everything went smoothly creating the new database. No more errors.

Since then ... it seems UiDivStats had not stopped of updating the graph and table.

It is weird but It seems this had solved the issue by now. I don’t know why.

If there is more news during the following hours I will post it here.

 

[JR Godwin]

What's the best way to determine if the USB is having problems? Look at the disk check log in AMTM?

 

[ComputerSteve]

See I think something is wrong too. I never had any problems with my Orbi. I now upgraded / reset / reconfigured the asus router after upgrading and since installing through AMTM I can’t get my Orbi to get an IP address from the asus. If I don’t install diversion I get an iP.

 

[Wishmaster1965]

If this was me I would do a fectory reset and start again.

 

[ComputerSteve]

So everytime I enable Diversion with AiMesh / Pixelserv-Tls dhcp stops working correctly.. At least on the RT-AC5300. I have tried factory resetting / TFTP re-installing firmware with same result.

 

[#TY]

Is Diversion still supported and under development?

 

[thelonelycoder]

Is Diversion still supported and under development?

That's a yes for both - and it includes amtm.

 

[ComputerSteve]

So is any testing being done with the latest Merlin & Diversion... I downgraded to 384.19 & now Diversion is working with fine with Full blocklist / Minimal as alternative / W alternative lan using DNS filtering. I also have AiMesh setup with this working correctly. Every time I upgrade to 386 with the new AiMesh UI the router stops responding correctly with DHCP. Devices don't receive IP addresses, the nodes never connect. As soon as I disable Diversion & Pixelserv then things work. I don't have any of these problems on 384.19. Thing is i'd like to get the new AiMesh UI so i'm hoping this gets fixed.

 

[thelonelycoder]

So is any testing being done with the latest Merlin & Diversion... I downgraded to 384.19 & now Diversion is working with fine with Full blocklist / Minimal as alternative / W alternative lan using DNS filtering. I also have AiMesh setup with this working correctly. Every time I upgrade to 386 with the new AiMesh UI the router stops responding correctly with DHCP. Devices don't receive IP addresses, the nodes never connect. As soon as I disable Diversion & Pixelserv then things work. I don't have any of these problems on 384.19. Thing is i'd like to get the new AiMesh UI so i'm hoping this gets fixed.

amtm and Diversion development were on a standstill for close to half a year now. I did post an update for amtm yesterday to catch up to the 386.x firmware changes. Diversion will follow assoon as it caught up too.

 

[#TY]

amtm and Diversion development were on a standstill for close to half a year now. I did post an update for amtm yesterday to catch up to the 386.x firmware changes. Diversion will follow assoon as it caught up too.

I'm really looking forward to it. I was a little concerned the project may have been abandoned but happy to read it's not. So many more great things possible with it. Thank you!

 

[ComputerSteve]

amtm and Diversion development were on a standstill for close to half a year now. I did post an update for amtm yesterday to catch up to the 386.x firmware changes. Diversion will follow assoon as it caught up too.

So I am very happy to hear you are continuing development. I have discovered that enabling the alternate blocking list with the second instance of dnsmasq seems to kill the router and Aimesh. Setting diversion up default with standard blocking seems to work. Is there a place we can donate to you for your efforts ? ( Never mind found it on your site and donated =] )

 

[sentinelvdx]

@thelonelycoder after updating amtm to 3.1.9 I've found diversion throws an error and amtm when accessing it gets CPU too high making router extremely slow responsive.
I'm remote so I was trying to remember how to uninstall diversion using command line to reinstall it (force reinstall causes router to reboot)

Can you remember me the command to uninstall it?

Thanks

 

[dev_null]

@thelonelycoder after updating amtm to 3.1.9 I've found diversion throws an error and amtm when accessing it gets CPU too high making router extremely slow responsive.
I'm remote so I was trying to remember how to uninstall diversion using command line to reinstall it (force reinstall causes router to reboot)

Can you remember me the command to uninstall it?

Thanks

You can't access via the amtm menu and pick uninstall?

That would seem to be the most straightforward and controlled way of doing it.

EDIT maybe diversion uninstall from the CLI.

 

[sentinelvdx]

You can't access via the amtm menu and pick uninstall?

That would seem to be the most straightforward and controlled way of doing it.

Yes, but when trying to access amtm, it shows the title and after some minutes router ssh drops.
I finally unmounted the usb drive, formatted it nd reinstalled everything back

 

[Ninko]

I don't know for a fact that diversion is what's causing my problem but it sounds similar.

After updating to 386.1_2 I find whenever I make any WiFi setting changes that require the client to reconnect, none of them are able to obtain an IP address.

The only way to fix it, other then a full reset is to restart the router without the USB pen drive, once everything is connected again I can safely plug the USB drive back in.

Everything appears ok after, unless I make any WiFi setting changes again.

Never had this problem before upgrading.

Sorry if I'm not explaining it very well.

 

[ComputerSteve]

I don't know for a fact that diversion is what's causing my problem but it sounds similar.

After updating to 386.1_2 I find whenever I make any WiFi setting changes that require the client to reconnect, none of them are able to obtain an IP address.

The only way to fix it, other then a full reset is to restart the router without the USB pen drive, once everything is connected again I can safely plug the USB drive back in.

Everything appears ok after, unless I make any WiFi setting changes again.

Never had this problem before upgrading.

Sorry if I'm not explaining it very well.

I have the same problem.. If I change any wifi settings / I loose the web interface. I can still access the router through SSH but to restore the web interface I have to do a full restart of everything.

 

[visortgw]

I have the same problem.. If I change any wifi settings / I loose the web interface. I can still access the router through SSH but to restore the web interface I have to do a full restart of everything.

Have you tried restarting httpd from scMerlin as opposed to full restart?

 

[Ninko]

I have the same problem.. If I change any wifi settings / I loose the web interface. I can still access the router through SSH but to restore the web interface I have to do a full restart of everything.

I think this problem is a little different to mine. It's not that I can't access the web interface, it's that it seems the DHCP server stops working, as no device is able to obtain an IP address and so is unable to connect.

 

[ComputerSteve]

Have you tried restarting httpd from scMerlin as opposed to full restart?

Didn’t try that. How do I even do that lol