Recent content by miazza

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. M

    Device all of a sudden is assigning itself a 169.254 IP address when coming out of standby

    I agree: after about one month I can say that since I reinstalled Diversion and amtm from scretch the problem disappeared ; so something was most likely messed in the router configuration.
  2. M

    BACKUPMON BACKUPMON v1.5.10 -Mar 1, 2024- Backup/Restore your Router: JFFS + NVRAM + External USB Drive! (**Thread closed due to age**)

    Finally making a back-up in cron is important only if you are changing your configuration on a daily/weekly basis. Otherwise it si worth to run a manual only when needed avoiding to increment the used space on the backup disk.
  3. M

    Device all of a sudden is assigning itself a 169.254 IP address when coming out of standby

    It's now about two weeks and I started from scratch. Also I removed in the DNS the IP reserved for pixelserv.
  4. M

    Device all of a sudden is assigning itself a 169.254 IP address when coming out of standby

    It will not solve the issue. Even fixing the IP in the host will not unlck the situation (at least in my case). Anyhow after Diversion uninstall/install the problem is not manifested so far.
  5. M

    Device all of a sudden is assigning itself a 169.254 IP address when coming out of standby

    I was sayin that I do not have a switch in between the router and the NAS and the problem is on the NAS. I have a switch on another port where I have the TV and a Raspberry. By th way with the same set-up I never had problems for years.
  6. M

    Device all of a sudden is assigning itself a 169.254 IP address when coming out of standby

    In my case this was not changing the problem and my host is connected straight to the router with 50cm LAN cable (no switch in between).
  7. M

    Device all of a sudden is assigning itself a 169.254 IP address when coming out of standby

    After having uninstalled and reinstalled Diversion from amtm the problem did not occur anymore. It's about 10 days. I also reconfigured the DHCP to start IP allocation from 192.168.1.2 (before it was assigned to Diversion but now no more needed from 5.0). Instead of powercycle you can reboot...
  8. M

    BACKUPMON BACKUPMON v1.5.10 -Mar 1, 2024- Backup/Restore your Router: JFFS + NVRAM + External USB Drive! (**Thread closed due to age**)

    Try with service reboot instead of a simple reboot. It's not the same and is the way amtm reboot scheduler works.
  9. M

    BACKUPMON BACKUPMON v1.5.10 -Mar 1, 2024- Backup/Restore your Router: JFFS + NVRAM + External USB Drive! (**Thread closed due to age**)

    I realised the same on my installation. I made a manual backup with a schedued monthly backup but I could not find anything added to the cron job. I did not investigate because I am not changing the router configuration frequently and I can run it manually when needed. Anyhow this evening I will...
  10. M

    BACKUPMON BACKUPMON v1.5.10 -Mar 1, 2024- Backup/Restore your Router: JFFS + NVRAM + External USB Drive! (**Thread closed due to age**)

    Excellent ! This works great. Messages: STATUS: External drive (USB) mounted successfully as: /tmp/mnt/RT86U_SMB STATUS: Finished backing up JFFS to /tmp/mnt/RT86U_SMB/RT86U-Backup/18/jffs.tar.gz. STATUS: Finished backing up NVRAM to /tmp/mnt/RT86U_SMB/RT86U-Backup/18/nvram.cfg. STATUS: Finished...
  11. M

    BACKUPMON BACKUPMON v1.5.10 -Mar 1, 2024- Backup/Restore your Router: JFFS + NVRAM + External USB Drive! (**Thread closed due to age**)

    Hi all. Thank you for this very useful script. I have made a network backup on my USB 3 port that is also smb share. At the end of the script, the USB is unmounted and remains therefore not reachable on the samba. Is there any way to avoid the umount at the end of the proess ? Messages: STATUS...
  12. M

    Device all of a sudden is assigning itself a 169.254 IP address when coming out of standby

    Yes clear. I do not like to fix the IP in the device : DHCP shall work with the MAC Address IP reservation (as for all the other wifi devices I have in the network) and I might consider the bandaid only as a temporary solution (by the way, even setting a fixed own IP and DNS on the NAS does not...
  13. M

    Device all of a sudden is assigning itself a 169.254 IP address when coming out of standby

    What do you mean ? Shall I configure the NAS and Pi with the same host of the router ?
  14. M

    Restart DHCP without reboot?

    Thank you. I did not search in the CLI because normally I use the WebIf panel (user3.asp). It is a pity not to have it in the webif... at least I have not found it.
  15. M

    AC86U - DHCP not assigning IP.

    The command "service reboot" makes the trick. It is not the same of a simple reboot. Despite I have not understood why the DHCP get stuck and not assigning the IP to those devices that are not connected to the router during the last switch-on.
Top